HTTP status codes (PUT bucket)

The table below describes HTTP status codes that can be returned in response to a request to create a bucket. For more information about HTTP status codes and the error codes that can accompany them, see Error codes.

Code Meaning Description
200 OK

One of these:

The bucket was successfully created.

A bucket with the specified name already exists and is owned by you.

400 Bad Request

Possible reasons include:

The specified bucket name is invalid.

An ACL grant header specifies an invalid grantee.

You already own the maximum number buckets allowed per user.

The tenant does not have enough space for another bucket.

The tenant already has the maximum number of buckets it’s allowed to have.

403 Forbidden

Possible reasons include:

The credentials provided with the request are invalid.

You do not have permission to create buckets.

The tenant does not currently support use of the S3 compatible API for creating buckets.

409 Conflict A bucket with the specified name already exists and either is owned by a user other than you or has no owner.
500 Internal Server Error

An internal error occurred.

If this error persists, contact your tenant administrator.

501 Not Implemented The request includes the x-amz-acl header with an invalid value.
503 Service Unavailable

HCP is temporarily unable to handle the request, probably due to system overload, maintenance, or upgrade. Try the request again, gradually increasing the delay between each successive attempt.

If this error persists, contact your tenant administrator.

© 2015, 2020 Hitachi Vantara LLC. All rights reserved.