I wanted to bring to your attention an issue regarding the tag retention in the EBS encryption automation document.
Currently, when the automation creates a new encrypted volume from an unencrypted volume, it only assigns one tag (encrypted-clone-of-volume) with the original volume ID.
This means that the newly created volume does not inherit any other tags that the original unencrypted volume may have.
Challenge:
The lack of tag retention can complicate management and tracking of EBS volumes, especially concerning backup and lifecycle policies tied to specific tags. like i faced now!
Proposed Solution:
To address this, I recommend adding a step to the automation in the document EBS-Encryption-Config-Rule-XXX that retrieves the existing tags from the unencrypted volume.
After capturing those tags, they can be included in the CreateVolume action when creating the new encrypted volume.
This way, all relevant tags from the original volume will be preserved, enhancing the overall effectiveness of the automation.
Implementing this change will help ensure better consistency in resource tagging, which is crucial for managing AWS resources effectively.
I wanted to bring to your attention an issue regarding the tag retention in the EBS encryption automation document.
Currently, when the automation creates a new encrypted volume from an unencrypted volume, it only assigns one tag (encrypted-clone-of-volume) with the original volume ID. This means that the newly created volume does not inherit any other tags that the original unencrypted volume may have.
Challenge: The lack of tag retention can complicate management and tracking of EBS volumes, especially concerning backup and lifecycle policies tied to specific tags. like i faced now!
Proposed Solution: To address this, I recommend adding a step to the automation in the document EBS-Encryption-Config-Rule-XXX that retrieves the existing tags from the unencrypted volume. After capturing those tags, they can be included in the CreateVolume action when creating the new encrypted volume. This way, all relevant tags from the original volume will be preserved, enhancing the overall effectiveness of the automation.
Implementing this change will help ensure better consistency in resource tagging, which is crucial for managing AWS resources effectively.
Thank you for considering this enhancement! Sameh