AWS AmazonElastiCache documentation change
Summary
Added documentation about Memcached vertical scaling support and the required IAM action `elasticache:ModifyCacheCluster`
Security assessment
The change adds documentation about required IAM permissions for a new scaling feature, which relates to security controls but does not address a specific vulnerability or security incident.
Diff
diff --git a/AmazonElastiCache/latest/dg/AutoScaling.md b/AmazonElastiCache/latest/dg/AutoScaling.md index 3ba3c0e1c..af3cab8bd 100644 --- a//AmazonElastiCache/latest/dg/AutoScaling.md +++ b//AmazonElastiCache/latest/dg/AutoScaling.md @@ -75 +75 @@ Scaling may take noticeable time and will require extra cluster resources for sh -ElastiCache for Valkey and Redis OSS Auto Scaling is made possible by a combination of the ElastiCache, CloudWatch, and Application Auto Scaling APIs. Clusters are created and updated with ElastiCache, alarms are created with CloudWatch, and scaling policies are created with Application Auto Scaling. In addition to the standard IAM permissions for creating and updating clusters, the IAM user that accesses ElastiCache Auto Scaling settings must have the appropriate permissions for the services that support dynamic scaling. IAM users must have permissions to use the actions shown in the following example policy: +ElastiCache for Valkey and Redis OSS Auto Scaling is made possible by a combination of the ElastiCache, CloudWatch, and Application Auto Scaling APIs. Clusters are created and updated with ElastiCache, alarms are created with CloudWatch, and scaling policies are created with Application Auto Scaling. In addition to the standard IAM permissions for creating and updating clusters, the IAM user that accesses ElastiCache Auto Scaling settings must have the appropriate permissions for the services that support dynamic scaling. In this most recent policy we have added support for Memcached vertical scaling, with the action `elasticache:ModifyCacheCluster`. IAM users must have permissions to use the actions shown in the following example policy: