AWS CodeDeploy rollback creates a new deployment with a new deployment ID; it does not restore or erase the earlier deployment record. A small deploy ledger should link the deployment that failed or was stopped to the recovery deployment, record why rollback happened, and point operators back to AWS history for the full details.
Why record both deployment IDs?
A rollback can look like a return to an earlier state, but CodeDeploy implements it by deploying a previously deployed revision again. AWS says, “These rolled-back deployments are technically new deployments, with new deployment IDs, rather than restored versions of a previous deployment.” AWS CodeDeploy documentation
As an Amazon Associate I earn from qualifying purchases.
That means the original deployment and the rollback deployment are separate records. If a later operator sees only the recovery deployment ID, the reason for it—and which rollout it followed—may be harder to establish. Keep both IDs and their relationship in one ledger entry.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →What should a deploy ledger contain?
Use a compact index, not a second event log. These fields are an operational recommendation, not an AWS-prescribed schema:
#1 Best Overall
- When and where: UTC timestamp, AWS account or environment, and region.
- What changed: CodeDeploy application and deployment group, or CloudFormation stack; include the revision or artifact identifier when available.
- Rollback chain: ID of the deployment or operation that triggered rollback and ID of the rollback deployment.
- Outcome and cause: status, whether rollback was automatic or manual, and the failure reason or monitoring alarm that prompted it.
- Follow-up context: operator or incident reference and a console link or query pointer to the native AWS records.
Capture only enough context to find and understand the chain. Keep detailed events, status changes, and failure information in CodeDeploy or CloudFormation rather than copying them into the ledger.
How to find the source records
CodeDeploy
Use the CodeDeploy console’s Deployment history to find deployment IDs and inspect their details. Alternatively, use the AWS CLI or APIs to list deployment IDs, then retrieve one deployment or a batch of deployments. Preserve the IDs in the ledger so an operator can return to those records. AWS CodeDeploy deployment details
CodeDeploy rollback metadata can identify the rollback deployment, its status, and the ID of the deployment that triggered it. Record these as linked IDs rather than treating the rollback as an update to the original deployment. AWS CodeDeploy DeploymentInfo API reference
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →CloudFormation-managed changes
For a change managed through CloudFormation, retain the stack and operation context in the ledger. Stack events are chronological, and the deployment timeline shows resource statuses and when they changed. Selecting a resource provides its start and end times, duration, and any failure reason. Use those native records to investigate the sequence instead of reproducing the full timeline in the ledger. View CloudFormation stack events · CloudFormation deployment progress
Rank #3
Make the rollback trigger clear
Automatic rollback can be configured for deployment failures or monitoring thresholds. Manual rollback has a different origin, so record which kind occurred and the relevant failure or alarm. A status alone does not explain why the recovery deployment was started. AWS CodeDeploy rollback behavior
Quick Recap
Keep the ledger useful over time
- Write the ledger entry when the rollback is initiated or completed, and link the triggering and recovery IDs.
- Include account, environment, and region so an ID can be located in the right AWS context.
- Use a durable, searchable record that fits your team’s operations process; AWS documentation does not prescribe a separate ledger format or retention policy for one.
- Check that the pointer leads to the relevant AWS history, while leaving detailed service events in their native records.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
