Flows and flow modules gain immutable versions and aliases

What changed

AWS added versioning and aliasing for Amazon Connect Customer flows and flow modules. Builders create immutable versions of a flow, attach one or more aliases to a version, and point resources such as queues, quick connects and phone numbers at an alias rather than a specific version. Moving the alias to a new version switches every linked resource at once, without republishing or relinking each one.

Why it matters

Flow changes have typically meant editing what live traffic is using or relinking many numbers by hand. Aliases give a cleaner release and rollback path: validate a new version while production stays on the current one, then repoint the alias, or point it back if something goes wrong.

CxCave practical context

Who should care

• Developers
• CX architects
• Administrators

Implementation considerations

Define an alias convention for production and test, decide how phone numbers and queues will move onto aliases, and update flow deployment and infrastructure-as-code processes to promote versions through aliases.

CxCave recommendation, not a vendor mandate unless explicitly stated.