1 Answer
- Newest
- Most votes
- Most comments
0
That's an authentication failure, not a permissions issue. It sounds like you have a static access key created for your IAM user, and it comes with an access key ID ("username") and a secret key ("password") with which your API requests must be signed. Check the access key ID and secret key that you're supplying to your code/command. If they seem to be correct, you've probably dropped a character or few when you copied them originally, and the simple solution is to create a new access key and make sure to record the key ID and secret key accurately.
Relevant content
- Accepted Answerasked a year ago
- AWS OFFICIALUpdated 6 months ago
- AWS OFFICIALUpdated 4 months ago
Hi
If you deep dive into my issue , I could able to create the table : table metadata json file is creating in the S3 Bucket folder , if its access issue then It shouldn't create any file in the S3 bucket right !!!