Configure cross-account access using VPC endpoints in a shared VPC - Amazon Keyspaces (for Apache Cassandra)
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China (PDF).

Configure cross-account access using VPC endpoints in a shared VPC

You can create different Amazon Web Services accounts to separate resources from applications. For example, you can create one account for your Amazon Keyspaces tables, a different account for applications in a development environment, and another account for applications in a production environment. This topic walks you through the configuration steps required to set up cross-account access for Amazon Keyspaces using interface VPC endpoints in a shared VPC.

For detailed steps how to configure a VPC endpoint for Amazon Keyspaces, see Step 3: Create a VPC endpoint for Amazon Keyspaces.

In this example we use the following three accounts in a shared VPC:

  • Account A – This account contains infrastructure, including the VPC endpoints, the VPC subnets, and Amazon Keyspaces tables.

  • Account B – This account contains an application in a development environment that needs to connect to the Amazon Keyspaces table in Account A.

  • Account C – This account contains an application in a production environment that needs to connect to the Amazon Keyspaces table in Account A.

Diagram showing three different accounts in owned by the same organization in the same Amazon Web Services Region that use a shared VPC.

Account A is the account that contains the resources that Account B and Account C need to access, so Account A is the trusting account. Account B and Account C are the accounts with the principals that need access to the resources in Account A, so Account B and Account C are the trusted accounts. The trusting account grants the permissions to the trusted accounts by sharing an IAM role. The following procedure outlines the configuration steps required in Account A.

Configuration for Account A

  1. Use Amazon Resource Access Manager to create a resource share for the subnet and share the private subnet with Account B and Account C.

    Account B and Account C can now see and create resources in the subnet that has been shared with them.

  2. Create an Amazon Keyspaces private VPC endpoint powered by Amazon PrivateLink. This creates multiple endpoints across shared subnets and DNS entries for the Amazon Keyspaces service endpoint.

  3. Create an Amazon Keyspaces keyspace and table.

  4. Create an IAM role that has full access to the Amazon Keyspaces table, read access to the Amazon Keyspaces system tables, and is able to describe the Amazon EC2 VPC resources as shown in the following policy example.

    {
    "Version": "2012-10-17",
    "Statement": [
        {
            "Sid": "CrossAccountAccess",
            "Effect": "Allow",
            "Action": [
                "ec2:DescribeNetworkInterfaces",
                "ec2:DescribeVpcEndpoints",
                "cassandra:*"
            ],
            "Resource": "*"
        }
    ]
}

  5. Configure the IAM role trust policy that Account B and Account C can assume as trusted accounts as shown in the following example. 

    {
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Principal": {
                "AWS": "arn:aws:iam::111111111111:root"
            },
            "Action": "sts:AssumeRole",
            "Condition": {}
        }
    ]
}

    For more information about cross-account IAM policies, see Cross-account policies in the IAM User Guide.

Configuration in Account B and Account C

  1. In Account B and Account C, create new roles and attach the following policy that allows the principal to assume the shared role created in Account A.

    {
    "Version": "2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Principal": {
                "Service": "ec2.amazonaws.com"
            },
            "Action": "sts:AssumeRole"
        }
    ]
}

    Allowing the principal to assume the shared role is implemented using the AssumeRole API of the Amazon Security Token Service (Amazon STS). For more information, see Providing access to an IAM user in another Amazon Web Services account that you own in the IAM User Guide.

  2. In Account B and Account C, you can create applications that utilize the SIGV4 authentication plugin, which allows an application to assume the shared role to connect to the Amazon Keyspaces table located in Account A through the VPC endpoint in the shared VPC. For more information about the SIGV4 authentication plugin, see Creating credentials to access Amazon Keyspaces programmatically.