google-native.storage/v1.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 ID of the bucket. For buckets, the id and name properties are the same.

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.

The project number of the project the bucket belongs to.

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

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.

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 ID of the bucket. For buckets, the id and name properties are the same.

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.

The project number of the project the bucket belongs to.

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

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.

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 ID of the bucket. For buckets, the id and name properties are the same.

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.

The project number of the project the bucket belongs to.

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

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.

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 ID of the bucket. For buckets, the id and name properties are the same.

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.

The project number of the project the bucket belongs to.

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

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.

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 ID of the bucket. For buckets, the id and name properties are the same.

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.

The project number of the project the bucket belongs to.

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

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.

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 ID of the bucket. For buckets, the id and name properties are the same.

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.

The project number of the project the bucket belongs to.

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

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.

The provider-assigned unique ID for this managed resource.

The provider-assigned unique ID for this managed resource.

The provider-assigned unique ID for this managed resource.

The provider-assigned unique ID for this managed resource.

The provider-assigned unique ID for this managed resource.

The provider-assigned unique ID for this managed resource.

The name of the bucket.

The domain associated with the entity, if any.

The email address associated with the entity, if any.

The entity holding the permission, in one of the following forms:

• user-userId
• user-email
• group-groupId
• group-email
• domain-domain
• project-team-projectId
• allUsers
• allAuthenticatedUsers Examples:
• The user liz@example.com would be user-liz@example.com.
• The group example@googlegroups.com would be group-example@googlegroups.com.
• To refer to all members of the Google Apps for Business domain example.com, the entity would be domain-example.com.

The ID for the entity, if any.

HTTP 1.1 Entity tag for the access-control entry.

The ID of the access-control entry.

The kind of item this is. For bucket access control entries, this is always storage#bucketAccessControl.

The project team associated with the entity, if any.

The access permission for the entity.

The link to this access-control entry.

The name of the bucket.

The domain associated with the entity, if any.

The email address associated with the entity, if any.

The entity holding the permission, in one of the following forms:

• user-userId
• user-email
• group-groupId
• group-email
• domain-domain
• project-team-projectId
• allUsers
• allAuthenticatedUsers Examples:
• The user liz@example.com would be user-liz@example.com.
• The group example@googlegroups.com would be group-example@googlegroups.com.
• To refer to all members of the Google Apps for Business domain example.com, the entity would be domain-example.com.

The ID for the entity, if any.

HTTP 1.1 Entity tag for the access-control entry.

The ID of the access-control entry.

The kind of item this is. For bucket access control entries, this is always storage#bucketAccessControl.

The project team associated with the entity, if any.

The access permission for the entity.

The link to this access-control entry.

The name of the bucket.

The domain associated with the entity, if any.

The email address associated with the entity, if any.

The entity holding the permission, in one of the following forms:

• user-userId
• user-email
• group-groupId
• group-email
• domain-domain
• project-team-projectId
• allUsers
• allAuthenticatedUsers Examples:
• The user liz@example.com would be user-liz@example.com.
• The group example@googlegroups.com would be group-example@googlegroups.com.
• To refer to all members of the Google Apps for Business domain example.com, the entity would be domain-example.com.

The ID for the entity, if any.

HTTP 1.1 Entity tag for the access-control entry.

The ID of the access-control entry.

The kind of item this is. For bucket access control entries, this is always storage#bucketAccessControl.

The project team associated with the entity, if any.

The access permission for the entity.

The link to this access-control entry.

The name of the bucket.

The domain associated with the entity, if any.

The email address associated with the entity, if any.

The entity holding the permission, in one of the following forms:

• user-userId
• user-email
• group-groupId
• group-email
• domain-domain
• project-team-projectId
• allUsers
• allAuthenticatedUsers Examples:
• The user liz@example.com would be user-liz@example.com.
• The group example@googlegroups.com would be group-example@googlegroups.com.
• To refer to all members of the Google Apps for Business domain example.com, the entity would be domain-example.com.

The ID for the entity, if any.

HTTP 1.1 Entity tag for the access-control entry.

The ID of the access-control entry.

The kind of item this is. For bucket access control entries, this is always storage#bucketAccessControl.

The project team associated with the entity, if any.

The access permission for the entity.

The link to this access-control entry.

The name of the bucket.

The domain associated with the entity, if any.

The email address associated with the entity, if any.

The entity holding the permission, in one of the following forms:

• user-userId
• user-email
• group-groupId
• group-email
• domain-domain
• project-team-projectId
• allUsers
• allAuthenticatedUsers Examples:
• The user liz@example.com would be user-liz@example.com.
• The group example@googlegroups.com would be group-example@googlegroups.com.
• To refer to all members of the Google Apps for Business domain example.com, the entity would be domain-example.com.

The ID for the entity, if any.

HTTP 1.1 Entity tag for the access-control entry.

The ID of the access-control entry.

The kind of item this is. For bucket access control entries, this is always storage#bucketAccessControl.

The project team associated with the entity, if any.

The access permission for the entity.

The link to this access-control entry.

The name of the bucket.

The domain associated with the entity, if any.

The email address associated with the entity, if any.

The entity holding the permission, in one of the following forms:

• user-userId
• user-email
• group-groupId
• group-email
• domain-domain
• project-team-projectId
• allUsers
• allAuthenticatedUsers Examples:
• The user liz@example.com would be user-liz@example.com.
• The group example@googlegroups.com would be group-example@googlegroups.com.
• To refer to all members of the Google Apps for Business domain example.com, the entity would be domain-example.com.

The ID for the entity, if any.

HTTP 1.1 Entity tag for the access-control entry.

The ID of the access-control entry.

The kind of item this is. For bucket access control entries, this is always storage#bucketAccessControl.

The project team associated with the entity, if any.

The access permission for the entity.

The link to this access-control entry.

The project number.

The team.

The project number.

The team.

The project number.

The team.

The project number.

The team.

The project number.

The team.

The project number.

The team.

The project number.

The team.

The project number.

The team.

The project number.

The team.

The project number.

The team.

The project number.

The team.

The project number.

The team.

The name of the bucket.

The domain associated with the entity, if any.

The email address associated with the entity, if any.

The entity holding the permission, in one of the following forms:

• user-userId
• user-email
• group-groupId
• group-email
• domain-domain
• project-team-projectId
• allUsers
• allAuthenticatedUsers Examples:
• The user liz@example.com would be user-liz@example.com.
• The group example@googlegroups.com would be group-example@googlegroups.com.
• To refer to all members of the Google Apps for Business domain example.com, the entity would be domain-example.com.

The ID for the entity, if any.

HTTP 1.1 Entity tag for the access-control entry.

The kind of item this is. For bucket access control entries, this is always storage#bucketAccessControl.

The project team associated with the entity, if any.

The access permission for the entity.

The link to this access-control entry.

The name of the bucket.

The domain associated with the entity, if any.

