2 Answers
- Newest
- Most votes
- Most comments
0
Hello,
The issue was resolved by renaming the S3 bucket to comply with AWS naming conventions. If you're facing a similar problem, make sure your S3 bucket name only includes lowercase letters, numbers, hyphens, and periods, as per AWS requirements.
https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html
Relevant content
- asked 10 months ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago