2 個答案
- 最新
- 最多得票
- 最多評論
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
已回答 2 年前
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!
已回答 2 年前
相關內容
- AWS 官方已更新 2 年前
- AWS 官方已更新 2 年前