The email address associated with the entity, if any.

The entity holding the permission, in one of the following forms:

• user-userId
• user-email
• group-groupId
• group-email
• domain-domain
• project-team-projectId
• allUsers
• allAuthenticatedUsers Examples:
• The user liz@example.com would be user-liz@example.com.
• The group example@googlegroups.com would be group-example@googlegroups.com.
• To refer to all members of the Google Apps for Business domain example.com, the entity would be domain-example.com.

The ID for the entity, if any.

HTTP 1.1 Entity tag for the access-control entry.

The kind of item this is. For bucket access control entries, this is always storage#bucketAccessControl.

The project team associated with the entity, if any.

The access permission for the entity.

The link to this access-control entry.

The name of the bucket.

The domain associated with the entity, if any.

The email address associated with the entity, if any.

The entity holding the permission, in one of the following forms:

• user-userId
• user-email
• group-groupId
• group-email
• domain-domain
• project-team-projectId
• allUsers
• allAuthenticatedUsers Examples:
• The user liz@example.com would be user-liz@example.com.
• The group example@googlegroups.com would be group-example@googlegroups.com.
• To refer to all members of the Google Apps for Business domain example.com, the entity would be domain-example.com.

The ID for the entity, if any.

HTTP 1.1 Entity tag for the access-control entry.

The kind of item this is. For bucket access control entries, this is always storage#bucketAccessControl.

The project team associated with the entity, if any.

The access permission for the entity.

The link to this access-control entry.

The name of the bucket.

The domain associated with the entity, if any.

The email address associated with the entity, if any.

The entity holding the permission, in one of the following forms:

• user-userId
• user-email
• group-groupId
• group-email
• domain-domain
• project-team-projectId
• allUsers
• allAuthenticatedUsers Examples:
• The user liz@example.com would be user-liz@example.com.
• The group example@googlegroups.com would be group-example@googlegroups.com.
• To refer to all members of the Google Apps for Business domain example.com, the entity would be domain-example.com.

The ID for the entity, if any.

HTTP 1.1 Entity tag for the access-control entry.

The kind of item this is. For bucket access control entries, this is always storage#bucketAccessControl.

The project team associated with the entity, if any.

The access permission for the entity.

The link to this access-control entry.

The name of the bucket.

The domain associated with the entity, if any.

The email address associated with the entity, if any.

The entity holding the permission, in one of the following forms:

• user-userId
• user-email
• group-groupId
• group-email
• domain-domain
• project-team-projectId
• allUsers
• allAuthenticatedUsers Examples:
• The user liz@example.com would be user-liz@example.com.
• The group example@googlegroups.com would be group-example@googlegroups.com.
• To refer to all members of the Google Apps for Business domain example.com, the entity would be domain-example.com.

The ID for the entity, if any.

HTTP 1.1 Entity tag for the access-control entry.

The kind of item this is. For bucket access control entries, this is always storage#bucketAccessControl.

The project team associated with the entity, if any.

The access permission for the entity.

The link to this access-control entry.

The name of the bucket.

The domain associated with the entity, if any.

The email address associated with the entity, if any.

The entity holding the permission, in one of the following forms:

• user-userId
• user-email
• group-groupId
• group-email
• domain-domain
• project-team-projectId
• allUsers
• allAuthenticatedUsers Examples:
• The user liz@example.com would be user-liz@example.com.
• The group example@googlegroups.com would be group-example@googlegroups.com.
• To refer to all members of the Google Apps for Business domain example.com, the entity would be domain-example.com.

The ID for the entity, if any.

HTTP 1.1 Entity tag for the access-control entry.

The kind of item this is. For bucket access control entries, this is always storage#bucketAccessControl.

The project team associated with the entity, if any.

The access permission for the entity.

The link to this access-control entry.

Whether or not Autoclass is enabled on this bucket

A date and time in RFC 3339 format representing the instant at which "enabled" was last toggled.

Whether or not Autoclass is enabled on this bucket

A date and time in RFC 3339 format representing the instant at which "enabled" was last toggled.

Whether or not Autoclass is enabled on this bucket

A date and time in RFC 3339 format representing the instant at which "enabled" was last toggled.

Whether or not Autoclass is enabled on this bucket

A date and time in RFC 3339 format representing the instant at which "enabled" was last toggled.

Whether or not Autoclass is enabled on this bucket

A date and time in RFC 3339 format representing the instant at which "enabled" was last toggled.

Whether or not Autoclass is enabled on this bucket

A date and time in RFC 3339 format representing the instant at which "enabled" was last toggled.

Whether or not Autoclass is enabled on this bucket

A date and time in RFC 3339 format representing the instant at which "enabled" was last toggled.

Whether or not Autoclass is enabled on this bucket

A date and time in RFC 3339 format representing the instant at which "enabled" was last toggled.

Whether or not Autoclass is enabled on this bucket

A date and time in RFC 3339 format representing the instant at which "enabled" was last toggled.

Whether or not Autoclass is enabled on this bucket

A date and time in RFC 3339 format representing the instant at which "enabled" was last toggled.

Whether or not Autoclass is enabled on this bucket

A date and time in RFC 3339 format representing the instant at which "enabled" was last toggled.

Whether or not Autoclass is enabled on this bucket

A date and time in RFC 3339 format representing the instant at which "enabled" was last toggled.

When set to true, Requester Pays is enabled for this bucket.

When set to true, Requester Pays is enabled for this bucket.

When set to true, Requester Pays is enabled for this bucket.

When set to true, Requester Pays is enabled for this bucket.

When set to true, Requester Pays is enabled for this bucket.

When set to true, Requester Pays is enabled for this bucket.

When set to true, Requester Pays is enabled for this bucket.

When set to true, Requester Pays is enabled for this bucket.

When set to true, Requester Pays is enabled for this bucket.

When set to true, Requester Pays is enabled for this bucket.

When set to true, Requester Pays is enabled for this bucket.

When set to true, Requester Pays is enabled for this bucket.

The value, in seconds, to return in the Access-Control-Max-Age header used in preflight responses.

The list of HTTP methods on which to include CORS response headers, (GET, OPTIONS, POST, etc) Note: "*" is permitted in the list of methods, and means "any method".

The list of Origins eligible to receive CORS response headers. Note: "*" is permitted in the list of origins, and means "any Origin".

The list of HTTP headers other than the simple response headers to give permission for the user-agent to share across domains.

The value, in seconds, to return in the Access-Control-Max-Age header used in preflight responses.

The list of HTTP methods on which to include CORS response headers, (GET, OPTIONS, POST, etc) Note: "*" is permitted in the list of methods, and means "any method".

The list of Origins eligible to receive CORS response headers. Note: "*" is permitted in the list of origins, and means "any Origin".

The list of HTTP headers other than the simple response headers to give permission for the user-agent to share across domains.

