Configure backup for multi-account access in AWS


Cloud Backup enables you to create backup files in an AWS account that is different than where your source Cloud Volumes ONTAP volumes reside. And both of those accounts can be different than the account where the Cloud Manager Connector resides.

These steps are required only when you are backing up Cloud Volumes ONTAP data to Amazon S3.

Follow the steps below to set up your configuration in this manner.

Set up VPC peering between accounts

  1. Log in to second account and Create Peering Connection:

    1. Select a local VPC: Select the VPC of the second account.

    2. Select another VPC: Enter the account ID of the first account.

    3. Select the Region where the Cloud Manager Connector is running. In this test setup both accounts are running in same region.

    4. VPC ID: Log into first account and enter the acceptor VPC ID. This is the VPC ID of the Cloud Manager Connector.

      screenshot aws peer1

      A Success dialog displays.

      screenshot aws peer2

      The status of the peering connection shows as Pending Acceptance.

      screenshot aws peer3

  2. Log into the first account and accept the peering request:

    screenshot aws peer4

    screenshot aws peer5

    1. Click Yes.

      screenshot aws peer6

      The connection now shows as Active. We have also added a Name tag to identify the peering connection called cbs-multi-account.

      screenshot aws peer7

    2. Refresh the peering connection in the second account and notice that the status changes to Active.

      screenshot aws peer8

Add a route to the route tables in both accounts

  1. Go to VPC > Subnet > Route table.

    screenshot aws route1

  2. Click on the Routes tab.

    screenshot aws route2

  3. Click Edit routes.

    screenshot aws route3

  4. Click Add route, and from the Target drop-down list select Peering Connection, and then select the peering connection that you created.

    1. In the Destination, enter the other account’s subnet CIDR.

      screenshot aws route4

    2. Click Save routes and a Success dialog displays.

      screenshot aws route5

Add the second AWS account credentials in Cloud Manager

  1. Add the second AWS account, for example, Saran-XCP-Dev.

    screenshot aws second account1

  2. In the Discover Cloud Volumes ONTAP page, select the newly added credentials.

    screenshot aws second account2

  3. Select the Cloud Volumes ONTAP system you want to discover from second account. You can also deploy a new Cloud Volumes ONTAP system in the second account.

    screenshot aws second account3

    The Cloud Volumes ONTAP system from the second account is now added to Cloud Manager which is running in a different account.

    screenshot aws second account4

Enable backup in the other AWS account

  1. In Cloud Manager, enable backup for the Cloud Volumes ONTAP system running in the first account, but select the second account as the location for creating the backup files.

    screenshot aws pick second account1

  2. Then select a backup policy and the volumes you want to back up, and Cloud Backup attempts to create a new bucket in the selected account.

    However, adding the bucket to the Cloud Volumes ONTAP system will fail because Cloud Backup uses the instance profile to add the bucket and the Cloud Manager instance profile doesn’t have access to the resources in the second account.

  3. Get the working environment ID for the Cloud Volumes ONTAP system.

    screenshot aws onprem we id

    Cloud Backup creates every bucket with the prefix Netapp-backup- and will include the working environment ID; for example: 87ULeA10

  4. In the EC2 portal, go to S3 and search for the bucket with name ending with 87uLeA10 and you’ll see the bucket name displayed as Netapp-backup-vsa87uLeA10.

    screenshot aws find bucket

  5. Click on the bucket, then click the Permissions tab, and then click Edit in the Bucket policy section.

    screenshot aws bucket policy

  6. Add a bucket policy for the newly created bucket to provide access to the Cloud Manager’s AWS account, and then Save the changes.

      "Version": "2012-10-17",
      "Statement": [
          "Sid": "PublicRead",
          "Effect": "Allow",
          "Principal": {
            "AWS": "arn:aws:iam::464262061435:root"
          "Action": [
          "Resource": [

    Note that "AWS": "arn:aws:iam::464262061435:root" gives complete access this bucket for all resources in account 464262061435. If you want to reduce it to specific role, level, you can update the policy with specific role(s). If you are adding individual roles, ensure that occm role also added, otherwise backups will not get updated in the Cloud Backup UI.

    For example: "AWS": "arn:aws:iam::464262061435:role/cvo-instance-profile-version10-d8e-IamInstanceRole-IKJPJ1HC2E7R"

  7. Retry enabling Cloud Backup on the Cloud Volumes ONTAP system and this time it should be successful.