> For the complete documentation index, see [llms.txt](https://docs.archera.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archera.ai/help-center/aws-onboarding/upgrading-the-archera-aws-integration-from-visibility-only-to-commitment-management.md).
# Upgrading the Archera AWS Integration from Visibility Only to Commitment Management
AWS customers who onboarded onto Archera using the **Visibility Only** (`read-only` access) can upgrade to **Commitment Management** (write access) simply by updating their current `ArcheraAI` CloudFormation stack with the following information.
1. Change the CloudFormation template URL from the `ReservedAI-Read` Template URL to the `ReservedAI-Write` Template URL
{% hint style="info" %}
**ReservedAI-Write Template URL:**
{% code overflow="wrap" %}
```
https://archera-cloudformation-production.s3.us-east-1.amazonaws.com/ReservedAI-Write-Cloudformation.template
```
{% endcode %}
{% endhint %}
2. Replace the `ReservedAIPrincipal` CloudFormation Parameter from `arn:aws:iam::967800896805:user/reserved-read` to
{% code overflow="wrap" %}
```
arn:aws:iam::967800896805:user/reserved-write
```
{% endcode %}
{% hint style="warning" %}
Please do not modify the `ExternalId` parameter within the CloudFormation stack, as it is critical to the integration with the Archera portal.
{% endhint %}
Refer to [#upgrade-from-visibility-only-to-commitment-management-with-aws-cloudformation](#upgrade-from-visibility-only-to-commitment-management-with-aws-cloudformation "mention")for step-by-step procedure to make the upgrade from Visibility Only to Commitment Management.
#### Upgrade from Visibility Only to Commitment Management with AWS CloudFormation
1. Sign in to the AWS console for your AWS management account.
2. Navigate to AWS CloudFormation.
3. Identify and select the CloudFormation Stack named `ArcheraAI` .
4. Navigate to the `Parameters` tab in the right pane. Ensure the `ReservedAIPrincipal` reads `arn:aws:iam::967800896805:user/reserved-read`
5. With the `ArcheraAI` stack selected, click on `Update stack` on the top right of the page.
6. From the dropdown, choose `Make a direct update`.
7. On the `Update Stack` page, click on `Replace existing template` and then select `Amazon S3 URL` under the Specify template section. Once the selection is made, enter the following Amazon S3 URL in the text field and click Next.
{% hint style="info" %}
Amazon S3 URL:
{% code overflow="wrap" %}
```
https://archera-cloudformation-production.s3.us-east-1.amazonaws.com/ReservedAI-Write-Cloudformation.template
```
{% endcode %}
{% endhint %}
8. On the next page (`Specify stack details`), update the `ReservedAIPrincipal` from `arn:aws:iam::967800896805:user/reserved-read` to
{% code overflow="wrap" %}
```
arn:aws:iam::967800896805:user/reserved-write
```
{% endcode %}
9. Click Next.
10. On the `Configure stack options` page, leave the defaults as-is, and scroll to the bottom of the page.
At the bottom of the page, check the box `I acknowledge that AWS CloudFormation might create IAM resources with custom names` and click Next.
11. On the `Review ArcheraAI` page, ensure the following values
1. In Step 1: Specify template, `Template URL` should now reflect the `ReservedAI-Write-Cloudformation.template` URL
2. In Step 2: Specify stack details, `ReservedAIPrincipal` should now read `arn:aws:iam::967800896805:user/reserved-write`
12. Once you have reviewed these values, scroll to the bottom of the page to review the `Change set preview` that highlights that the resource `ReservedAIRole` will be modified and replaced with the write permissions. Click `Submit`.
13. Once submitted, the stack status changes to `UPDATE_IN_PROGRESS` as shown below.
14. In a minute, once the stack update is complete, the status changes to `UPDATE_COMPLETE`
15. To verify the change took effect, navigate to the following URL and search for `ReservedAI`. You should now see the updated IAM role name, `ReservedAI-Write`.
{% code overflow="wrap" %}
```
https://us-east-1.console.aws.amazon.com/iam/home?region=us-east-1#/roles
```
{% endcode %}
With the updated IAM role with write permissions, you should now be able to manage commitments in the Archera portal.
{% hint style="info" %}
To verify the health of the AWS integration, navigate to the Archera portal.
{% endhint %}
---
# 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://docs.archera.ai/help-center/aws-onboarding/upgrading-the-archera-aws-integration-from-visibility-only-to-commitment-management.md?ask=&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.