The value, in seconds, to return in the Access-Control-Max-Age header used in preflight responses.

The list of HTTP methods on which to include CORS response headers, (GET, OPTIONS, POST, etc) Note: "*" is permitted in the list of methods, and means "any method".

The list of Origins eligible to receive CORS response headers. Note: "*" is permitted in the list of origins, and means "any Origin".

The list of HTTP headers other than the simple response headers to give permission for the user-agent to share across domains.

The value, in seconds, to return in the Access-Control-Max-Age header used in preflight responses.

The list of HTTP methods on which to include CORS response headers, (GET, OPTIONS, POST, etc) Note: "*" is permitted in the list of methods, and means "any method".

The list of Origins eligible to receive CORS response headers. Note: "*" is permitted in the list of origins, and means "any Origin".

The list of HTTP headers other than the simple response headers to give permission for the user-agent to share across domains.

The value, in seconds, to return in the Access-Control-Max-Age header used in preflight responses.

The list of HTTP methods on which to include CORS response headers, (GET, OPTIONS, POST, etc) Note: "*" is permitted in the list of methods, and means "any method".

The list of Origins eligible to receive CORS response headers. Note: "*" is permitted in the list of origins, and means "any Origin".

The list of HTTP headers other than the simple response headers to give permission for the user-agent to share across domains.

The value, in seconds, to return in the Access-Control-Max-Age header used in preflight responses.

The list of HTTP methods on which to include CORS response headers, (GET, OPTIONS, POST, etc) Note: "*" is permitted in the list of methods, and means "any method".

The list of Origins eligible to receive CORS response headers. Note: "*" is permitted in the list of origins, and means "any Origin".

The list of HTTP headers other than the simple response headers to give permission for the user-agent to share across domains.

The value, in seconds, to return in the Access-Control-Max-Age header used in preflight responses.

The list of HTTP methods on which to include CORS response headers, (GET, OPTIONS, POST, etc) Note: "*" is permitted in the list of methods, and means "any method".

The list of Origins eligible to receive CORS response headers. Note: "*" is permitted in the list of origins, and means "any Origin".

The list of HTTP headers other than the simple response headers to give permission for the user-agent to share across domains.

The value, in seconds, to return in the Access-Control-Max-Age header used in preflight responses.

The list of HTTP methods on which to include CORS response headers, (GET, OPTIONS, POST, etc) Note: "*" is permitted in the list of methods, and means "any method".

The list of Origins eligible to receive CORS response headers. Note: "*" is permitted in the list of origins, and means "any Origin".

The list of HTTP headers other than the simple response headers to give permission for the user-agent to share across domains.

The value, in seconds, to return in the Access-Control-Max-Age header used in preflight responses.

The list of HTTP methods on which to include CORS response headers, (GET, OPTIONS, POST, etc) Note: "*" is permitted in the list of methods, and means "any method".

The list of Origins eligible to receive CORS response headers. Note: "*" is permitted in the list of origins, and means "any Origin".

The list of HTTP headers other than the simple response headers to give permission for the user-agent to share across domains.

The value, in seconds, to return in the Access-Control-Max-Age header used in preflight responses.

The list of HTTP methods on which to include CORS response headers, (GET, OPTIONS, POST, etc) Note: "*" is permitted in the list of methods, and means "any method".

The list of Origins eligible to receive CORS response headers. Note: "*" is permitted in the list of origins, and means "any Origin".

The list of HTTP headers other than the simple response headers to give permission for the user-agent to share across domains.

The value, in seconds, to return in the Access-Control-Max-Age header used in preflight responses.

The list of HTTP methods on which to include CORS response headers, (GET, OPTIONS, POST, etc) Note: "*" is permitted in the list of methods, and means "any method".

The list of Origins eligible to receive CORS response headers. Note: "*" is permitted in the list of origins, and means "any Origin".

The list of HTTP headers other than the simple response headers to give permission for the user-agent to share across domains.

The value, in seconds, to return in the Access-Control-Max-Age header used in preflight responses.

The list of HTTP methods on which to include CORS response headers, (GET, OPTIONS, POST, etc) Note: "*" is permitted in the list of methods, and means "any method".

The list of Origins eligible to receive CORS response headers. Note: "*" is permitted in the list of origins, and means "any Origin".

The list of HTTP headers other than the simple response headers to give permission for the user-agent to share across domains.

The list of regional locations in which data is placed.

The list of regional locations in which data is placed.

The list of regional locations in which data is placed.

The list of regional locations in which data is placed.

The list of regional locations in which data is placed.

The list of regional locations in which data is placed.

The list of regional locations in which data is placed.

The list of regional locations in which data is placed.

The list of regional locations in which data is placed.

The list of regional locations in which data is placed.

The list of regional locations in which data is placed.

The list of regional locations in which data is placed.

A Cloud KMS key that will be used to encrypt objects inserted into this bucket, if no encryption method is specified.

A Cloud KMS key that will be used to encrypt objects inserted into this bucket, if no encryption method is specified.

A Cloud KMS key that will be used to encrypt objects inserted into this bucket, if no encryption method is specified.

A Cloud KMS key that will be used to encrypt objects inserted into this bucket, if no encryption method is specified.

A Cloud KMS key that will be used to encrypt objects inserted into this bucket, if no encryption method is specified.

A Cloud KMS key that will be used to encrypt objects inserted into this bucket, if no encryption method is specified.

A Cloud KMS key that will be used to encrypt objects inserted into this bucket, if no encryption method is specified.

A Cloud KMS key that will be used to encrypt objects inserted into this bucket, if no encryption method is specified.

A Cloud KMS key that will be used to encrypt objects inserted into this bucket, if no encryption method is specified.

A Cloud KMS key that will be used to encrypt objects inserted into this bucket, if no encryption method is specified.

A Cloud KMS key that will be used to encrypt objects inserted into this bucket, if no encryption method is specified.

A Cloud KMS key that will be used to encrypt objects inserted into this bucket, if no encryption method is specified.

The bucket's uniform bucket-level access configuration. The feature was formerly known as Bucket Policy Only. For backward compatibility, this field will be populated with identical information as the uniformBucketLevelAccess field. We recommend using the uniformBucketLevelAccess field to enable and disable the feature.

The bucket's Public Access Prevention configuration. Currently, 'inherited' and 'enforced' are supported.

The bucket's uniform bucket-level access configuration.

The bucket's uniform bucket-level access configuration. The feature was formerly known as Bucket Policy Only. For backward compatibility, this field will be populated with identical information as the uniformBucketLevelAccess field. We recommend using the uniformBucketLevelAccess field to enable and disable the feature.

The bucket's Public Access Prevention configuration. Currently, 'inherited' and 'enforced' are supported.

The bucket's uniform bucket-level access configuration.

The bucket's uniform bucket-level access configuration. The feature was formerly known as Bucket Policy Only. For backward compatibility, this field will be populated with identical information as the uniformBucketLevelAccess field. We recommend using the uniformBucketLevelAccess field to enable and disable the feature.

