Amazon ElastiCache now supports Tag-Based Access Control
Share
Services
[Amazon ElastiCache](/elasticache/) now supports tag-based access control and adding tags to additional cluster resources. By using tags for access control, your [AWS Identity and Access Management (IAM)](/iam/) users, groups, and roles get access only to the Amazon ElastiCache resources with matching tags. This provides you the capability to scale by reducing the number of distinct permissions you need to create and manage in your AWS account. You can define AWS IAM policies that grant or deny access to a resource based on its tags. Furthermore, you can use specific condition context keys to customize your AWS IAM policies to limit specific behaviors on Amazon ElastiCache resources. For a complete list of condition context keys for Amazon ElastiCache, visit the Amazon ElastiCache [documentation](https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/IAM.ConditionKeys.html).
You can now also tag your Amazon ElastiCache replication groups. When you add or remove tags from your replication groups, Amazon ElastiCache will also add or remove these tags to each node in the group, respectively. For a complete list of resources that can be tagged, visit the Amazon ElastiCache [documentation](https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/Tagging-Resources.html#Tagging-your-resources).
Tag-based access control and tagging Amazon ElastiCache resources is supported in all AWS regions. You can manage your AWS IAM polices and manage tags on Amazon ElastiCache resources using the AWS console, CLI, or SDK. To learn more, visit our Amazon ElastiCache [documentation](https://docs.aws.amazon.com/AmazonElastiCache/latest/red-ug/Tagging-Resources.html). To get started, visit the [AWS Management Console](https://signin.aws.amazon.com/signin?redirect%5Furi=https%3A%2F%2Fconsole.aws.amazon.com%2Fconsole%2Fhome%3Fstate%3DhashArgs%2523%26isauthcode%3Dtrue&client%5Fid=arn%3Aaws%3Aiam%3A%3A015428540659%3Auser%2Fhomepage&forceMobileApp=0&code%5Fchallenge=obNxfoY1G2Y3cH6plz6pGk5wCU2aI4B%5FKnehL2BSKNE&code%5Fchallenge%5Fmethod=SHA-256).
What else is happening at Amazon Web Services?
Read update
Services
Share
Read update
Services
Share
Amazon Managed Service for Prometheus now supports configuring a minimum firing period for alerts
October 16th, 2024
Services
Share