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

ReservedAI-Write Template URL:

https://archera-cloudformation-production.s3.us-east-1.amazonaws.com/ReservedAI-Write-Cloudformation.template

1. Replace the ReservedAIPrincipal CloudFormation Parameter from arn:aws:iam::967800896805:user/reserved-read to

arn:aws:iam::967800896805:user/reserved-write

Please do not modify the ExternalId parameter within the CloudFormation stack, as it is critical to the integration with the Archera portal.

Refer to Upgrade from Visibility Only to Commitment Management with AWS CloudFormationfor 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 .

1. Navigate to the Parameters tab in the right pane. Ensure the ReservedAIPrincipal reads arn:aws:iam::967800896805:user/reserved-read

1. With the ArcheraAI stack selected, click on Update stack on the top right of the page.

1. From the dropdown, choose Make a direct update.

1. 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.

Amazon S3 URL:

https://archera-cloudformation-production.s3.us-east-1.amazonaws.com/ReservedAI-Write-Cloudformation.template

1. On the next page (Specify stack details), update the ReservedAIPrincipal from arn:aws:iam::967800896805:user/reserved-read to

arn:aws:iam::967800896805:user/reserved-write

1. Click Next.

2. 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.

1. 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

1. 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.

1. Once submitted, the stack status changes to UPDATE_IN_PROGRESS as shown below.

1. In a minute, once the stack update is complete, the status changes to UPDATE_COMPLETE

1. 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.

https://us-east-1.console.aws.amazon.com/iam/home?region=us-east-1#/roles

With the updated IAM role with write permissions, you should now be able to manage commitments in the Archera portal.

To verify the health of the AWS integration, navigate to the Archera portal.

Navigate to the In-App AWS Integration