The bucket's Public Access Prevention configuration. Currently, 'inherited' and 'enforced' are supported.

The bucket's uniform bucket-level access configuration.

The bucket's uniform bucket-level access configuration. The feature was formerly known as Bucket Policy Only. For backward compatibility, this field will be populated with identical information as the uniformBucketLevelAccess field. We recommend using the uniformBucketLevelAccess field to enable and disable the feature.

The bucket's Public Access Prevention configuration. Currently, 'inherited' and 'enforced' are supported.

The bucket's uniform bucket-level access configuration.

The bucket's uniform bucket-level access configuration. The feature was formerly known as Bucket Policy Only. For backward compatibility, this field will be populated with identical information as the uniformBucketLevelAccess field. We recommend using the uniformBucketLevelAccess field to enable and disable the feature.

The bucket's Public Access Prevention configuration. Currently, 'inherited' and 'enforced' are supported.

The bucket's uniform bucket-level access configuration.

The bucket's uniform bucket-level access configuration. The feature was formerly known as Bucket Policy Only. For backward compatibility, this field will be populated with identical information as the uniformBucketLevelAccess field. We recommend using the uniformBucketLevelAccess field to enable and disable the feature.

The bucket's Public Access Prevention configuration. Currently, 'inherited' and 'enforced' are supported.

The bucket's uniform bucket-level access configuration.

If set, access is controlled only by bucket-level or above IAM policies.

The deadline for changing iamConfiguration.bucketPolicyOnly.enabled from true to false in RFC 3339 format. iamConfiguration.bucketPolicyOnly.enabled may be changed from true to false until the locked time, after which the field is immutable.

If set, access is controlled only by bucket-level or above IAM policies.

The deadline for changing iamConfiguration.bucketPolicyOnly.enabled from true to false in RFC 3339 format. iamConfiguration.bucketPolicyOnly.enabled may be changed from true to false until the locked time, after which the field is immutable.

If set, access is controlled only by bucket-level or above IAM policies.

The deadline for changing iamConfiguration.bucketPolicyOnly.enabled from true to false in RFC 3339 format. iamConfiguration.bucketPolicyOnly.enabled may be changed from true to false until the locked time, after which the field is immutable.

If set, access is controlled only by bucket-level or above IAM policies.

The deadline for changing iamConfiguration.bucketPolicyOnly.enabled from true to false in RFC 3339 format. iamConfiguration.bucketPolicyOnly.enabled may be changed from true to false until the locked time, after which the field is immutable.

If set, access is controlled only by bucket-level or above IAM policies.

The deadline for changing iamConfiguration.bucketPolicyOnly.enabled from true to false in RFC 3339 format. iamConfiguration.bucketPolicyOnly.enabled may be changed from true to false until the locked time, after which the field is immutable.

If set, access is controlled only by bucket-level or above IAM policies.

The deadline for changing iamConfiguration.bucketPolicyOnly.enabled from true to false in RFC 3339 format. iamConfiguration.bucketPolicyOnly.enabled may be changed from true to false until the locked time, after which the field is immutable.

If set, access is controlled only by bucket-level or above IAM policies.

The deadline for changing iamConfiguration.bucketPolicyOnly.enabled from true to false in RFC 3339 format. iamConfiguration.bucketPolicyOnly.enabled may be changed from true to false until the locked time, after which the field is immutable.

If set, access is controlled only by bucket-level or above IAM policies.

The deadline for changing iamConfiguration.bucketPolicyOnly.enabled from true to false in RFC 3339 format. iamConfiguration.bucketPolicyOnly.enabled may be changed from true to false until the locked time, after which the field is immutable.

If set, access is controlled only by bucket-level or above IAM policies.

The deadline for changing iamConfiguration.bucketPolicyOnly.enabled from true to false in RFC 3339 format. iamConfiguration.bucketPolicyOnly.enabled may be changed from true to false until the locked time, after which the field is immutable.

If set, access is controlled only by bucket-level or above IAM policies.

The deadline for changing iamConfiguration.bucketPolicyOnly.enabled from true to false in RFC 3339 format. iamConfiguration.bucketPolicyOnly.enabled may be changed from true to false until the locked time, after which the field is immutable.

If set, access is controlled only by bucket-level or above IAM policies.

The deadline for changing iamConfiguration.bucketPolicyOnly.enabled from true to false in RFC 3339 format. iamConfiguration.bucketPolicyOnly.enabled may be changed from true to false until the locked time, after which the field is immutable.

If set, access is controlled only by bucket-level or above IAM policies.

The deadline for changing iamConfiguration.bucketPolicyOnly.enabled from true to false in RFC 3339 format. iamConfiguration.bucketPolicyOnly.enabled may be changed from true to false until the locked time, after which the field is immutable.

The bucket's uniform bucket-level access configuration. The feature was formerly known as Bucket Policy Only. For backward compatibility, this field will be populated with identical information as the uniformBucketLevelAccess field. We recommend using the uniformBucketLevelAccess field to enable and disable the feature.

The bucket's Public Access Prevention configuration. Currently, 'inherited' and 'enforced' are supported.

The bucket's uniform bucket-level access configuration.

The bucket's uniform bucket-level access configuration. The feature was formerly known as Bucket Policy Only. For backward compatibility, this field will be populated with identical information as the uniformBucketLevelAccess field. We recommend using the uniformBucketLevelAccess field to enable and disable the feature.

The bucket's Public Access Prevention configuration. Currently, 'inherited' and 'enforced' are supported.

The bucket's uniform bucket-level access configuration.

The bucket's uniform bucket-level access configuration. The feature was formerly known as Bucket Policy Only. For backward compatibility, this field will be populated with identical information as the uniformBucketLevelAccess field. We recommend using the uniformBucketLevelAccess field to enable and disable the feature.

The bucket's Public Access Prevention configuration. Currently, 'inherited' and 'enforced' are supported.

The bucket's uniform bucket-level access configuration.

The bucket's uniform bucket-level access configuration. The feature was formerly known as Bucket Policy Only. For backward compatibility, this field will be populated with identical information as the uniformBucketLevelAccess field. We recommend using the uniformBucketLevelAccess field to enable and disable the feature.

The bucket's Public Access Prevention configuration. Currently, 'inherited' and 'enforced' are supported.

The bucket's uniform bucket-level access configuration.

The bucket's uniform bucket-level access configuration. The feature was formerly known as Bucket Policy Only. For backward compatibility, this field will be populated with identical information as the uniformBucketLevelAccess field. We recommend using the uniformBucketLevelAccess field to enable and disable the feature.

The bucket's Public Access Prevention configuration. Currently, 'inherited' and 'enforced' are supported.

The bucket's uniform bucket-level access configuration.

