A city’s shared-services account accumulates orphaned AMIs and untagged ECR images from retired pipelines, steadily increasing snapshot and registry storage cost. Which action best reclaims that artifact sprawl cost?
Select an answer to reveal the explanation.
Short Explanation
Orphaned AMIs and ECR tags are attic boxes that keep billing you rent. Lifecycle policies—and a deliberate deregister pass—clear the attic. Shipping everything to Docker Hub or weekly VM exports just moves the mess.
Full Explanation
Lifecycle policies for ECR and disciplined AMI/snapshot retention reclaim storage cost from unused artifacts while preserving required rollback images. Indefinite retention without policy, pushing to public registries as a cost dodge, or weekly on-prem exports do not provide governed artifact cost control in AWS shared-services accounts.