S3 Pipeline Errors

For more information about creating pipelines with S3, refer to Load Data from Amazon Web Services (AWS) S3.

S3 Authentication Errors

You may receive authentication errors if you attempt to create an S3 pipeline without providing credentials or if the provided credentials are invalid.

NoCredentialProviders: no valid providers in chain.

This error is caused by one or more of the following conditions:

  • No CREDENTIALS were specified in the CREATE PIPELINE statement or the JSON was malformed.

  • An IAM role was specified, but your EC2 instance was not configured with an instance profile.

"aws_access_key_id" specified, but not "aws_secret_access_key"

This error is caused by a missing aws_secret_access_key key in the CREDENTIALS JSON of your CREATE PIPELINE statement, or if the JSON key is malformed.

"aws_secret_access_key" specified, but not "aws_access_key_id"

This error is caused by a missing aws_access_key_id key in the CREDENTIALS JSON of your CREATE PIPELINE statement, or if the JSON is malformed.

InvalidAccessKeyID: The access key ID you provided does not exist in our records

This error is caused by specifying an Access Key ID that does not exist.

SignatureDoesNotMatch: The request signature we calculated does not match the signature you provided. Check your key and signing method

This error is caused by specifying an invalid combination of an Access Key ID and a Secret Access Key.

Subprocess timed out or CREATE PIPELINE stalls after approximately 60 seconds when using S3 without CREDENTIALS

This occurs when the IMDS reachability probe for implicit AWS credentials times out on networks where the 169.254.169.254 IP address is unreachable. To resolve this issue, either reduce the value of the subprocess_ec2_metadata_timeout_ms engine variable (for example, to 1000) or provide explicit CREDENTIALS for S3. Refer to List of Engine Variables for more information.

Last modified:

Was this article helpful?