The bucket's uniform bucket-level access configuration. The feature was formerly known as Bucket Policy Only. For backward compatibility, this field will be populated with identical information as the uniformBucketLevelAccess field. We recommend using the uniformBucketLevelAccess field to enable and disable the feature.

The bucket's Public Access Prevention configuration. Currently, 'inherited' and 'enforced' are supported.

The bucket's uniform bucket-level access configuration.

If set, access is controlled only by bucket-level or above IAM policies.

The deadline for changing iamConfiguration.uniformBucketLevelAccess.enabled from true to false in RFC 3339 format. iamConfiguration.uniformBucketLevelAccess.enabled may be changed from true to false until the locked time, after which the field is immutable.

If set, access is controlled only by bucket-level or above IAM policies.

The deadline for changing iamConfiguration.uniformBucketLevelAccess.enabled from true to false in RFC 3339 format. iamConfiguration.uniformBucketLevelAccess.enabled may be changed from true to false until the locked time, after which the field is immutable.

If set, access is controlled only by bucket-level or above IAM policies.

The deadline for changing iamConfiguration.uniformBucketLevelAccess.enabled from true to false in RFC 3339 format. iamConfiguration.uniformBucketLevelAccess.enabled may be changed from true to false until the locked time, after which the field is immutable.

If set, access is controlled only by bucket-level or above IAM policies.

The deadline for changing iamConfiguration.uniformBucketLevelAccess.enabled from true to false in RFC 3339 format. iamConfiguration.uniformBucketLevelAccess.enabled may be changed from true to false until the locked time, after which the field is immutable.

If set, access is controlled only by bucket-level or above IAM policies.

The deadline for changing iamConfiguration.uniformBucketLevelAccess.enabled from true to false in RFC 3339 format. iamConfiguration.uniformBucketLevelAccess.enabled may be changed from true to false until the locked time, after which the field is immutable.

If set, access is controlled only by bucket-level or above IAM policies.

The deadline for changing iamConfiguration.uniformBucketLevelAccess.enabled from true to false in RFC 3339 format. iamConfiguration.uniformBucketLevelAccess.enabled may be changed from true to false until the locked time, after which the field is immutable.

If set, access is controlled only by bucket-level or above IAM policies.

The deadline for changing iamConfiguration.uniformBucketLevelAccess.enabled from true to false in RFC 3339 format. iamConfiguration.uniformBucketLevelAccess.enabled may be changed from true to false until the locked time, after which the field is immutable.

If set, access is controlled only by bucket-level or above IAM policies.

The deadline for changing iamConfiguration.uniformBucketLevelAccess.enabled from true to false in RFC 3339 format. iamConfiguration.uniformBucketLevelAccess.enabled may be changed from true to false until the locked time, after which the field is immutable.

If set, access is controlled only by bucket-level or above IAM policies.

The deadline for changing iamConfiguration.uniformBucketLevelAccess.enabled from true to false in RFC 3339 format. iamConfiguration.uniformBucketLevelAccess.enabled may be changed from true to false until the locked time, after which the field is immutable.

If set, access is controlled only by bucket-level or above IAM policies.

The deadline for changing iamConfiguration.uniformBucketLevelAccess.enabled from true to false in RFC 3339 format. iamConfiguration.uniformBucketLevelAccess.enabled may be changed from true to false until the locked time, after which the field is immutable.

If set, access is controlled only by bucket-level or above IAM policies.

The deadline for changing iamConfiguration.uniformBucketLevelAccess.enabled from true to false in RFC 3339 format. iamConfiguration.uniformBucketLevelAccess.enabled may be changed from true to false until the locked time, after which the field is immutable.

If set, access is controlled only by bucket-level or above IAM policies.

The deadline for changing iamConfiguration.uniformBucketLevelAccess.enabled from true to false in RFC 3339 format. iamConfiguration.uniformBucketLevelAccess.enabled may be changed from true to false until the locked time, after which the field is immutable.

A lifecycle management rule, which is made of an action to take and the condition(s) under which the action will be taken.

A lifecycle management rule, which is made of an action to take and the condition(s) under which the action will be taken.

A lifecycle management rule, which is made of an action to take and the condition(s) under which the action will be taken.

A lifecycle management rule, which is made of an action to take and the condition(s) under which the action will be taken.

A lifecycle management rule, which is made of an action to take and the condition(s) under which the action will be taken.

A lifecycle management rule, which is made of an action to take and the condition(s) under which the action will be taken.

A lifecycle management rule, which is made of an action to take and the condition(s) under which the action will be taken.

A lifecycle management rule, which is made of an action to take and the condition(s) under which the action will be taken.

A lifecycle management rule, which is made of an action to take and the condition(s) under which the action will be taken.

A lifecycle management rule, which is made of an action to take and the condition(s) under which the action will be taken.

A lifecycle management rule, which is made of an action to take and the condition(s) under which the action will be taken.

A lifecycle management rule, which is made of an action to take and the condition(s) under which the action will be taken.

The action to take.

The condition(s) under which the action will be taken.

The action to take.

The condition(s) under which the action will be taken.

The action to take.

The condition(s) under which the action will be taken.

The action to take.

The condition(s) under which the action will be taken.

The action to take.

The condition(s) under which the action will be taken.

The action to take.

The condition(s) under which the action will be taken.

Target storage class. Required iff the type of the action is SetStorageClass.

Type of the action. Currently, only Delete, SetStorageClass, and AbortIncompleteMultipartUpload are supported.

Target storage class. Required iff the type of the action is SetStorageClass.

Type of the action. Currently, only Delete, SetStorageClass, and AbortIncompleteMultipartUpload are supported.

Target storage class. Required iff the type of the action is SetStorageClass.

Type of the action. Currently, only Delete, SetStorageClass, and AbortIncompleteMultipartUpload are supported.

Target storage class. Required iff the type of the action is SetStorageClass.

Type of the action. Currently, only Delete, SetStorageClass, and AbortIncompleteMultipartUpload are supported.

Target storage class. Required iff the type of the action is SetStorageClass.

Type of the action. Currently, only Delete, SetStorageClass, and AbortIncompleteMultipartUpload are supported.

Target storage class. Required iff the type of the action is SetStorageClass.

Type of the action. Currently, only Delete, SetStorageClass, and AbortIncompleteMultipartUpload are supported.

Target storage class. Required iff the type of the action is SetStorageClass.

Type of the action. Currently, only Delete, SetStorageClass, and AbortIncompleteMultipartUpload are supported.

Target storage class. Required iff the type of the action is SetStorageClass.

Type of the action. Currently, only Delete, SetStorageClass, and AbortIncompleteMultipartUpload are supported.

Target storage class. Required iff the type of the action is SetStorageClass.

Type of the action. Currently, only Delete, SetStorageClass, and AbortIncompleteMultipartUpload are supported.

Target storage class. Required iff the type of the action is SetStorageClass.

