About the changes in AWS Backup tagging behavior that AWS has been notifying about since around June 2025

About the changes in AWS Backup tagging behavior that AWS has been notifying about since around June 2025

2025.08.12

The issue I'm facing

What is the change to AWS Backup tagging behavior that will be notified from AWS around June 2025?
Also, please advise how to determine if a response is required.

How can I solve it?

This notification concerns a change in behavior when an EBS volume with tags is included in a backup rule that also has tag settings. Previously, when the tag keys were the same, the volume's tags would take priority and be applied to the snapshot. Going forward, tags configured in the backup rule will take priority instead.

Specifically, the following behavior change will occur:

Current behavior:
EBS volume tag value: VolumeTag
Backup rule tag value: RuleTag
Resulting tag value on snapshots created by the backup rule: VolumeTag

New behavior after the change:
EBS volume tag value: VolumeTag
Backup rule tag value: RuleTag
Resulting tag value on snapshots created by the backup rule: RuleTag

Therefore, if your EBS volumes and backup rules have the same tag keys but different values, the tags may not be applied as intended. We kindly ask you to review your backup rule settings.

It seems that even when both the tag keys and values are identical, they may be displayed as "affected resources" in the notification. However, if they are completely identical, the same tags will continue to be applied, so no action is required.
If the tag keys differ between EBS volumes and backup rules, both tags will be applied as before, so there is no need to consider the changes mentioned in this notification.

Also, for AMIs, the backup rule tags already take priority as described in the behavior change.

I've created this article because I've noticed several questions about this notification.
I hope this article is helpful to someone.

Share this article

FacebookHatena blogX

Related articles