Integrate your AWS account with Zesty

This topic describes how to integrate (“onboard”) your AWS account with Zesty. That may mean creating or updating an IAM role or uploading a CUR.

This procedure is done once per AWS account or when you want to update permissions or add a CUR on an already-integrated account. If your account has the relevant permissions, you do not need to run this procedure.

Specifically, use this procedure to:

• see potential savings with Commitment Manager

• update your Master Payer account permissions from ‘Read-only’ to ‘managed’

• see potential savings with Zesty Disk

• deploy Zesty Disk (on standalone instances)

  Regardless of the use, the procedure is nearly identical, with minor differences pointed out within.

To easily integrate a master account and its subaccounts for Zesty Disk, see Onboarding Accounts to Zesty with StackSets.

Prerequisites

• Access to the Zesty platform

• User account in AWS with permissions to add Zesty IAM roles with the required roles

• (To see potential savings or to update your Master Payer account permissions, you also need a Zesty-compatible CUR, as described in Create a legacy CUR.)

To Integrate your AWS account with Zesty:

1. From the Zesty platform main menu, select Organization Settings > Accounts.
   The Accounts page displays existing accounts.

2. Enable Zesty permissions, by doing one of the following:

   • To create a new account, click Add account.

     On the Choose provider page of the Create new account wizard, click AWS (the cloud provider to link with Zesty).
     Skip to the next step.

   • To add additional permissions to an existing account, from that account’s Action menu, click Update permissions.
     If you are adding permissions to a Master Payer account, it is marked with a blue badge:
     

3. Configure the connection:

   This step uses CloudFormation to configure permissions for Zesty.

   1. In Step 1 (Permission presets), do the following:

      • If you are configuring Zesty Disk, select Zesty Disk.

        You can select other permissions, too.

      • If you are configuring Commitment Manager, select Read-only.
        You can select other permissions, too.

      • If you are updating your permissions from ‘Read-only’ to ‘Managed,’ select Managed.
        This automatically selects the necessary permissions.
        You can select other permissions, too.

   2. In Step 2 (CUR), do the following:

      • If you are configuring Zesty Disk, select I will provide the CUR later/it is a sub-account. (If you have already enabled a CUR, you can select I have a CUR report already enabled and then enter the S3 bucket name.)

      • If you are configuring or updating Commitment Manager, select I have a CUR report already enabled and then enter the S3 bucket name.

   3. In Step 3, select a region in which to create the stack.

      Your choice in this step is not relevant.

   4. In Step 4, approve the permissions to be assigned to the IAM role.

   5. In Step 5, click Create IAM role.

      The AWS Quick create stack page is opened.

   6. In the AWS console, scroll down to the Capabilities section.

   7. Select I acknowledge that AWS CloudFormation might create IAM resources with custom names, then click Create stack.

      In the AWS console, the CloudFormation > Stacks page is displayed.

      The Events tab shows the different events taking place. When the process is done, the CREATE_COMPLETE status is displayed.

4. Verify the integration:

   1. From the AWS console CloudFormation page, select the Outputs tab and copy the ARN value.

      If the ARN value is not displayed, refresh the table until it is.

   2. In the Zesty platform Verify Integration screen of the wizard, paste the entire ARN value (including arn:) in the ROLE ARN field, then click Connect.

   3. Unless you have more accounts to connect, click No.

Zesty takes a few moments to finalize the integration and prepare the new account.

The Create new account wizard is completed.

If you receive an error message or require other assistance, contact Customer Support.