Type of the action. Currently, only Delete, SetStorageClass, and AbortIncompleteMultipartUpload are supported.

Target storage class. Required iff the type of the action is SetStorageClass.

Type of the action. Currently, only Delete, SetStorageClass, and AbortIncompleteMultipartUpload are supported.

Target storage class. Required iff the type of the action is SetStorageClass.

Type of the action. Currently, only Delete, SetStorageClass, and AbortIncompleteMultipartUpload are supported.

Age of an object (in days). This condition is satisfied when an object reaches the specified age.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when an object is created before midnight of the specified date in UTC.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when the custom time on an object is before this date in UTC.

Number of days elapsed since the user-specified timestamp set on an object. The condition is satisfied if the days elapsed is at least this number. If no custom timestamp is specified on an object, the condition does not apply.

Number of days elapsed since the noncurrent timestamp of an object. The condition is satisfied if the days elapsed is at least this number. This condition is relevant only for versioned objects. The value of the field must be a nonnegative integer. If it's zero, the object version will become eligible for Lifecycle action as soon as it becomes noncurrent.

Relevant only for versioned objects. If the value is true, this condition matches live objects; if the value is false, it matches archived objects.

A regular expression that satisfies the RE2 syntax. This condition is satisfied when the name of the object matches the RE2 pattern. Note: This feature is currently in the "Early Access" launch stage and is only available to a whitelisted set of users; that means that this feature may be changed in backward-incompatible ways and that it is not guaranteed to be released.

List of object name prefixes. This condition will be satisfied when at least one of the prefixes exactly matches the beginning of the object name.

Objects having any of the storage classes specified by this condition will be matched. Values include MULTI_REGIONAL, REGIONAL, NEARLINE, COLDLINE, ARCHIVE, STANDARD, and DURABLE_REDUCED_AVAILABILITY.

List of object name suffixes. This condition will be satisfied when at least one of the suffixes exactly matches the end of the object name.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when the noncurrent time on an object is before this date in UTC. This condition is relevant only for versioned objects.

Relevant only for versioned objects. If the value is N, this condition is satisfied when there are at least N versions (including the live version) newer than this version of the object.

Age of an object (in days). This condition is satisfied when an object reaches the specified age.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when an object is created before midnight of the specified date in UTC.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when the custom time on an object is before this date in UTC.

Number of days elapsed since the user-specified timestamp set on an object. The condition is satisfied if the days elapsed is at least this number. If no custom timestamp is specified on an object, the condition does not apply.

Number of days elapsed since the noncurrent timestamp of an object. The condition is satisfied if the days elapsed is at least this number. This condition is relevant only for versioned objects. The value of the field must be a nonnegative integer. If it's zero, the object version will become eligible for Lifecycle action as soon as it becomes noncurrent.

Relevant only for versioned objects. If the value is true, this condition matches live objects; if the value is false, it matches archived objects.

A regular expression that satisfies the RE2 syntax. This condition is satisfied when the name of the object matches the RE2 pattern. Note: This feature is currently in the "Early Access" launch stage and is only available to a whitelisted set of users; that means that this feature may be changed in backward-incompatible ways and that it is not guaranteed to be released.

List of object name prefixes. This condition will be satisfied when at least one of the prefixes exactly matches the beginning of the object name.

Objects having any of the storage classes specified by this condition will be matched. Values include MULTI_REGIONAL, REGIONAL, NEARLINE, COLDLINE, ARCHIVE, STANDARD, and DURABLE_REDUCED_AVAILABILITY.

List of object name suffixes. This condition will be satisfied when at least one of the suffixes exactly matches the end of the object name.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when the noncurrent time on an object is before this date in UTC. This condition is relevant only for versioned objects.

Relevant only for versioned objects. If the value is N, this condition is satisfied when there are at least N versions (including the live version) newer than this version of the object.

Age of an object (in days). This condition is satisfied when an object reaches the specified age.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when an object is created before midnight of the specified date in UTC.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when the custom time on an object is before this date in UTC.

Number of days elapsed since the user-specified timestamp set on an object. The condition is satisfied if the days elapsed is at least this number. If no custom timestamp is specified on an object, the condition does not apply.

Number of days elapsed since the noncurrent timestamp of an object. The condition is satisfied if the days elapsed is at least this number. This condition is relevant only for versioned objects. The value of the field must be a nonnegative integer. If it's zero, the object version will become eligible for Lifecycle action as soon as it becomes noncurrent.

Relevant only for versioned objects. If the value is true, this condition matches live objects; if the value is false, it matches archived objects.

A regular expression that satisfies the RE2 syntax. This condition is satisfied when the name of the object matches the RE2 pattern. Note: This feature is currently in the "Early Access" launch stage and is only available to a whitelisted set of users; that means that this feature may be changed in backward-incompatible ways and that it is not guaranteed to be released.

List of object name prefixes. This condition will be satisfied when at least one of the prefixes exactly matches the beginning of the object name.

Objects having any of the storage classes specified by this condition will be matched. Values include MULTI_REGIONAL, REGIONAL, NEARLINE, COLDLINE, ARCHIVE, STANDARD, and DURABLE_REDUCED_AVAILABILITY.

List of object name suffixes. This condition will be satisfied when at least one of the suffixes exactly matches the end of the object name.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when the noncurrent time on an object is before this date in UTC. This condition is relevant only for versioned objects.

Relevant only for versioned objects. If the value is N, this condition is satisfied when there are at least N versions (including the live version) newer than this version of the object.

Age of an object (in days). This condition is satisfied when an object reaches the specified age.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when an object is created before midnight of the specified date in UTC.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when the custom time on an object is before this date in UTC.

Number of days elapsed since the user-specified timestamp set on an object. The condition is satisfied if the days elapsed is at least this number. If no custom timestamp is specified on an object, the condition does not apply.

Number of days elapsed since the noncurrent timestamp of an object. The condition is satisfied if the days elapsed is at least this number. This condition is relevant only for versioned objects. The value of the field must be a nonnegative integer. If it's zero, the object version will become eligible for Lifecycle action as soon as it becomes noncurrent.

Relevant only for versioned objects. If the value is true, this condition matches live objects; if the value is false, it matches archived objects.

A regular expression that satisfies the RE2 syntax. This condition is satisfied when the name of the object matches the RE2 pattern. Note: This feature is currently in the "Early Access" launch stage and is only available to a whitelisted set of users; that means that this feature may be changed in backward-incompatible ways and that it is not guaranteed to be released.

List of object name prefixes. This condition will be satisfied when at least one of the prefixes exactly matches the beginning of the object name.

Objects having any of the storage classes specified by this condition will be matched. Values include MULTI_REGIONAL, REGIONAL, NEARLINE, COLDLINE, ARCHIVE, STANDARD, and DURABLE_REDUCED_AVAILABILITY.

