Security in Object Storage

Who may do what (IAM), what is audited, how objects are encrypted at rest, and who can reach a bucket.

Last updated 18 November 2026View as Markdown

IAM actions

Every signed request, through the console, the API or an S3 client, is checked against your IAM policies and the bucket policy; an unsigned request, against the bucket policy alone. A bucket's resource name is rn:ews::<org>:s3:bucket/<name>, an object's rn:ews::<org>:s3:bucket/<name>/object/<key>; object storage has no region segment.

ActionAccessWhat it allows
s3:ListBucketsReadList the buckets of the organization
s3:GetBucketReadDescribe a bucket
s3:CreateBucketWriteCreate a bucket
s3:DeleteBucketWrite · destructiveDelete an empty bucket
s3:ListObjectsReadList the object keys and sizes in a bucket
s3:GetObjectRead · sensitiveRead the contents of an object
s3:PutObjectWrite · destructiveUpload an object, including multipart uploads
s3:DeleteObjectWrite · destructiveDelete an object
s3:AbortMultipartUploadWrite · destructiveAbandon a multipart upload and discard its parts
s3:GetBucketVersioningReadRead whether a bucket keeps old versions of its objects
s3:PutBucketVersioningWrite · destructiveTurn versioning on or suspend it
s3:ListBucketVersionsReadList every version and delete marker in a bucket
s3:GetLifecycleConfigurationReadRead the rules that expire or clean up objects
s3:PutLifecycleConfigurationWrite · destructiveSet or remove the rules that expire or clean up objects
s3:GetBucketCORSReadRead which websites may call the bucket from a browser
s3:PutBucketCORSWrite · destructiveSet or remove which websites may call the bucket from a browser
s3:GetBucketObjectLockConfigurationReadRead a locked bucket's default retention
s3:PutBucketObjectLockConfigurationWrite · destructiveSet a locked bucket's default retention
s3:GetBucketPolicyReadRead the bucket policy, which can make objects public
s3:PutBucketPolicyWrite · destructiveSet the bucket policy; with block public access off it can make objects public
s3:DeleteBucketPolicyWrite · destructiveRemove the bucket policy
s3:GetBucketPublicAccessBlockReadRead whether the bucket blocks public access
s3:PutBucketPublicAccessBlockWrite · destructiveTurn block public access on or off for the bucket
s3:GetBucketWebsiteReadRead the static website configuration and custom domains
s3:PutBucketWebsiteWriteServe the bucket as a static website, and add custom domains
s3:DeleteBucketWebsiteWrite · destructiveStop serving the bucket as a website, or remove a custom domain
s3:GetReplicationConfigurationReadRead the bucket’s replication rules and how far replication has got
s3:PutReplicationConfigurationWriteReplicate the bucket’s objects to another bucket (also needs PutObject on the destination)
s3:DeleteReplicationConfigurationWrite · destructiveStop replicating the bucket (replicas already made are kept)
s3:GetBucketRemoteCopyReadRead whether a bucket on a storage cluster keeps a copy in another location, and what still waits to be copied
s3:PutBucketRemoteCopyWrite · destructiveTurn the copy in another location on or off for a bucket on a storage cluster (off: the copy is deleted after a grace period)
s3:GetEncryptionConfigurationReadRead which key encrypts the bucket’s objects
s3:PutEncryptionConfigurationWriteChoose the key that encrypts the bucket’s objects: the platform key or a KMS key (also needs kms:Encrypt on it)
s3:GetObjectVersionRead · sensitiveRead a specific earlier version of an object
s3:DeleteObjectVersionWrite · destructiveDelete a specific version of an object for good
s3:GetObjectRetentionReadRead how long an object version is locked
s3:PutObjectRetentionWrite · destructiveLock an object version until a date, or extend the lock
s3:BypassGovernanceRetentionWrite · destructiveShorten or remove a governance-mode lock, or delete under one
s3:GetObjectLegalHoldReadRead whether an object version is under legal hold
s3:PutObjectLegalHoldWrite · destructivePlace or lift a legal hold on an object version
s3:ListAccessKeysReadList S3 access keys — ids and status, never secrets
s3:CreateAccessKeyWriteCreate an S3 access key; the secret is shown once
s3:DeleteAccessKeyWrite · destructiveDelete an S3 access key
s3:CreateTemporaryCredentialsWriteCreate short-lived S3 credentials with a session token; they act with the caller’s permissions

Generated from the service’s IAM descriptor. Sensitive reads hand over secret material or source code and are recorded in the audit log like writes; destructive writes delete, overwrite or revoke.

  • s3:GetObject and s3:GetObjectVersion are sensitive reads: the generated ReadOnly policy leaves them out, and an allowed read through the API is recorded in the audit log.
  • Some operations check more than their own action: restoring a version also needs s3:GetObjectVersion; replication needs s3:PutObject on the destination; a KMS key needs kms:Encrypt on it; reading all public-access settings at once (GET /s3/api/buckets/{name}/public-access) needs s3:GetBucketPolicy, s3:GetBucketPublicAccessBlock and s3:GetBucketWebsite.
  • Removing CORS rules, lifecycle rules or the KMS key needs the setting's Put action, as on AWS.
  • A bucket's policy, Block public access, website and other settings can be changed only by your own organization, never through a bucket policy.
  • Access keys are IAM access keys: creating one is iam:CreateAccessKey (see Create an access key). Older S3 keys, made with s3:CreateAccessKey, keep working; temporary credentials are s3:CreateTemporaryCredentials.

How IAM policies, key scopes and bucket policies combine is in Access control.

Audit

Every write through the API is recorded in the audit log with its outcome, and so are sensitive reads and refused requests. An unsigned request, such as a public read, has nobody to record.

Encryption at rest

Every object is encrypted under its bucket's own data key, which is wrapped by the platform key or a KMS key of yours. See Encryption.

Encryption in transit

The endpoint, the bucket addresses and the website addresses answer over HTTPS.

Network exposure

A bucket is private: nothing in it can be read without a key while Block public access is on, which it is for every new bucket. A bucket policy can make objects public (see Make objects public), and a website serves only those public objects.

Did this page help you?