Amazon EC2 and Amazon EBS add support for tagging resources upon creation and additional resource-level permissions
You can now tag your Amazon EC2 Instances and Amazon EBS Volumes upon creation. You can do this from the EC2 Instance launch wizard or through the RunInstances or CreateVolume APIs. By tagging resources at the time of creation, you can eliminate the need to run custom tagging scripts after resource creation. In addition, you can now set resource-level permissions on the CreateVolume, CreateTags, DeleteTags, and the RunInstances APIs. This allows you to implement stronger security policies by giving you more granular control over who has access to these APIs. You can also enforce the use of tagging and control which tag keys and values are set on your resources.
You can now tag your Amazon EC2 Instances and Amazon EBS Volumes upon creation. You can do this from the EC2 Instance launch wizard or through the RunInstances or CreateVolume APIs. By tagging resources at the time of creation, you can eliminate the need to run custom tagging scripts after resource creation. In addition, you can now set resource-level permissions on the CreateVolume, CreateTags, DeleteTags, and the RunInstances APIs. This allows you to implement stronger security policies by giving you more granular control over who has access to these APIs. You can also enforce the use of tagging and control which tag keys and values are set on your resources.
By tagging resources on creation and using resource-level permissions, you can ensure your instances and volumes are secured upon creation, more easily track your resources, and achieve more accurate cost allocation reporting.
These new features are provided at no additional cost. You can get started from the EC2 Instance launch wizard, AWS CLI, AWS SDKs, and AWS Tools for Windows PowerShell. To learn more about tagging your Amazon resources, visit the EC2 User Guide.