Bucket Policy
Bucket Policy is a JSON-based access policy language that allows you to create fine-grained permissions for your S3 buckets. With Bucket Policy, you can specify which users or services can access specific objects and what actions users can perform.
Note: Bucket Policy is supported for both contract-owned buckets and user-owned buckets. The maximum allowed Bucket Policy size for a contract-owned bucket is 1 MB, and for a user-owned bucket is 20 KB. For more information, see Bucket Types.
Note: Granting access of a user-owned bucket to another IONOS user does not make the bucket appear in the user's Object Storage in the DCD as the granted access does not translate to interface visibility due to the S3 protocol's architecture. To access the bucket, the user must utilize other S3 Tools.
Use cases
Use this feature to grant access to a specific user or group to only a subset of the objects in your bucket.
Restrict access to certain operations on your bucket, for example, list objects or remove object lock.
Using Bucket Policy, you can grant access based on conditions, such as the IP address of the user.
Create fine-grained access control rules to allow a user to put objects to a specific prefix in your bucket, but not to get objects from that prefix.
Bucket Policy alternatives
Use Bucket ACL and Object ACL instead of Bucket Policy if you need to define different sets of permissions such as
READ
,WRITE
, orFULL CONTROL
to many objects.Use Share Objects with Pre-Signed URLs to grant temporary access to authorized users for a specified period, after which the URL and the access to the object expire.
Policy format
A JSON-formatted bucket policy contains one or more policy statements. Within a policy's statement blocks, IONOS S3 Object Storage support for policy statement elements and their values is as follows:
Id (optional): A unique identifier for the policy. Example:
SamplePolicyID
.Version (required): Specifies the policy language version. The current version is
2012-10-17
.Statement (required): An array of individual statements, each specifying a permission.
Sid (optional): Custom string identifying the statement. For example,
Delegate certain actions to another user
.Action (required): Specifies the action(s) that are allowed or denied by the statement. See the Action section in the Request for the supported values. Example:
s3:GetObject
for allowing read access to objects.Effect (required): Specifies the effect of the statement. Possible values:
Allow
,Deny
.Resource (required): Must be one of the following:
arn:aws:s3:::<bucketName>
– For bucket actions (such as s3:ListBucket) and bucket subresource actions (such ass3:GetBucketAcl
).arn:aws:s3:::<bucketName>/*
orarn:aws:s3:::<bucketName>/<objectName>
– For object actions (such ass3:PutObject
).
Condition (optional): Specifies conditions for when the statement is in effect. See the Condition section in the Request for the supported values. Example:
{"aws:SourceIp": "123.123.123.0/24"}
restricts access to the specified IP range. For the list of supported bucket and object actions and condition values, see Supported Action Values.Principal (required): Specifies the user, account, service, or other entity to which the statement applies. For information specific to the bucket types, see the following:
"AWS": “*”
– Statement applies to all users (also known as 'anonymous access')."AWS": "arn:aws:iam:::user/<contractNumber>"
– Statement applies to the specified contract number."AWS": ["arn:aws:iam:::user/<contractNumber>:<UUID1>", "arn:aws:iam:::user/<contractNumber>:<UUID2>", …]
– Statement applies to the specified IONOS S3 Object Storage users.
Request
For more information, see Bucket Policy Examples and supported bucket and object actions and condition values.
DCD
Apply a Bucket Policy
You can apply Bucket Policy using the DCD by following these steps:
1. In the DCD, go to Menu > Storage > IONOS S3 Object Storage.
2. From the drop-down list in the Buckets tab, choose either Show user-owned buckets or Show contract-owned buckets depending on the bucket type you want to view.
3. From the Buckets list, choose the required S3 bucket and click the Bucket settings.
4. Go to the Bucket Policy setting under the Access management section and click Edit.
5. Copy and paste the provided JSON policy by replacing BUCKET_NAME
and USER_ID
with the actual values. Depending on the Bucket Types, replace the USER_ID
as follows:
Use Contract user ID for contract-owned buckets.
Use Canonical user ID for user-owned buckets.
Info: You can retrieve your user ID from the Key management section. For more information, see Retrieve User ID.
6. Click Save.
Result: This action grants the specified user full access to your bucket.
Info: You have the option to restrict actions, define the scope of access, or incorporate conditions into the Bucket Policy for more tailored control. For more information, see Examples.
Delete a Bucket Policy
You can delete a Bucket Policy at any time using the Bucket Policy section in the Bucket settings and click Delete.
Info: Removing a bucket policy is irreversible and it is advised to create a backup policy before deleting it.
IONOS S3 Object Storage API
Use the API to manage the Bucket Policy configuration.
CLI
Use the CLI to manage Bucket Policy.
Related feature
Block Public Access
If you have defined a bucket policy to grant public access, activating the Block Public Access feature will revoke these permissions, ensuring your data remains private. This feature is invaluable in scenarios where ensuring data privacy is paramount, or when you want to enforce a blanket no-public-access rule, irrespective of Bucket Policy settings. Currently, Block Public Access is available only via the IONOS S3 Object Storage API.
Last updated