[hsusul]

Why

S3 CreateBucket on a bucket that already exists in the project returns BucketAlreadyExists. Amazon S3 returns BucketAlreadyOwnedByYou when the caller owns the bucket, and the Storage bucket namespace is per project. Clients that treat that code as "already created" fail instead.

Fixes #1656.

What changed

• S3ProtocolHandler.createBucket maps BucketAlreadyExists to a new S3BucketAlreadyOwnedByYou error with code BucketAlreadyOwnedByYou.
• The status stays 409. This follows the S3BucketNotEmpty pattern from fix(s3): report BucketNotEmpty when deleting a non-empty bucket #1448.

Scope

Only the S3 protocol code for this one case changes. The REST API keeps BucketAlreadyExists.

Verification

• npm run test:unit -- src/storage/protocols/s3/s3-handler.test.ts failed at the test commit with Expected "BucketAlreadyOwnedByYou", Received "BucketAlreadyExists", then passed all 88 tests with the fix. Full npm run test:unit passed 3,485 tests.
• formatS3ErrorResponse on the handler's error now gives Code: BucketAlreadyOwnedByYou instead of BucketAlreadyExists.
• npm run lint and npm run build passed. Integration tests were not run.

[coveralls]

Coverage Report for CI Build 41881508237

Warning

Build has drifted: This PR's base is out of sync with its target branch, so coverage data may include unrelated changes.
Quick fix: rebase this PR. Learn more →

Coverage increased (+0.004%) to 87.245%

Details

• Coverage increased (+0.004%) from the base build.
• Patch coverage: 7 of 7 lines across 2 files are fully covered (100%).
• No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	15844
Covered Lines:	14268
Line Coverage:	90.05%
Relevant Branches:	10083
Covered Branches:	8352
Branch Coverage:	82.83%
Branches in Coverage %:	Yes
Coverage Strength:	1256.25 hits per line

---

💛 - Coveralls