Hey @Ralf J - nope, this is not a bug. That functionality is only intended to tag the EC2 instances. You can certainly ask for a feature request to be opened against AWS Batch on this if it's valuable. I am curious to know more about your use case. Are you trying to operate on the resources and use the tags to filter, doing something like this?
aws autoscaling describe-auto-scaling-groups --filters <tags>
OS in Batch compute environment suddenly changed?asked 2 years ago
Cloudformation + AWS Batch - stack-level tags -> EC2 tagsasked 10 months ago
how to delete compute environment that is invalid ?Accepted Answerasked a year ago
Does using SPOT_CAPACITY _OPTIMIZED launch spot instances into an auto-scaling group in AWS Batch?asked 5 months ago
AWS batch does not scale down EC2 instancesasked 10 months ago
Unable to add new compute environment on JobQueue on AWS Batchasked a month ago
AWS Batch: How to enable metrics on EC2 auto scaling groups?
Unable to use launch template with AWS Batch Compute EnvironmentAccepted Answerasked 3 months ago
AWS Batch: how to propagate tags to ECS clusters and EC2 auto scaling groups?
Managed compute environment, launches m4 instead of m5Accepted Answerasked 3 years ago