AWS keyspaces medium security documentation change
Summary
Expanded IAM permissions documentation with granular policy examples for autoscaling operations (create/update/view/delete). Added specific resource ARNs and separated permissions by operation type.
Security assessment
The changes explicitly document required IAM permissions for security-sensitive operations like disabling autoscaling before deletion. The addition of 'application-autoscaling:*' requirement and resource-specific policies helps prevent privilege escalation risks.
Diff
diff --git a/keyspaces/latest/devguide/autoscaling.permissions.md b/keyspaces/latest/devguide/autoscaling.permissions.md index ac1b36b20..014265bdc 100644 --- a//keyspaces/latest/devguide/autoscaling.permissions.md +++ b//keyspaces/latest/devguide/autoscaling.permissions.md @@ -4,0 +5,2 @@ +Create permissionsUpdatee permissionsView permissionsDelete permissions + @@ -7 +9 @@ -To get started, confirm that the principal has the appropriate permissions to create and manage automatic scaling settings. In AWS Identity and Access Management (IAM), the AWS managed policy `AmazonKeyspacesFullAccess` is required to manage Amazon Keyspaces scaling policies. +To configure the required permissions to create and manage automatic scaling settings for tables in Amazon Keyspaces, you can use the following AWS Identity and Access Management (IAM) policies. @@ -9 +11 @@ To get started, confirm that the principal has the appropriate permissions to cr -###### Important +## Permissions to create a table with autoscaling enabled @@ -11 +13,22 @@ To get started, confirm that the principal has the appropriate permissions to cr -`application-autoscaling:*` permissions are required to disable automatic scaling on a table. You must turn off auto scaling for a table before you can delete it. +To create a new table with autoscaling enabled, the principal needs `CREATE` and `ALTER` permissions for tables. + +The following IAM policy is an example of this. + + + { + "Version": "2012-10-17", + "Statement": [ + { + "Effect": "Allow", + "Action": [ + "cassandra:Create", + "cassandra:Alter" + ] + "Resource": [ + "arn:aws:cassandra:aws-region:111122223333:/keyspace/my_keyspace/table/my_table" + ] + } + ] + } + +## Permissions to update autoscaling settings of a table @@ -13 +36 @@ To get started, confirm that the principal has the appropriate permissions to cr -To set up an IAM user or role for Amazon Keyspaces console access and Amazon Keyspaces automatic scaling, add the following policy. +To update the autoscaling settings of a table, the principal needs `ALTER` permissions for tables. @@ -15 +38 @@ To set up an IAM user or role for Amazon Keyspaces console access and Amazon Key -###### To attach the `AmazonKeyspacesFullAccess` policy +The following IAM policy is an example of this. @@ -17 +39,0 @@ To set up an IAM user or role for Amazon Keyspaces console access and Amazon Key - 1. Sign in to the AWS Management Console and open the IAM console at [https://console.aws.amazon.com/iam/](https://console.aws.amazon.com/iam/). @@ -19 +41,14 @@ To set up an IAM user or role for Amazon Keyspaces console access and Amazon Key - 2. On the IAM console dashboard, choose **Users** , and then choose your IAM user or role from the list. + { + "Version": "2012-10-17", + "Statement": [ + { + "Effect": "Allow", + "Action": [ + "cassandra:Alter" + ] + "Resource": [ + "arn:aws:cassandra:aws-region:111122223333:/keyspace/my_keyspace/table/my_table" + ] + } + ] + } @@ -21 +56 @@ To set up an IAM user or role for Amazon Keyspaces console access and Amazon Key - 3. On the **Summary** page, choose **Add permissions**. +## Permissions to view autoscaling settings @@ -23 +58 @@ To set up an IAM user or role for Amazon Keyspaces console access and Amazon Key - 4. Choose **Attach existing policies directly**. +To view or list tables and autoscaling settings, the principal needs read permissions for the system keyspace. For more information, see [system_schema_mcs](./working-with-keyspaces.html#keyspace_system_schema_mcs). @@ -25 +60 @@ To set up an IAM user or role for Amazon Keyspaces console access and Amazon Key - 5. From the list of policies, choose **AmazonKeyspacesFullAccess** , and then choose **Next: Review**. +The following IAM policy is an example of this. @@ -27 +61,0 @@ To set up an IAM user or role for Amazon Keyspaces console access and Amazon Key - 6. Choose **Add permissions**. @@ -28,0 +63,22 @@ To set up an IAM user or role for Amazon Keyspaces console access and Amazon Key + { + "Version":"2012-10-17", + "Statement":[ + { + "Effect":"Allow", + "Action":"cassandra:Select", + "Resource":[ + "arn:aws:cassandra:aws-region:111122223333:/keyspace/system*" + ] + } + ] + } + +## Permissions to delete a table with autoscaling enabled + +To delete a table with autoscaling enabled, the principal needs permissions for the `Drop` action for the specified table. + +The following IAM policy is an example of this. + +###### Important + +`application-autoscaling:*` permissions are required to disable automatic scaling on a table. You must turn off auto scaling for a table before you can delete it. @@ -30,0 +87,12 @@ To set up an IAM user or role for Amazon Keyspaces console access and Amazon Key + { + "Version": "2012-10-17", + "Statement": [ + { + "Effect": "Allow", + "Action": "cassandra:Drop", + "Resource": [ + "arn:aws:cassandra:aws-region:111122223333:/keyspace/my_keyspace/table/my_table" + ] + } + ] + }