Source note · Planning a contact center platform migration
AWS guidance recommends separate AWS accounts for development, testing and production Amazon Connect instances, both to limit the impact of changes and to set billing boundaries.
Checked 2026-09-25
- Vendor
- Amazon Web Services
- Product
- Amazon Connect Customer
- Subsystem
- environments
- Deployment
- multi-tenant
- Region
- not restricted
- Release range
- current as of 2026-09-25
- Checked
- 2026-09-25
Sources
- Technical considerations - Strategies for migrating your contact center to Amazon Connect (AWS Prescriptive Guidance) — Amazon Web Services · tier 2 current vendor documentation · Separate AWS accounts
Cite this note
APA
WarmTransfer. (2026, September 25). Planning a contact center platform migration: source note contact-center-migration-planning-separate-accounts. WarmTransfer. https://warmtransfer.net/knowledge/claims/contact-center-migration-planning-separate-accounts
BibTeX
@misc{warmtransfer-claim-contact-center-migration-planning-separate-accounts,
title = {Planning a contact center platform migration: source note contact-center-migration-planning-separate-accounts},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/contact-center-migration-planning-separate-accounts},
note = {Source note contact-center-migration-planning-separate-accounts, checked 2026-09-25}
}