AWS OpsWorks for Configuration Management now supports tagging and tag-based access control
Share
Services
AWS OpsWorks CM now supports assigning tags to OpsWorks CM servers and backups for both OpsWorks for Chef Automate and OpsWorks for Puppet Enterprise. You can define access controls using tags and AWS Identity and Access Management (IAM) policies to control access to resources and actions. Tags are key value pairs you can use to organize resources, search, create cost allocation reports and control access. For example you can allow your development team full access to your staging OpsWorks CM server but restrict access to your production server.
To learn more about how to tag OpsWorks CM servers and backups, see the [OpsWorks CM API reference guide](https://docs.aws.amazon.com/opsworks-cm/latest/APIReference/Welcome.html). Tagging is now supported in all AWS regions where OpsWorks CM is offered. To learn more about OpsWorks CM, the service that runs and manages configuration management servers in the cloud, please visit the [OpsWorks website](/opsworks/).
What else is happening at Amazon Web Services?
Amazon AppStream 2.0 users can now save their user preferences between streaming sessions
December 13th, 2024
Services
Share
AWS Elemental MediaConnect Gateway now supports source-specific multicast
December 13th, 2024
Services
Share
Amazon EC2 instances support bandwidth configurations for VPC and EBS
December 13th, 2024
Services
Share
AWS announces new AWS Direct Connect location in Osaka, Japan
December 13th, 2024
Services
Share
Amazon DynamoDB announces support for FIPS 140-3 interface VPC and Streams endpoints
December 13th, 2024
Services
Share