- Newest
- Most votes
- Most comments
The error you're encountering suggests that the S3 bucket specified for your pipeline's artifact storage does not exist or is not accessible. This is likely due to the pipeline trying to upload artifacts to a non-existent or inaccessible S3 bucket during the Approval Workflow-beta stage. Here are some steps to troubleshoot and resolve this issue:
-
Verify the S3 bucket existence: Check if the bucket "codetest-us-west-2-298037688727-do-not-delete" exists in your AWS account. If it doesn't exist, you'll need to create it or update your pipeline configuration to use an existing bucket.
-
Check bucket permissions: Ensure that the IAM role used by your pipeline has the necessary permissions to access and write to the specified S3 bucket. The role should have s3:PutObject and s3:CreateMultipartUpload permissions at a minimum.
-
Review pipeline configuration: Double-check your pipeline configuration, especially for the new fe-beta stage, to make sure it's using the correct S3 bucket for artifact storage.
-
Validate cross-account access: If you're working across multiple AWS accounts, ensure that the necessary cross-account permissions are in place for accessing the S3 bucket.
-
Check for typos: Verify that there are no typos in the bucket name within your pipeline configuration.
-
Rerun bootstrap: Since you mentioned running "bb bootstrap" only once previously, consider running it again to ensure all necessary resources, including the S3 bucket, are properly set up for your updated pipeline configuration.
-
Review CloudWatch Logs: Check the CloudWatch logs for your pipeline to see if there are any additional error messages or clues about why the bucket access is failing.
-
Verify region consistency: Ensure that the region specified in your pipeline configuration matches the region where the S3 bucket is located.
If after checking these points the issue persists, you may need to recreate the S3 bucket or update your pipeline configuration to use a different, existing bucket for artifact storage. Remember to update any relevant IAM policies to reflect any changes in bucket names or locations.
Sources
Glue Error: error occurred while calling o228.pyWriteDynamicFrame. com.amazon.ws.emr.hadoop.fs.shaded.com.amazonaws.services.s3.model.AmazonS3Exception: The specified bucket does not exist | AWS re:Post
Codepipline s3 source action does not work | AWS re:Post
Relevant content
- asked 3 years ago
