S3 Authentication Errors
On this page
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 theCREATE 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_
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_
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.
Last modified: April 24, 2021