forked from TrueCloudLab/frostfs-s3-gw
[#732] docs: Clarify some outputs of bucket creation
Add description with interpretation of some AWS CLI outputs occurred during bucket creation. Signed-off-by: Leonard Lyubich <ctulhurider@gmail.com>
This commit is contained in:
parent
7bbbda6b7e
commit
f6b94c25c5
1 changed files with 10 additions and 0 deletions
|
@ -44,6 +44,16 @@ $ aws s3api create-bucket --bucket %BUCKET_NAME --acl %ACL
|
||||||
where `%ACL` can be represented by a hex encoded value or by keywords `public-read-write`, `private`, `public-read`.
|
where `%ACL` can be represented by a hex encoded value or by keywords `public-read-write`, `private`, `public-read`.
|
||||||
If the parameter is not set, the default value is `private`.
|
If the parameter is not set, the default value is `private`.
|
||||||
|
|
||||||
|
> **_NOTE:_** Bucket creation uses async-poll approach. `BucketAlreadyOwnedByYou`
|
||||||
|
> status can occur if the AWS CLI makes multiple attempts (see details
|
||||||
|
> in [docs](https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-retries.html)).
|
||||||
|
> This status means successful bucket creation after several tries. When the
|
||||||
|
> operation has not been completed in the entire wait time, timeout status outputs.
|
||||||
|
> Timeout does not always mean failure of the operation: success can be checked
|
||||||
|
> later by bucket getting/listing commands, or by repeating the creating command
|
||||||
|
> (previous success will result in the status mentioned above). It is worth clarifying
|
||||||
|
> that the final success of the bucket creation is not guaranteed after a timeout error.
|
||||||
|
|
||||||
#### Deletion of a bucket
|
#### Deletion of a bucket
|
||||||
|
|
||||||
To delete a bucket, execute the following command:
|
To delete a bucket, execute the following command:
|
||||||
|
|
Loading…
Reference in a new issue