EC2's New Feature "AMI Ancestry" Now Lets You See the Complete Family Tree of an AMI
This page has been translated by machine translation. View original
On November 20, 2025, AMI Ancestry was released as a new feature of Amazon EC2.
Until now, managing the origin of an AMI (which AMI it was copied or created from) had to be done manually using tags and the like, and if the source AMI was deleted, tracking the parent-child relationship could become difficult.
With this update, AWS now automatically records and retains the lineage of AMIs.
I actually created four generations of AMIs and tested whether they can still be traced even after deleting an intermediate parent AMI, so I'll share the results.
Verification Scenario
Following the steps below, I built a "family tree" and tried to check it even after an intermediate AMI had been deleted.
- Create the family tree: Starting from the Base AMI (Amazon Linux 2023), repeatedly make copies in sequence to create four generations (Gen1 to Gen4).
- Check the lineage: Confirm that each AMI correctly points to its parent.
- Destructive test: Delete the intermediate Gen2.
- Check traceability: Confirm whether the information of the deleted parent (Gen2) remains in the information of its child, Gen3.
Verification
1. Create four generations of AMIs
Using Amazon Linux 2023 (al2023-ami-2023.9.20251117.1...) in the Tokyo region as the base, I created copies sequentially via the CLI.
# Verification script image
export BASE_AMI_ID="ami-03852a41f1e05c8e4" # Public AMI
aws ec2 copy-image --source-image-id $BASE_AMI_ID ... --name "Ancestry-Test-Gen1"
aws ec2 copy-image --source-image-id $GEN1_AMI_ID ... --name "Ancestry-Test-Gen2"
# ... Repeat through Gen4
After creation was complete, checking the SourceImageId of each AMI shows that a clean chain has been formed.
--------------------------------------------------------------------------
| DescribeImages |
+-----------------------+----------------------+-------------------------+
| CurrentAMI | Name | SourceImageId |
+-----------------------+----------------------+-------------------------+
| ami-xxxxxxxxxxxxx0a0f7| Ancestry-Test-Gen2 | ami-xxxxxxxxxxxxx2c21d |
| ami-xxxxxxxxxxxxx3a19e| Ancestry-Test-Gen3 | ami-xxxxxxxxxxxxx0a0f7 |
| ami-xxxxxxxxxxxxx0ba6c6| Ancestry-Test-Gen4 | ami-xxxxxxxxxxxxx3a19e |
| ami-xxxxxxxxxxxxx2c21d| Ancestry-Test-Gen1 | ami-03852a41f1e05c8e4 |
+-----------------------+----------------------+-------------------------+
The original Amazon Linux 2023 (ami-03852a41f1e05c8e4) is recorded as the parent of Gen1.
An even more interesting discovery:
The original base AMI itself actually had lineage information too.
aws ec2 describe-images --image-ids ami-03852a41f1e05c8e4 \
--query 'Images[0].{ImageId:ImageId, SourceImageId:SourceImageId, SourceImageRegion:SourceImageRegion}'
{
"ImageId": "ami-03852a41f1e05c8e4",
"SourceImageId": "ami-02b297871a94f4b42",
"SourceImageRegion": "us-west-2"
}
We found that the Amazon Linux 2023 AMI in the Tokyo region was copied from us-west-2.
In other words, the official AWS AMI had also been copied across regions, and its lineage had been recorded automatically.
2. Delete the intermediate AMI (Gen2)
Here I deliberately break the chain. I deregistered (deleted) the intermediate Gen2 (ami-xxxxxxxxxxxxx0a0f7).
3. Check the lineage after deletion (this is the important part!)
With the parent gone, I checked the information of the child, Gen3.
aws ec2 describe-images --image-ids $GEN3_AMI_ID ...
Execution result:
--------------------------------------------------------------------------
| DescribeImages |
+-----------------------+----------------------+-------------------------+
| CurrentAMI | Name | SourceImageId |
+-----------------------+----------------------+-------------------------+
| ami-xxxxxxxxxxxxx3a19e| Ancestry-Test-Gen3 | ami-xxxxxxxxxxxxx0a0f7 |
+-----------------------+----------------------+-------------------------+
The SourceImageId field of Gen3 still reliably retained the ID of the Gen2 I had just deleted (ami-xxxxxxxxxxxxx0a0f7).
This confirmed that the fact that "this AMI was created from the now-gone Gen2" can be proven and traced at the system level.
How it looks in the Management Console
This lineage information can also be checked in the GUI.
The newly added "AMI Ancestry" tab on the AMI details screen let me view the list.
- Gen1 selected

- Gen4 selected

- After Gen2 deletion

It could display the information of the deleted Gen2 AMI, and even the ID of the original AWS-provided AMI.
Summary: What are the benefits?
The greatest benefit of this feature is "transparency in security and governance".
- Security: You can identify, in one sweep, all descendant AMIs derived from a specific past version (for example, a parent AMI in which a vulnerability was found).
- Operations: You can prove, as an AWS feature rather than relying on tag-based operations, that an AMI is not "one that someone created on their own" but "one built from an approved golden image."
- Cleanup: Because the history can be traced even if you delete the parent AMI, you can safely delete intermediate images that you had kept only for lineage checks, helping to clean up your AWS environment and optimize storage.
It is an unglamorous update, but it can be said to be an effective one for resolving challenges in AMI management in enterprise environments.