List of object name suffixes. This condition will be satisfied when at least one of the suffixes exactly matches the end of the object name.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when the noncurrent time on an object is before this date in UTC. This condition is relevant only for versioned objects.

Relevant only for versioned objects. If the value is N, this condition is satisfied when there are at least N versions (including the live version) newer than this version of the object.

Age of an object (in days). This condition is satisfied when an object reaches the specified age.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when an object is created before midnight of the specified date in UTC.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when the custom time on an object is before this date in UTC.

Number of days elapsed since the user-specified timestamp set on an object. The condition is satisfied if the days elapsed is at least this number. If no custom timestamp is specified on an object, the condition does not apply.

Number of days elapsed since the noncurrent timestamp of an object. The condition is satisfied if the days elapsed is at least this number. This condition is relevant only for versioned objects. The value of the field must be a nonnegative integer. If it's zero, the object version will become eligible for Lifecycle action as soon as it becomes noncurrent.

Relevant only for versioned objects. If the value is true, this condition matches live objects; if the value is false, it matches archived objects.

A regular expression that satisfies the RE2 syntax. This condition is satisfied when the name of the object matches the RE2 pattern. Note: This feature is currently in the "Early Access" launch stage and is only available to a whitelisted set of users; that means that this feature may be changed in backward-incompatible ways and that it is not guaranteed to be released.

List of object name prefixes. This condition will be satisfied when at least one of the prefixes exactly matches the beginning of the object name.

Objects having any of the storage classes specified by this condition will be matched. Values include MULTI_REGIONAL, REGIONAL, NEARLINE, COLDLINE, ARCHIVE, STANDARD, and DURABLE_REDUCED_AVAILABILITY.

List of object name suffixes. This condition will be satisfied when at least one of the suffixes exactly matches the end of the object name.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when the noncurrent time on an object is before this date in UTC. This condition is relevant only for versioned objects.

Relevant only for versioned objects. If the value is N, this condition is satisfied when there are at least N versions (including the live version) newer than this version of the object.

Age of an object (in days). This condition is satisfied when an object reaches the specified age.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when an object is created before midnight of the specified date in UTC.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when the custom time on an object is before this date in UTC.

Number of days elapsed since the user-specified timestamp set on an object. The condition is satisfied if the days elapsed is at least this number. If no custom timestamp is specified on an object, the condition does not apply.

Number of days elapsed since the noncurrent timestamp of an object. The condition is satisfied if the days elapsed is at least this number. This condition is relevant only for versioned objects. The value of the field must be a nonnegative integer. If it's zero, the object version will become eligible for Lifecycle action as soon as it becomes noncurrent.

Relevant only for versioned objects. If the value is true, this condition matches live objects; if the value is false, it matches archived objects.

A regular expression that satisfies the RE2 syntax. This condition is satisfied when the name of the object matches the RE2 pattern. Note: This feature is currently in the "Early Access" launch stage and is only available to a whitelisted set of users; that means that this feature may be changed in backward-incompatible ways and that it is not guaranteed to be released.

List of object name prefixes. This condition will be satisfied when at least one of the prefixes exactly matches the beginning of the object name.

Objects having any of the storage classes specified by this condition will be matched. Values include MULTI_REGIONAL, REGIONAL, NEARLINE, COLDLINE, ARCHIVE, STANDARD, and DURABLE_REDUCED_AVAILABILITY.

List of object name suffixes. This condition will be satisfied when at least one of the suffixes exactly matches the end of the object name.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when the noncurrent time on an object is before this date in UTC. This condition is relevant only for versioned objects.

Relevant only for versioned objects. If the value is N, this condition is satisfied when there are at least N versions (including the live version) newer than this version of the object.

Age of an object (in days). This condition is satisfied when an object reaches the specified age.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when an object is created before midnight of the specified date in UTC.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when the custom time on an object is before this date in UTC.

Number of days elapsed since the user-specified timestamp set on an object. The condition is satisfied if the days elapsed is at least this number. If no custom timestamp is specified on an object, the condition does not apply.

Number of days elapsed since the noncurrent timestamp of an object. The condition is satisfied if the days elapsed is at least this number. This condition is relevant only for versioned objects. The value of the field must be a nonnegative integer. If it's zero, the object version will become eligible for Lifecycle action as soon as it becomes noncurrent.

Relevant only for versioned objects. If the value is true, this condition matches live objects; if the value is false, it matches archived objects.

A regular expression that satisfies the RE2 syntax. This condition is satisfied when the name of the object matches the RE2 pattern. Note: This feature is currently in the "Early Access" launch stage and is only available to a whitelisted set of users; that means that this feature may be changed in backward-incompatible ways and that it is not guaranteed to be released.

List of object name prefixes. This condition will be satisfied when at least one of the prefixes exactly matches the beginning of the object name.

Objects having any of the storage classes specified by this condition will be matched. Values include MULTI_REGIONAL, REGIONAL, NEARLINE, COLDLINE, ARCHIVE, STANDARD, and DURABLE_REDUCED_AVAILABILITY.

List of object name suffixes. This condition will be satisfied when at least one of the suffixes exactly matches the end of the object name.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when the noncurrent time on an object is before this date in UTC. This condition is relevant only for versioned objects.

Relevant only for versioned objects. If the value is N, this condition is satisfied when there are at least N versions (including the live version) newer than this version of the object.

Age of an object (in days). This condition is satisfied when an object reaches the specified age.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when an object is created before midnight of the specified date in UTC.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when the custom time on an object is before this date in UTC.

Number of days elapsed since the user-specified timestamp set on an object. The condition is satisfied if the days elapsed is at least this number. If no custom timestamp is specified on an object, the condition does not apply.

Number of days elapsed since the noncurrent timestamp of an object. The condition is satisfied if the days elapsed is at least this number. This condition is relevant only for versioned objects. The value of the field must be a nonnegative integer. If it's zero, the object version will become eligible for Lifecycle action as soon as it becomes noncurrent.

Relevant only for versioned objects. If the value is true, this condition matches live objects; if the value is false, it matches archived objects.

A regular expression that satisfies the RE2 syntax. This condition is satisfied when the name of the object matches the RE2 pattern. Note: This feature is currently in the "Early Access" launch stage and is only available to a whitelisted set of users; that means that this feature may be changed in backward-incompatible ways and that it is not guaranteed to be released.

List of object name prefixes. This condition will be satisfied when at least one of the prefixes exactly matches the beginning of the object name.

Objects having any of the storage classes specified by this condition will be matched. Values include MULTI_REGIONAL, REGIONAL, NEARLINE, COLDLINE, ARCHIVE, STANDARD, and DURABLE_REDUCED_AVAILABILITY.

List of object name suffixes. This condition will be satisfied when at least one of the suffixes exactly matches the end of the object name.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when the noncurrent time on an object is before this date in UTC. This condition is relevant only for versioned objects.

