> 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-features/vault-connect-2/storage-and-kms-user-guide.md).

# Storage and KMS User Guide

## Vault Connect: Storage and KMS Configuration

Configuration guide

This guide explains how to grant AutoRABIT Vault Connect access to your AWS storage and encryption resources. Follow the option that matches your setup:

* **Option 1:** Fully AutoRABIT-managed storage and processing engines. No configuration required.
* **Option 2:** Customer-owned S3 bucket encrypted with a customer-owned KMS key.
* **Option 3:** AutoRABIT-managed storage encrypted with a customer-owned KMS key.

{% hint style="warning" %}
**Important:** Complete your storage and KMS setup before Vault Connect is enabled. The AutoRABIT access role is created only once, when the Vault Connect settings page is first opened, and it is based on the backup storage and KMS key configured at that time. Make sure the S3 bucket, region, and KMS key settings in AutoRABIT Vault are correct and final before enabling Vault Connect.
{% endhint %}

{% hint style="info" %}
**Prerequisites (Options 2 and 3):** AWS console access with permission to edit S3 bucket policies, lifecycle rules, and KMS key policies.
{% endhint %}

{% hint style="info" %}
**Note:** Account IDs, role ARNs, bucket names, key IDs, and user details are masked in the screenshots. Always copy the policies directly from your Vault Connect screen; they are generated specifically for your account.
{% endhint %}

## Option 1: Fully AutoRABIT-Managed (No Configuration Required)

Use this option when AutoRABIT manages both the backup storage and the processing engines. Vault Connect is enabled automatically. No bucket policy, KMS key policy, or lifecycle rules are required.

### Verify that Vault Connect is enabled

{% stepper %}
{% step %}

### Go to Vault Connect

In AutoRABIT Vault, go to **Settings > Vault Connect**.
{% endstep %}

{% step %}

### Confirm the configuration

Confirm that the status shows **Enabled** and the configuration route is **AutoRABIT-managed storage > AutoRABIT-managed engines**.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fjjf5C64cr5Tp4z3oFRz9%2Fimage.png?alt=media&amp;token=93449550-2fb4-4909-9f56-6045d775675e" alt=""><figcaption></figcaption></figure>

Vault Connect enabled with AutoRABIT-managed storage and engines
{% endstep %}
{% endstepper %}

## Option 2: Customer-Owned S3 Bucket and KMS Key

Use this option when Vault Connect reads backups from an S3 bucket in your AWS account that is encrypted with your own customer-managed KMS key (SSE-KMS).

{% stepper %}
{% step %}

### Copy the AutoRABIT access role and bucket policy

In AutoRABIT Vault, go to **Settings > Vault Connect**. In **Grant storage access**, review the storage summary and the AutoRABIT access role ARN.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FVlqNvjmoAREINlY9CncW%2Fimage.png?alt=media&amp;token=274e002a-7abb-4679-a11a-2a9349241f87" alt=""><figcaption></figcaption></figure>

Vault Connect – Grant storage access

Under **1. Add bucket policy**, click the eye icon to review the policy, then click **Copy Policy**.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FLPtpqEyBDaNEeDSXl0Fr%2Fimage.png?alt=media&amp;token=87ac60c1-79b1-467e-ba6d-98131ce62d93" alt=""><figcaption></figcaption></figure>

Bucket policy generated by Vault Connect
{% endstep %}

{% step %}

### Apply the bucket policy in AWS S3

In the AWS console, open **Amazon S3 > Buckets >** your bucket **> Permissions**.

Under **Bucket policy**, click **Edit**, paste the copied policy, and click **Save changes**. If the bucket already has a policy, add the Vault Connect statements to the existing policy instead of replacing it.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F3TTwuzG2ptfTQxJk9k1J%2Fimage.png?alt=media&amp;token=33c24106-d882-4be1-9cea-e7769849b4bf" alt=""><figcaption></figcaption></figure>

Bucket policy applied in AWS S3
{% endstep %}

{% step %}

### Copy the KMS key policy

Back in Vault Connect, under **2. Add KMS key policy**, click the eye icon to review the policy, then click **Copy Policy**.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FOgm84BYXZz0ReibMmVTR%2Fimage.png?alt=media&amp;token=c8c1eb9b-43e5-416a-b85c-a6aeeca7c327" alt=""><figcaption></figcaption></figure>

KMS key policy generated by Vault Connect
{% endstep %}

{% step %}

### Apply the KMS key policy in AWS KMS

In the AWS console, open **KMS > Customer managed keys**, select the key used by the bucket, and click **Edit policy**.

Add the copied statement to the Statement array of the existing key policy and click **Save changes**. Do not remove the existing statements (for example, Enable IAM User Permissions).

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fm2K6xvQrG0lGxGfg8YdS%2Fimage.png?alt=media&amp;token=edcf44cd-cc1e-4796-969c-5a0e001a521e" alt=""><figcaption></figcaption></figure>

KMS key policy updated in AWS KMS
{% endstep %}

{% step %}

### Review the recommended lifecycle rules

In Vault Connect, under **Recommended lifecycle rules**, click **View rules** to see the lifecycle guidance.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F7bxW6dEwGNLFXwVCrrKf%2Fimage.png?alt=media&amp;token=b403baa3-a4ba-4b89-9e6e-46229385e6cd" alt=""><figcaption></figcaption></figure>

Recommended lifecycle rules

| **Lifecycle rule name**       | **Prefix**                | **Expire after** |
| ----------------------------- | ------------------------- | ---------------- |
| vault-connect-staging-expiry  | vault-connect/staging/    | 7 days           |
| vault-connect-progress-expiry | vault-connect/\_progress/ | 1 day            |
| {% endstep %}                 |                           |                  |

{% step %}

### Create the lifecycle rules in AWS S3

