Default authentication | Redshift IAM Authentication via Assume Role |
---|---|
|
|
*To use the Redshift IAM role ARN, configure the Redshift IAM role ARN with the required trust policies to generate temporary security credentials to access Amazon Redshift. For instructions, see Configure an assume role for Amazon Redshift. |
S3 staging options | Tasks |
---|---|
Generate temporary credentials for the IAM user who assumes the S3 IAM role to access S3 staging. | AWS configurations Enable IAM users to assume an S3 IAM role and generate temporary credentials. For instructions, see the following references:
Redshift V2 connection configurations
|
Generate temporary security credentials for an EC2 instance that assumes an S3 IAM role to access S3 staging. | AWS configurations Define an EC2 instance to assume an S3 IAM role and generate the temporary credentials for S3 staging. For instructions, see Generate temporary security credentials using AssumeRole for EC2. Redshift V2 connection configurations Configure the following minimum required properties:
|
Generate the S3 access and secret access keys for the IAM user with access to the S3 bucket. | AWS configurations To generate the credentials, perform the following tasks:
For more information about how to create an IAM user and generate keys, see the AWS documentation. Redshift V2 connection configurations Enter the S3 Access Key ID and S3 Secret Access Key values. |
Configure IAM authentication | AWS configurations If you have an EC2 instance, and do not want to specify the keys or use the IAM role ARN, then assign the minimum policy to the EC2 with access to the S3 bucket. For instructions, see Configure IAM authentication. Redshift V2 connection configurations In this case, you do not need to enable or specify any of the staging properties in the connection. However, before you run the mapping, specify the Redshift role assigned to the Redshift cluster in the UnloadOptions and CopyOptions Property File fields in the mapping. |