Relevant only for versioned objects. If the value is N, this condition is satisfied when there are at least N versions (including the live version) newer than this version of the object.

Age of an object (in days). This condition is satisfied when an object reaches the specified age.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when an object is created before midnight of the specified date in UTC.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when the custom time on an object is before this date in UTC.

Number of days elapsed since the user-specified timestamp set on an object. The condition is satisfied if the days elapsed is at least this number. If no custom timestamp is specified on an object, the condition does not apply.

Number of days elapsed since the noncurrent timestamp of an object. The condition is satisfied if the days elapsed is at least this number. This condition is relevant only for versioned objects. The value of the field must be a nonnegative integer. If it's zero, the object version will become eligible for Lifecycle action as soon as it becomes noncurrent.

Relevant only for versioned objects. If the value is true, this condition matches live objects; if the value is false, it matches archived objects.

A regular expression that satisfies the RE2 syntax. This condition is satisfied when the name of the object matches the RE2 pattern. Note: This feature is currently in the "Early Access" launch stage and is only available to a whitelisted set of users; that means that this feature may be changed in backward-incompatible ways and that it is not guaranteed to be released.

List of object name prefixes. This condition will be satisfied when at least one of the prefixes exactly matches the beginning of the object name.

Objects having any of the storage classes specified by this condition will be matched. Values include MULTI_REGIONAL, REGIONAL, NEARLINE, COLDLINE, ARCHIVE, STANDARD, and DURABLE_REDUCED_AVAILABILITY.

List of object name suffixes. This condition will be satisfied when at least one of the suffixes exactly matches the end of the object name.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when the noncurrent time on an object is before this date in UTC. This condition is relevant only for versioned objects.

Relevant only for versioned objects. If the value is N, this condition is satisfied when there are at least N versions (including the live version) newer than this version of the object.

Age of an object (in days). This condition is satisfied when an object reaches the specified age.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when an object is created before midnight of the specified date in UTC.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when the custom time on an object is before this date in UTC.

Number of days elapsed since the user-specified timestamp set on an object. The condition is satisfied if the days elapsed is at least this number. If no custom timestamp is specified on an object, the condition does not apply.

Number of days elapsed since the noncurrent timestamp of an object. The condition is satisfied if the days elapsed is at least this number. This condition is relevant only for versioned objects. The value of the field must be a nonnegative integer. If it's zero, the object version will become eligible for Lifecycle action as soon as it becomes noncurrent.

Relevant only for versioned objects. If the value is true, this condition matches live objects; if the value is false, it matches archived objects.

A regular expression that satisfies the RE2 syntax. This condition is satisfied when the name of the object matches the RE2 pattern. Note: This feature is currently in the "Early Access" launch stage and is only available to a whitelisted set of users; that means that this feature may be changed in backward-incompatible ways and that it is not guaranteed to be released.

List of object name prefixes. This condition will be satisfied when at least one of the prefixes exactly matches the beginning of the object name.

Objects having any of the storage classes specified by this condition will be matched. Values include MULTI_REGIONAL, REGIONAL, NEARLINE, COLDLINE, ARCHIVE, STANDARD, and DURABLE_REDUCED_AVAILABILITY.

List of object name suffixes. This condition will be satisfied when at least one of the suffixes exactly matches the end of the object name.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when the noncurrent time on an object is before this date in UTC. This condition is relevant only for versioned objects.

Relevant only for versioned objects. If the value is N, this condition is satisfied when there are at least N versions (including the live version) newer than this version of the object.

Age of an object (in days). This condition is satisfied when an object reaches the specified age.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when an object is created before midnight of the specified date in UTC.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when the custom time on an object is before this date in UTC.

Number of days elapsed since the user-specified timestamp set on an object. The condition is satisfied if the days elapsed is at least this number. If no custom timestamp is specified on an object, the condition does not apply.

Number of days elapsed since the noncurrent timestamp of an object. The condition is satisfied if the days elapsed is at least this number. This condition is relevant only for versioned objects. The value of the field must be a nonnegative integer. If it's zero, the object version will become eligible for Lifecycle action as soon as it becomes noncurrent.

Relevant only for versioned objects. If the value is true, this condition matches live objects; if the value is false, it matches archived objects.

A regular expression that satisfies the RE2 syntax. This condition is satisfied when the name of the object matches the RE2 pattern. Note: This feature is currently in the "Early Access" launch stage and is only available to a whitelisted set of users; that means that this feature may be changed in backward-incompatible ways and that it is not guaranteed to be released.

List of object name prefixes. This condition will be satisfied when at least one of the prefixes exactly matches the beginning of the object name.

Objects having any of the storage classes specified by this condition will be matched. Values include MULTI_REGIONAL, REGIONAL, NEARLINE, COLDLINE, ARCHIVE, STANDARD, and DURABLE_REDUCED_AVAILABILITY.

List of object name suffixes. This condition will be satisfied when at least one of the suffixes exactly matches the end of the object name.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when the noncurrent time on an object is before this date in UTC. This condition is relevant only for versioned objects.

Relevant only for versioned objects. If the value is N, this condition is satisfied when there are at least N versions (including the live version) newer than this version of the object.

Age of an object (in days). This condition is satisfied when an object reaches the specified age.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when an object is created before midnight of the specified date in UTC.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when the custom time on an object is before this date in UTC.

Number of days elapsed since the user-specified timestamp set on an object. The condition is satisfied if the days elapsed is at least this number. If no custom timestamp is specified on an object, the condition does not apply.

Number of days elapsed since the noncurrent timestamp of an object. The condition is satisfied if the days elapsed is at least this number. This condition is relevant only for versioned objects. The value of the field must be a nonnegative integer. If it's zero, the object version will become eligible for Lifecycle action as soon as it becomes noncurrent.

Relevant only for versioned objects. If the value is true, this condition matches live objects; if the value is false, it matches archived objects.

A regular expression that satisfies the RE2 syntax. This condition is satisfied when the name of the object matches the RE2 pattern. Note: This feature is currently in the "Early Access" launch stage and is only available to a whitelisted set of users; that means that this feature may be changed in backward-incompatible ways and that it is not guaranteed to be released.

List of object name prefixes. This condition will be satisfied when at least one of the prefixes exactly matches the beginning of the object name.

Objects having any of the storage classes specified by this condition will be matched. Values include MULTI_REGIONAL, REGIONAL, NEARLINE, COLDLINE, ARCHIVE, STANDARD, and DURABLE_REDUCED_AVAILABILITY.

List of object name suffixes. This condition will be satisfied when at least one of the suffixes exactly matches the end of the object name.

A date in RFC 3339 format with only the date part (for instance, "2013-01-15"). This condition is satisfied when the noncurrent time on an object is before this date in UTC. This condition is relevant only for versioned objects.

Relevant only for versioned objects. If the value is N, this condition is satisfied when there are at least N versions (including the live version) newer than this version of the object.