Redshift OLEDB AWS Access key issue

More
3 years 11 months ago #13835 by rseshadri
rseshadri created the topic: Redshift OLEDB AWS Access key issue
Im testing the Redshift OLE DB Provider. My source is MySql and Destination is Redshift.

OLE DB Destination using the Redshift OLE DB connection manager throws this error when running the package.

SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005.
An OLE DB record is available. Source: "Redshift OLE DB Provider" Hresult: 0x80004005 Description: "ERROR: AWS access key ID not found
DETAIL:
error: AWS access key ID not found
code: 8001
context:
query: 490183
location: aws_credentials_parser.cpp:96
process: padbmaster [pid=27899]

Why do we need to specify the aws access /secret key and s3 bucket folder name? I was able to test the connection during design time and it was successful. This error is thrown when I run the package. Can we skip the aws access/secret key and s3 bucket name? My source is MySql ODBC.

Thanks
Ravi

Please Log in or Create an account to join the conversation.

More
3 years 11 months ago #13836 by rseshadri
rseshadri replied the topic: Re: Redshift OLEDB AWS Access key issue
After providing the AWS Access/Secret/S3 bucket info. I get this error during package execution...

DETAIL:
error: S3ServiceException:The request signature we calculated does not match the signature you provided. Check your key and signing method.,Status 403,Error SignatureDoesNotMatch,Rid 6EB88F186C874907,ExtRid Lv1jVu+617/oQFffgCQsdOcP5UP/afGcAmgG62OXnXEj607Ida4dMU2m
code: 8001
context: Listing bucket=http: prefix=/s3.amazonaws.com/dev-dw-load/640F5F91248742EB8F32F206AE4C72A4
query: 491059
location: s3_utility.cpp:529
process: padbmaster [pid=4314]

Please Log in or Create an account to join the conversation.

More
3 years 10 months ago #13838 by Moderator
Moderator replied the topic: Re: Redshift OLEDB AWS Access key issue
There could be many reasons for the error: a trailing space or a single quote in the end of the secret key, forward slash in front of the bucket name, etc. Please double check the connection string parameters (AWS_*).

You can capture parameters of generated COPY command in the PGNProfiler, or by using tools like WireShark.

Please Log in or Create an account to join the conversation.

Time to create page: 0.122 seconds
Powered by Kunena Forum