Bucket

Access controls on the bucket.

The bucket's Autoclass configuration.

The bucket's billing configuration.

The bucket's Cross-Origin Resource Sharing (CORS) configuration.

The bucket's custom placement configuration for Custom Dual Regions.

The default value for event-based hold on newly created objects in this bucket. Event-based hold is a way to retain objects indefinitely until an event occurs, signified by the hold's release. After being released, such objects will be subject to bucket-level retention (if any). One sample use case of this flag is for banks to hold loan documents for at least 3 years after loan is paid in full. Here, bucket-level retention is 3 years and the event is loan being paid in full. In this example, these objects will be held intact for any number of years until the event has occurred (event-based hold on the object is released) and then 3 more years after that. That means retention duration of the objects begins from the moment event-based hold transitioned from true to false. Objects under event-based hold cannot be deleted, overwritten or archived until the hold is removed.

Default access controls to apply to new objects when no ACL is provided.

Encryption configuration for a bucket.

HTTP 1.1 Entity tag for the bucket.

The bucket's IAM configuration.

The kind of item this is. For buckets, this is always storage#bucket.

User-provided labels, in key/value pairs.

The bucket's lifecycle configuration. See lifecycle management for more information.

The location of the bucket. Object data for objects in the bucket resides in physical storage within this region. Defaults to US. See the developer's guide for the authoritative list.

The type of the bucket location.

The bucket's logging configuration, which defines the destination bucket and optional name prefix for the current bucket's logs.

The metadata generation of this bucket.

The name of the bucket.

The owner of the bucket. This is always the project team's owner group.

Apply a predefined set of access controls to this bucket.

Apply a predefined set of default object access controls to this bucket.

A valid API project identifier.

Set of properties to return. Defaults to noAcl, unless the bucket resource specifies acl or defaultObjectAcl properties, when it defaults to full.

The project number of the project the bucket belongs to.

The bucket's retention policy. The retention policy enforces a minimum retention time for all objects contained in the bucket, based on their creation time. Any attempt to overwrite or delete objects younger than the retention period will result in a PERMISSION_DENIED error. An unlocked retention policy can be modified or removed from the bucket via a storage.buckets.update operation. A locked retention policy cannot be removed or shortened in duration for the lifetime of the bucket. Attempting to remove or decrease period of a locked retention policy will result in a PERMISSION_DENIED error.

The Recovery Point Objective (RPO) of this bucket. Set to ASYNC_TURBO to turn on Turbo Replication on a bucket.

Reserved for future use.

The URI of this bucket.

The bucket's default storage class, used whenever no storageClass is specified for a newly-created object. This defines how objects in the bucket are stored and determines the SLA and the cost of storage. Values include MULTI_REGIONAL, REGIONAL, STANDARD, NEARLINE, COLDLINE, ARCHIVE, and DURABLE_REDUCED_AVAILABILITY. If this value is not specified when the bucket is created, it will default to STANDARD. For more information, see storage classes.

The creation time of the bucket in RFC 3339 format.

The modification time of the bucket in RFC 3339 format.

The project to be billed for this request.

The bucket's versioning configuration.

The bucket's website configuration, controlling how the service behaves when accessing bucket contents as a web site. See the Static Website Examples for more information.