1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
First thing that came to mind is encryption, and if KMS is used then whether ImageBuilder has the privileges to utilise the keys?
This is one of several things identified that can cause 403 errors, and it would be worth stepping through all of them https://repost.aws/knowledge-center/s3-403-forbidden-error
The associated video is helpful as well https://www.youtube.com/watch?v=rn4qLXhMesg
I looked at the video and the repots page but did not find anything that helped. In the end I just removed the bucket from the config and it got past that step.
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
I had thought of the keys too. But we are using Server-side encryption with Amazon S3 managed keys (SSE-S3). So we should be good. I will check out the rest of the page you sent me and the video to see if there is something else I am missing.