Create an IAM role that can be assumed by AWS Glue, Redshift, and S3. This role should have the necessary permissions to read from your Redshift cluster and write to your S3 bucket. Attach policies like `AmazonRedshiftReadOnlyAccess`, `AmazonS3FullAccess`, and `AWSGlueServiceRole`.

Ensure that the data you want to export is ready in Amazon Redshift. This might involve cleaning up your dataset, transforming it into the desired format, and possibly creating new tables or views optimized for export.

Create a new S3 bucket or choose an existing one where you want to store the exported data. Ensure the bucket's permissions allow access from the IAM role you set up in Step 1.

In the AWS Glue console, create a new Glue job. Select the IAM role created in Step 1 for the job execution. Choose the option to use a script editor, as you will be writing a custom script to extract data from Redshift and load it into S3.

Use the PySpark or Scala script in your Glue job to connect to Redshift and extract the required data. Use the `jdbc` connection to read from Redshift and the `write` method to output to S3 in the desired format (e.g., CSV, Parquet). An example script snippet might look like this:
```python
# Initialize Glue context
glueContext = GlueContext(SparkContext.getOrCreate())

# Read data from Redshift
redshift_data = glueContext.create_dynamic_frame.from_options(
connection_type="redshift",
connection_options={
"url": "jdbc:redshift://:5439/",
"user": "",
"password": "",
"dbtable": ".

"
}
)

# Write data to S3
glueContext.write_dynamic_frame.from_options(
frame=redshift_data,
connection_type="s3",
connection_options={"path": "s3:///"},
format="parquet" # or "csv", "json" etc.
)
```

Configure your Glue job's properties, such as specifying the number of DPUs (Data Processing Units) and setting up any needed retry policies. Ensure your job is set to run with sufficient resources to handle the data volume.

Execute the Glue job and monitor its progress through the AWS Glue console. Check for any errors or logs if the job fails to ensure successful data transfer. Once the job completes, verify that the data appears in the S3 bucket as expected.

By following these steps, you can efficiently move data from Amazon Redshift to S3 using AWS Glue without relying on third-party connectors or integrations. Adjust the script and configurations as necessary to fit your specific data and infrastructure requirements.