Amazon Quick Resource Migrator Automates Auditable Cross-Account Promotion
AWS introduces the Amazon Quick Resource Migrator MCP server, enabling automatic, idempotent, and auditable migration of Amazon Quick agents, connectors, knowledge bases, flows, and spaces across AWS accounts. This brings automation to a manual process, improves governance, and provides detailed backup and rollback capabilities.
What changed?
Amazon Web Services has released the Amazon Quick Resource Migrator, an MCP server running on Amazon Bedrock AgentCore. This tool automates the promotion of Amazon Quick resources—including agents, action connectors, knowledge bases, flows, and spaces—from one AWS account to another (for example, from development to production). The process is idempotent, supports selective resource-driven migration, faithfully copies permissions, writes versioned backups to S3 for every change, and provides a read-only migration preview for safe approvals. Secret values and S3 documents themselves are not copied; these require re-authentication or manual transfer.
Why does it matter to an everyday developer?
Previously, promoting Amazon Quick resources between AWS accounts required manual recreation and reconfiguration, leading to high risk of errors and governance challenges, especially in organizations with separate development and production environments. The new migrator automates these tasks, reducing manual effort and mitigating risks such as configuration drift and accidental permission errors. It provides auditability with backup snapshots and allows dry-run previews, supporting enterprise change management processes and rollback capabilities.
What can the developer do now?
Developers and DevOps teams can deploy the Amazon Quick Resource Migrator to orchestrate safe, automated, and repeatable cross-account promotions. Teams can use the read-only preview to review pending changes before applying them. For action connectors, re-authentication is required after migration. For knowledge bases backed by S3, only metadata and configuration migrate; actual data objects must be managed separately. Documentation and source code are available in the aws-samples repository, allowing integration into release pipelines for managed and auditable resource promotion.