Tag Your AWS Batch Spot Managed Compute Environments
AWS Batch now supports user tags that will automatically propagate to Spot instances launched by your Managed Compute Environments. This makes it easier for AWS Batch customers to track ownership, drive their cost accounting processes, implement compliance protocols, and to control access to Spot instances via IAM policies.
AWS Batch now supports user tags that will automatically propagate to Spot instances launched by your Managed Compute Environments. This makes it easier for AWS Batch customers to track ownership, drive their cost accounting processes, implement compliance protocols, and to control access to Spot instances via IAM policies.
Previously, if you wanted to tag Spot instances launched by AWS Batch you had to write and manage custom code. Now you can provide user tags when you create a Managed Compute Environment and let AWS Batch automatically tag instances launched on your behalf.
Tags enable you to categorize your AWS resources in different ways, for example, by purpose, owner, or environment. This is useful when you have many resources of the same type — you can quickly identify a specific resource based on the tags you've assigned to it. Each tag consists of a key and an optional value, both of which you define. For example, you could define a set of tags for your account's Amazon EC2 instances that helps you track each instance's owner and stack level.
Tagging is supported today in all regions where AWS Batch is available. For more information, click here.
AWS Batch is currently available in the following regions:
- US East (N. Virginia) us-east-1
- US East (Ohio) us-east-2
- US West (Oregon) us-west-2
- EU (Ireland) eu-west-1
- EU (London) eu-west-2
- EU (Frankfurt) eu-central-1
- Asia Pacific (Tokyo) ap-northeast-1
- Asia Pacific (Singapore) ap-southeast-1
- Asia Pacific (Sydney) ap-southeast-2
For more information on AWS Batch: