2 réponses
- Le plus récent
- Le plus de votes
- La plupart des commentaires
1
I believe this could be due to one of these two:
- Are you using an S3 bucket owned by a different account? MWAA executes the code inside the provided bucket and as such the security standard regarding this S3 bucket is to be kept very high. As part of that, only buckets within the same account as the user trying to create the environment are allowed.
- The S3 bucket field needs a high level S3 bucket in the format of
s3://mybucket
. It does not allow folders or prefixes. So, if you are usings3://mybucket/my-prefix
that would not work
Let me know if that fixes your problem
répondu il y a 2 ans
0
Thank you. It was probably number 2 - having used a folder. But I had fixed it using CloudFormation (which creates a top level bucket within the config) instead of going through the web console. Appreciate the help!
répondu il y a 2 ans
Contenus pertinents
- demandé il y a un an
- Réponse acceptéedemandé il y a 2 ans
- demandé il y a un an
- AWS OFFICIELA mis à jour il y a 3 ans
- AWS OFFICIELA mis à jour il y a un an
- Comment dépanner mon environnement Amazon MWAA bloqué à l'état « Creating (En cours de création) » ?AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 2 ans