Unexpected output of `aws s3api create-bucket` using S3 gateway #343

New issue

Closed

opened 2025-12-28 17:37:05 +00:00 by sami · 1 comment

sami commented

2025-12-28 17:37:05 +00:00

Owner

Originally created by @cthulhu-rider on GitHub (Oct 25, 2022).

Originally assigned to: @cthulhu-rider on GitHub.

I tried to create S3 bucket using NeoFS S3 Gateway app which is pointed to the NeoFS TestNet.

aws s3api create-bucket --bucket buget --acl public-read-write

I've got this error

An error occurred (BucketAlreadyOwnedByYou) when calling the CreateBucket operation: Your previous request to create the named bucket succeeded and you already own it.

Despite this message, overall, the bucket has been successfully created in the network:

aws s3 ls
...
2022-10-25 15:27:17 buget
...

Gateway log:

2022-10-25T15:28:16.192+0400	error	handler/util.go:26	could not create bucket	{"request_id": "1a5c36aa-67c3-4fe7-a82d-895380be3341", "method": "CreateBucket", "bucket_name": "buget", "object_name": "", "error": "set container eacl: save eACL via connection pool: wait eacl presence on client: context canceled"}
2022-10-25T15:28:16.192+0400	error	api/router.go:158	something went wrong	{"status": 500, "request_id": "1a5c36aa-67c3-4fe7-a82d-895380be3341", "method": "CreateBucket", "description": "Internal Server Error"}
2022-10-25T15:28:17.842+0400	error	handler/util.go:26	could not create bucket	{"request_id": "3834d6ec-f305-42d7-a58c-df5178d56f5f", "method": "CreateBucket", "bucket_name": "buget", "object_name": "", "error": "BucketAlreadyOwnedByYou: 409 => Your previous request to create the named bucket succeeded and you already own it."}
2022-10-25T15:28:17.843+0400	error	api/router.go:158	something went wrong	{"status": 409, "request_id": "3834d6ec-f305-42d7-a58c-df5178d56f5f", "method": "CreateBucket", "description": "Conflict"}

Seems like 1st time container creation op failed by timeout, container was created asynchronously, and 2nd time gateway encountered the name conflict.

The output confused me a bit, but I'm not closely familiar with AWS CLI, maybe this scenario is expected. Just in case, I'll leave it for inspection.

Originally created by @cthulhu-rider on GitHub (Oct 25, 2022). Originally assigned to: @cthulhu-rider on GitHub. I tried to create S3 bucket using NeoFS S3 Gateway app which is pointed to the NeoFS TestNet. ``` aws s3api create-bucket --bucket buget --acl public-read-write ``` I've got this error ``` An error occurred (BucketAlreadyOwnedByYou) when calling the CreateBucket operation: Your previous request to create the named bucket succeeded and you already own it. ``` Despite this message, overall, the bucket has been successfully created in the network: ``` aws s3 ls ... 2022-10-25 15:27:17 buget ... ``` Gateway log: ``` 2022-10-25T15:28:16.192+0400 error handler/util.go:26 could not create bucket {"request_id": "1a5c36aa-67c3-4fe7-a82d-895380be3341", "method": "CreateBucket", "bucket_name": "buget", "object_name": "", "error": "set container eacl: save eACL via connection pool: wait eacl presence on client: context canceled"} 2022-10-25T15:28:16.192+0400 error api/router.go:158 something went wrong {"status": 500, "request_id": "1a5c36aa-67c3-4fe7-a82d-895380be3341", "method": "CreateBucket", "description": "Internal Server Error"} 2022-10-25T15:28:17.842+0400 error handler/util.go:26 could not create bucket {"request_id": "3834d6ec-f305-42d7-a58c-df5178d56f5f", "method": "CreateBucket", "bucket_name": "buget", "object_name": "", "error": "BucketAlreadyOwnedByYou: 409 => Your previous request to create the named bucket succeeded and you already own it."} 2022-10-25T15:28:17.843+0400 error api/router.go:158 something went wrong {"status": 409, "request_id": "3834d6ec-f305-42d7-a58c-df5178d56f5f", "method": "CreateBucket", "description": "Conflict"} ``` Seems like 1st time container creation op failed by timeout, container was created asynchronously, and 2nd time gateway encountered the name conflict. The output confused me a bit, but I'm not closely familiar with AWS CLI, maybe this scenario is expected. Just in case, I'll leave it for inspection.

sami

2025-12-28 17:37:05 +00:00

closed this issue
added the
question

discussion
labels

sami commented

2025-12-28 17:37:05 +00:00

Author

Owner

@KirillovDenis commented on GitHub (Oct 25, 2022):

I usually use export AWS_MAX_ATTEMPTS=1 this variable to prevent retry and see real error (if it happens)

@KirillovDenis commented on GitHub (Oct 25, 2022): I usually use `export AWS_MAX_ATTEMPTS=1` this variable to prevent retry and see real error (if it happens)