The option "---no-object-lock-enabled-for-bucket" does not work with AWS CLI:The created bucket has always all public access blocked!
0
When I create a bucket using the AWS CLI, it has by default "block public access". When trying to create a bucket having public access enabled: I used the option from the documentation : "--no-object-lock-enabled-for-bucket", but it turns out that also with the opposite option "object-lock-enabled-for-bucket", the public access is always disabled !
Here 2 screenshots
commands
1 Answer
- Newest
- Most votes
- Most comments
0
You are using the wrong option. ---no-object-lock-enabled-for-bucket set S3 Object Lock behavior for the bucket.
To adjust the Block Public Access use put-public-access-block.
Relevant content
AWS OFFICIALUpdated a month ago- AWS OFFICIALUpdated 10 months ago
by default when creating a bucket (the public access is blocked)! I want an option to do the opposite thing, so I added --no-object-lock-enabled-for-bucket or even --object-lock-enabled-for-bucket (but it has no effect), the access remains blocked! (just try it et you will see: it is odd!) that with the AWS command line , this option is obselete (but still exsists in the documentation). To get a bucket wiht open public access (not blocked), I have to do 2 commands :
Because S3 Object Lock is a different thing than Block Public Access. They do two different things.