Deploying with Confidence: Versions and Aliases

If you edit your live agent's instructions while 1,000 people are using it, you are asking for trouble. In Bedrock, we use Versions and Aliases to create a professional deployment pipeline.

1. What is a Version?

A Version is an immutable "Snapshot" of your agent. It captures the Instructions, the Action Group, and the Knowledge Base at a specific point in time.

• You cannot edit "Version 5." It is locked forever.

2. What is an Alias?

An Alias is a "Pointer" to a version.

• You might have an alias called PROD that points to Version 5.
• You have another alias called TEST that points to Version 6.
• When you are happy with Version 6, you simply update the PROD alias to point to it. This is a Zero-Downtime Deployment.

---

3. Visualizing the Pipeline

graph TD
    Dev[Development: Draft] --> V1[Version 1]
    Dev --> V2[Version 2]
    
    V1 --> ProdAlias[PROD Alias]
    V2 --> TestAlias[TEST Alias]
    
    UI[Mobile App] --> ProdAlias

---

4. Why this is mandatory

• Rollback: If Version 6 starts acting weird, you can point the PROD alias back to Version 5 in 1 second.
• Consistency: Different versions of your app can talk to different versions of the agent simultaneously.

---

Summary

• Versions are read-only snapshots of your agent configuration.
• Aliases allow you to point your app at specific versions.
• Blue-Green deployments are possible by updating aliases.
• Never point your production code at the "Draft" version of an agent.