In the AWS console, open your bucket, go to **Management > Lifecycle rules**, and click **Create lifecycle rule**. Create both rules below.

#### Rule 1: vault-connect-staging-expiry

Enter the rule name vault-connect-staging-expiry, select **Limit the scope of this rule using one or more filters**, and enter the prefix vault-connect/staging/.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FYLBwy2xmxHhrnNTtdlSn%2Fimage.png?alt=media&amp;token=f5a3f946-79e1-4b77-b60c-e7f92e6c5d34" alt=""><figcaption></figcaption></figure>

Rule 1 – name, scope, and prefix

Under **Lifecycle rule actions**, select **Expire current versions of objects**, set **Days after object creation** to **7**, and save the rule.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F7PiAJhjZ9JqnGyfZbRq3%2Fimage.png?alt=media&amp;token=cd0aaee0-c447-4a9f-a1c2-987538578758" alt=""><figcaption></figcaption></figure>

Rule 1 – expire after 7 days

#### Rule 2: vault-connect-progress-expiry

Enter the rule name vault-connect-progress-expiry, select **Limit the scope of this rule using one or more filters**, and enter the prefix vault-connect/\_progress/.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FeNr8A3X4t983xQSG9wvU%2Fimage.png?alt=media&amp;token=247a52d2-449d-414c-919a-2b25784e77a4" alt=""><figcaption></figcaption></figure>

Rule 2 – name, scope, and prefix

Under **Lifecycle rule actions**, select **Expire current versions of objects**, set **Days after object creation** to **1**, and save the rule.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2F0k1zFzZux6f4VllDiDty%2Fimage.png?alt=media&amp;token=1e64cd80-103e-498d-81d3-da2362137d55" alt=""><figcaption></figcaption></figure>

Rule 2 – expire after 1 day

Confirm that both rules appear as **Enabled** in the lifecycle rules list.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FW324qrLXlHvJvkBXNZZ0%2Fimage.png?alt=media&amp;token=395e3eed-43a4-46d0-983b-82cacdbbccb9" alt=""><figcaption></figcaption></figure>

Lifecycle rules enabled on the bucket
{% endstep %}

{% step %}

### Verify and activate

In Vault Connect, click **Continue to Verification**.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FxjEuKol2SBNdwrUTn7sf%2Fimage.png?alt=media&amp;token=6a0c2fd0-d6cf-416f-84ce-4e6baa643185" alt=""><figcaption></figcaption></figure>

Continue to Verification

Vault Connect assumes the access role, checks read/write access to the bucket, and runs a test Athena query. This usually takes less than a minute.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FsDCKurWuepL27owPpS3e%2Fimage.png?alt=media&amp;token=ac60747b-4b59-4462-9d91-7e9a7ad5cf6a" alt=""><figcaption></figcaption></figure>

Verification in progress

When all checks pass, the status changes to **Verified** and Vault Connect is active.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FgFCh6XqBI9zuLu9c4PJk%2Fimage.png?alt=media&amp;token=399e91fa-6d8a-4230-9a63-b17f9c090279" alt=""><figcaption></figcaption></figure>

Connection verified

{% hint style="info" %}
**Note:** If verification fails, Vault Connect identifies the denied resource and the checks that did not run. Review the bucket policy, KMS key policy, and lifecycle rules, then click Re-verify Connection.
{% endhint %}
{% endstep %}
{% endstepper %}

## Option 3: AutoRABIT-Managed Storage with Customer-Owned KMS Key

Use this option when your backups are stored in AutoRABIT-managed storage but encrypted with a KMS key in your AWS account. Only the KMS key policy is required.

{% stepper %}
{% step %}

### Open the managed configuration

In AutoRABIT Vault, go to **Settings > Vault Connect**. Under **Grant access to your KMS key**, review the AutoRABIT access role ARN.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FGUD6IgsLwV7QPHovRBZL%2Fimage.png?alt=media&amp;token=ad908d72-1361-42cc-bd6b-c0f0f9b7e988" alt=""><figcaption></figcaption></figure>

Vault Connect – Grant access to your KMS key
{% endstep %}

{% step %}

### Copy the KMS key policy

Under **Add KMS key policy**, click the eye icon to review the policy, then click **Copy Policy**.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2FGqeLkm9WeFTcrXepWlFl%2Fimage.png?alt=media&amp;token=60c8ac29-94c7-426f-ade3-9f97eaf64986" alt=""><figcaption></figcaption></figure>

KMS key policy generated by Vault Connect
{% endstep %}

{% step %}

### Apply the KMS key policy in AWS KMS

In the AWS console, open **KMS > Customer managed keys**, select your key, and click **Edit policy**.

Add the copied statement to the Statement array of the existing key policy and click **Save changes**.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fm2K6xvQrG0lGxGfg8YdS%2Fimage.png?alt=media&amp;token=edcf44cd-cc1e-4796-969c-5a0e001a521e" alt=""><figcaption></figcaption></figure>

KMS key policy updated in AWS KMS
{% endstep %}

{% step %}

### Verify and activate

In Vault Connect, click **Verify Connection**.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fdigtl1eYLqCfUvvDQlgi%2Fimage.png?alt=media&amp;token=d7abc522-1b2c-4fd7-a44b-88a0593120a0" alt=""><figcaption></figcaption></figure>

Verification in progress

When all checks pass, the status changes to **Verified** and Vault Connect is active.

<figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fizn5mWHZ2zbpGQSO5xTF%2Fimage.png?alt=media&amp;token=36cdd1bb-d6c7-497b-8e1b-6463650f8164" alt=""><figcaption></figcaption></figure>

Connection verified
{% endstep %}
{% endstepper %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/product-guides/vault/vault-features/vault-connect-2/storage-and-kms-user-guide.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
