Troubleshooting
Problem
The behaviour is seen when we start the pipeline/job, it will fail with the mentioned error message.
There could be multiple reasons for getting S3_SPOOLDIR_20 error code.
Example:
Incorrect Bucket name:
S3_SPOOLDIR_20 - Cannot connect to Amazon S3, reason : com.amazonaws.services.s3.model.AmazonS3Exception: The request signature we calculated does not match the signature you provided. Check your key and signing method. (Service: Amazon S3; Status Code: 403; Error Code: SignatureDoesNotMatch; Request ID: X88A06533SXRX84E; S3 Extended Request ID: KQkWK2ec9/jR31bACAjxzcuQTbV0OiW72zkehSKf6kLmky5XKCkew3oJhBqfQJUcbU+zOXtm6Ic=; Proxy: null), S3 Extended Request ID: KQkWK2ec9/jR31bACAjxzcuQTbV0OiW72zkehSKf6kLmky5XKCkew3oJhBqfQJUcbU+zOXtm6Ic=Invalid endpoint specified in the option Region Other-specify:
S3_SPOOLDIR_20 - Cannot connect to Amazon S3, reason : com.amazonaws.SdkClientException: Unable to execute HTTP request: <bucketname>.endpointIncorrect Access Key ID and Secret Access Key specified when using AWS keys as Authentication Method:
S3_SPOOLDIR_20 - Cannot connect to Amazon S3, reason : com.amazonaws.services.s3.model.AmazonS3Exception: The AWS Access Key Id you provided does not exist in our records. (Service: Amazon S3; Status Code: 403; Error Code: InvalidAccessKeyId; Request ID: BGTS5N1TE0B71XPX; S3 Extended Request ID: AqzQDezfpLmORycx9I0C3WA5ssfXJV27nCVJ8IHGA/vQlffT1shueiAh9HT2rUOo6EIs6e92rvY=; Proxy: null), S3 Extended Request ID: AqzQDezfpLmORycx9I0C3WA5ssfXJV27nCVJ8IHGA/vQlffT1shueiAh9HT2rUOo6EIs6e92rvY=
Symptom
We observe this error message when writing or reading data from Amazon S3 bucket.
Resolving The Problem
Depending on the error message, please verify and configure the correct values.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
15 March 2025
UID
ibm17186238