Configuring your Redshift destination.
<password>
with a password of your choice).CREATE USER <username> PASSWORD DISABLE;
.create
and temporary
privileges on the database. create
allows the service to create new schemas and temporary
allows the service to create temporary tables.schema
already exists
By default, the service creates a new schema based on the destination configuration. If you prefer to create the schema yourself before connecting the destination, you must ensure that the writer user has the proper permissions on the schema, using GRANT ALL ON schema <schema> TO <username>;
Once you’ve provided the GRANT ALL
permission on the schema, you can safely remove the CREATE
permission on the database (but you must retain the TEMPORARY
permission on the database).5439
)BUCKET_NAME
with the name of the bucket chosen above, and REGION_NAME, ACCOUNT_ID, CLUSTER_NAME, USERNAME, and DATABASE_NAME with the proper Redshift values.
BUCKET_NAME
whereas the second permission applies only to the bucket’s contents — BUCKET_NAME/*
— an important distinction.transfer-service-policy
(this will be referenced in the next step), add a description, and click Create policy.transfer-role
, and click Create role.transfer-service
, click Next. Under Select AWS access type, select the Access key - Programatic access option. Click Next: Permissions.