AWS keyspaces high security documentation change
Summary
Added detailed cross-account configuration steps including IAM role creation, trust policies, VPC endpoint policies, and application setup instructions for secure access without shared VPC
Security assessment
The changes explicitly document security-focused configurations including IAM role trust relationships, principal ARN restrictions in VPC endpoint policies, and STS AssumeRole usage. These additions demonstrate how to securely implement cross-account access controls, preventing unauthorized access through proper policy configuration. The VPC endpoint policy's Condition block with ArnEquals specifically limits access to designated IAM roles from trusted accounts.
Diff
diff --git a/keyspaces/latest/devguide/access.cross-account.noVPC.setup.md b/keyspaces/latest/devguide/access.cross-account.noVPC.setup.md index e09f6e699..d509a971b 100644 --- a//keyspaces/latest/devguide/access.cross-account.noVPC.setup.md +++ b//keyspaces/latest/devguide/access.cross-account.noVPC.setup.md @@ -9 +9 @@ If the Amazon Keyspaces table and private VPC endpoint are owned by different ac -You can also access Amazon Keyspaces tables across different accounts without a shared VPC endpoint by using the public endpoint or deploying a private VPC endpoint in each account. When not using a shared VPC, each account requires its own VPC endpoint. In this example `Account A`, `Account B`, and `Account C` require their own VPC endpoints to access the table in `Account A`. When using VPC endpoints in this configuration, Amazon Keyspaces appears as a single node cluster to the Cassandra client driver instead of a multi-node cluster. Upon connection, the client driver reaches the DNS server which returns one of the available endpoints in the account’s VPC. But the client driver is not able to access the `system.peers` table to discover additional endpoints. Because there are less hosts available, the driver makes less connections. To adjust this, increase the connection pool setting of the driver by a factor of three. +You can also access Amazon Keyspaces tables across different accounts without a shared VPC endpoint by using the public endpoints or deploying a private VPC endpoint in each account. When not using a shared VPC, each account requires its own VPC endpoint. In this example `Account A`, `Account B`, and `Account C` require their own VPC endpoints to access the table in `Account A`. When using VPC endpoints in this configuration, Amazon Keyspaces appears as a single node cluster to the Cassandra client driver instead of a multi-node cluster. Upon connection, the client driver reaches the DNS server which returns one of the available endpoints in the account’s VPC. But the client driver is not able to access the `system.peers` table to discover additional endpoints. Because there are less hosts available, the driver makes less connections. To adjust this, increase the connection pool setting of the driver by a factor of three. @@ -12,0 +13,88 @@ You can also access Amazon Keyspaces tables across different accounts without a +`Account A` is the account that contains the resources (an Amazon Keyspaces table) 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 (an Amazon Keyspaces table) 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. Create an Amazon Keyspaces keyspace and table in `Account A`. + + 2. Create an IAM role in `Account A` that has full access to the Amazon Keyspaces table and read access to the Amazon Keyspaces system tables. + + { + "Version":"2012-10-17", + "Statement":[ + { + "Effect":"Allow", + "Action":[ + "cassandra:Select", + "cassandra:Modify" + ], + "Resource":[ + "arn:aws:cassandra:region:Account-A:/keyspace/mykeyspace/table/mytable", + "arn:aws:cassandra:region:Account-A:/keyspace/system*" + ] + } + ] + } + + 3. Configure a trust policy for the IAM role in `Account A` so that principals in `Account B` and `Account C` can assume the role as trusted accounts. This is shown in the following example. + + { + "Version": "2012-10-17", + "Statement": [ + { + "Effect": "Allow", + "Principal": { + "AWS": "arn:aws:iam::AccountB:role/Cross-Account-Role-B", + "AWS": "arn:aws:iam::AccountC:role/Cross-Account-Role-C" + }, + "Action": "sts:AssumeRole", + "Condition": {} + } + ] + } + +For more information about cross-account IAM policies, see [Cross-account policies](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_policies_evaluation-logic-cross-account.html) in the IAM User Guide. + + 4. Configure the VPC endpoint in `Account A` and attach permissions to the endpoint that allow the roles from `Account B` and `Account C` to assume the role in `Account A` using the VPC endpoint. These permissions are valid for the VPC endpoint that they are attached to. For more information about VPC endpoint policies, see [Controlling access to interface VPC endpoints for Amazon Keyspaces](./vpc-endpoints.html#interface-vpc-endpoints-policies). + + { + "Version": "2012-10-17", + "Statement": [ + { + "Sid": "Allow-access-from-specific-IAM-roles", + "Effect": "Allow", + "Principal": "*", + "Action": "cassandra:*", + "Resource": "*", + "Condition": { + "ArnEquals": { + "aws:PrincipalArn": "arn:aws:iam::AccountB:role/Cross-Account-Role-B", + "aws:PrincipalArn": "arn:aws:iam::AccountC:role/Cross-Account-Role-C" + } + } + } + ] + } + + + + +###### 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", + "Action": "sts:AssumeRole", + "Resource": "arn:aws:iam::Account-A:role/keyspaces_access" + } + } + +Allowing the principal to assume the shared role is implemented using the `AssumeRole` API of the AWS Security Token Service (AWS STS). For more information, see [ Providing access to an IAM user in another AWS account that you own](https://docs.aws.amazon.com/IAM/latest/UserGuide/id_roles_common-scenarios_aws-accounts.html) 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`. For more information about the SIGV4 authentication plugin, see [Create credentials for programmatic access to Amazon Keyspaces ](./programmatic.credentials.html). For more information on how to configure an application to assume a role in another AWS account, see [Authentication and access](https://docs.aws.amazon.com/sdkref/latest/guide/access.html) in the _AWS SDKs and Tools Reference Guide_. + + + +