OpenStack Private Cloud to AWS Blueprint
Exit a self-operated OpenStack private cloud for AWS. OpenStack's IaaS model maps cleanly to AWS: translate Neutron to VPC and Keystone to IAM, move images and Swift/Cinder data, rehost in waves with MGN, and retire the control plane for major ops savings.
What and Why
This blueprint migrates a self-operated OpenStack private cloud to AWS. Organizations leave OpenStack to escape the heavy operational burden of running Nova, Neutron, Cinder, Keystone, and the rest, and to gain managed services and elasticity. Because OpenStack is already an IaaS, the mental model maps cleanly to AWS, but the operational savings are the real prize.
Phases
Assessment. Inventory Nova instances, Cinder volumes, Neutron networks and security groups, Keystone tenants and roles, and Swift object data. Map OpenStack projects to AWS accounts and assign 7 Rs dispositions.
Landing zone. Stand up AWS Organizations and Control Tower, a VPC topology mirroring Neutron networks, IAM Identity Center mapped from Keystone roles, and centralized logging. Codify in Terraform (replacing Heat templates).
Image and data. Export VM images (QCOW2) and import them with VM Import/Export, or replicate live instances with AWS Application Migration Service (MGN). Move Swift object data to S3 and Cinder volumes to EBS snapshots.
Migration waves. Rehost instances to EC2 wave by wave, replatform databases to RDS, and validate networking and security-group equivalents. Keep replication running for short cutover windows.
Decommission. After a soak period and backup verification, tear down the OpenStack control plane and reclaim hardware.
Key Risks and Mitigations
- Networking translation from Neutron to VPC. Carefully map subnets, routers, floating IPs (to Elastic IPs), and security groups; test connectivity in staging.
- Large image and volume transfer. Seed with Snowball and use MGN continuous replication.
- Cost overrun from naive rehosting. Right-size, use Savings Plans, and tag for cost allocation.
- Skills gap. OpenStack operators know IaaS; enable them on AWS-specific services.
Recommended Tooling
AWS MGN and VM Import/Export, Terraform (replacing Heat), Control Tower and Organizations, AWS DataSync and Snowball for data, and Prometheus and Grafana for observability.
Success Metrics
Track cost reduction, the steep drop in operational overhead from retiring the OpenStack control plane, migration velocity per wave, and availability through cutover.
Prerequisites
Admin access to OpenStack (Nova, Cinder, Neutron, Swift, Keystone), an AWS landing zone, connectivity for replication, and a wave plan with rollback criteria.