> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/vault/vault-faqs/common-restore-errors-and-solutions/s3-iam-policy-permissions.md). # S3 IAM Policy Permissions

Modifying an Existing IAM Policy to Add S3 Bucket Versioning Permissions

s3:GetBucketVersioning | s3:PutBucketVersioning | s3:ListBucketVersions

## 1. Overview This guide shows how to modify an existing IAM policy in the AWS Management Console by adding the following Amazon S3 permissions to it: 1. s3:GetBucketVersioning — read the versioning state of a bucket 2. s3:PutBucketVersioning — enable or suspend versioning on a bucket 3. s3:ListBucketVersions — list object versions in a bucket {% hint style="info" %} Note: The screenshots in this document are illustrative recreations of the AWS console. Names such as my-s3-access-policy and my-example-bucket are placeholders — replace them with your actual policy and bucket names. {% endhint %} ## 2. Step-by-Step Instructions ### Step 1 — Sign in and open the IAM service Sign in to the AWS Management Console and open the IAM service (search for “IAM” in the Services search bar). ### Step 2 — Go to Access management → Policies In the left navigation pane, expand Access management and choose Policies.

IAM left navigation — Access management → Policies (illustrative)

### Step 3 — Search for and select the policy In the search box, type the policy name and select it from the results list by clicking the policy name.

Policies list — search for the policy and click its name (illustrative)

### Step 4 — Open the Permissions tab and click Edit On the policy detail page, make sure the Permissions tab is selected, then click Edit.

Policy detail page — Permissions tab → Edit (illustrative)

### Step 5 — Switch to the JSON tab In the policy editor, switch from Visual to JSON using the toggle at the top of the editor. The editor shows the policy's current JSON. ### Step 6 — Add the S3 versioning permissions to the existing policy Do not create a new policy — edit the JSON that is already in the editor. Locate the existing S3 statement and add the following three actions inside its "Action" array (remember to keep the commas between entries valid):

"s3:GetBucketVersioning",

"s3:PutBucketVersioning",

"s3:ListBucketVersions"

The example below shows an existing policy after the change — the highlighted lines are the only ones added; everything else stays exactly as it was:

JSON editor — the three actions added into the existing Action array (illustrative)

These three are bucket-level actions, so make sure the statement's Resource includes the bucket ARN itself (arn:aws:s3:::my-example-bucket) — not only the /\* object ARN. Choose Next, review the summary, and click Save changes. IAM saves the update as a new default version of the same policy, and it takes effect immediately for every user, group, and role the policy is attached to.

Review and save — the change becomes the default policy version (illustrative)

--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://knowledgebase.autorabit.com/product-guides/vault/vault-faqs/common-restore-errors-and-solutions/s3-iam-policy-permissions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.