AWS Glue now supports resource tagging
You can now assign AWS resource tags to crawlers, development endpoints, jobs, and triggers in AWS Glue. Each tag consists of a key and an optional value, both of which you define. You can use tags in AWS Glue to easily organize and identify your resources, create cost allocation reports, and control access to resources.
You can now assign AWS resource tags to crawlers, development endpoints, jobs, and triggers in AWS Glue. Each tag consists of a key and an optional value, both of which you define. You can use tags in AWS Glue to easily organize and identify your resources, create cost allocation reports, and control access to resources.
You can add or remove resource tags from the above mentioned AWS Glue resources using the AWS Glue console, API, CLI, or SDK, and assign up to 50 tags per resource.
AWS resource tags are now supported by AWS Glue in all the regions where AWS Glue is available except the AWS GovCloud (US-West) region. To learn more about adding tags to AWS Glue resources, please visit our documentation. See AWS Tagging Strategies for general best practices when using tags with AWS resources.