Unique identifier for the access key.
Human-readable name for the access key.
Must be at least 1 characters long
Must be at most 200 characters long
Account the access key belongs to, or null if that account no longer exists.
Must be at least 1 characters long
Stored account linkage. A numeric user ID for local accounts or a SID for directory services accounts.
Whether the access key belongs to a local user account rather than a directory services one.
The S3 access key id clients sign requests with.
Must match regular expression:^[A-Z0-9]{16,128}$
The S3 secret access key. Readable only by administrators holding SHARING_S3_WRITE; redacted for everyone else. null when the secret was lost to a configuration restore without the secret seed.
Whether the access key may be used. A disabled key is refused by the S3 service.
Expiration timestamp for the access key or null for no expiration.
Timestamp when the access key was created.
Time the S3 service last accepted a request signed with this key, or null if the key has never been used. The S3 service reports this at intervals, so a recent request can be absent for a short time. This field is read-only.
Whether this access key may create and delete buckets through the S3 protocol. Setting it requires the account that owns the key to hold the SHARING_S3_WRITE role, checked when a call turns it on. It scopes the key, not the account: an account may hold several access keys, and leaving this off on one of them affects neither its other keys nor its own access to sharing.s3.create.
Effective state of the access key. Only ENABLED keys are usable. DISABLED was set by an administrator, EXPIRED passed its expiration, USER_MISSING belongs to a directory account that no longer resolves (a deleted local account takes its keys with it), and SECRET_LOST lost its secret to a configuration restore without the secret seed and must be rotated.
Unique identifier for the access key.
Human-readable name for the access key.
Must be at least 1 characters long
Must be at most 200 characters long
Account the access key belongs to, or null if that account no longer exists.
Must be at least 1 characters long
Stored account linkage. A numeric user ID for local accounts or a SID for directory services accounts.
Whether the access key belongs to a local user account rather than a directory services one.
The S3 access key id clients sign requests with.
Must match regular expression:^[A-Z0-9]{16,128}$
The S3 secret access key. Readable only by administrators holding SHARING_S3_WRITE; redacted for everyone else. null when the secret was lost to a configuration restore without the secret seed.
Whether the access key may be used. A disabled key is refused by the S3 service.
Expiration timestamp for the access key or null for no expiration.
Timestamp when the access key was created.
Time the S3 service last accepted a request signed with this key, or null if the key has never been used. The S3 service reports this at intervals, so a recent request can be absent for a short time. This field is read-only.
Whether this access key may create and delete buckets through the S3 protocol. Setting it requires the account that owns the key to hold the SHARING_S3_WRITE role, checked when a call turns it on. It scopes the key, not the account: an account may hold several access keys, and leaving this off on one of them affects neither its other keys nor its own access to sharing.s3.create.
Effective state of the access key. Only ENABLED keys are usable. DISABLED was set by an administrator, EXPIRED passed its expiration, USER_MISSING belongs to a directory account that no longer resolves (a deleted local account takes its keys with it), and SECRET_LOST lost its secret to a configuration restore without the secret seed and must be rotated.