Migration from AWS to Enterprise Data Centers: 5 Top Considerations
1 like173 views
This document discusses considerations for migrating from AWS to enterprise data centers. The top 5 considerations are: 1) Networking management and configuration, 2) Infrastructure provisioning for development teams, 3) Establishing a disaster recovery strategy to backup data offsite, 4) Automating deployment operations to replicate public cloud processes, and 5) Planning the data migration approach for moving data from public to private cloud environments.
Migration from AWS to Enterprise Data Centers: 5 Top Considerations
- 1. Migration from AWS to Enterprise Data Centers: Top 5 Considerations Rajesh Mani, Product Marketing Cody Hill, Cloud Architect
- 2. Cloud Migration: There and Back Againβ¦To DCs β’ With the advent of the public cloud wave, beginning with AWS in the mid- 2000s, enterprises increasingly adopted public clouds for their convenience, agility and flexibility β’ Smaller companies especially adopted a βcloud onlyβ approach by locating all their IT applications and services on the public cloud β’ But as enterprises scaled in size and operations/management complexities increased, there has been an increased impetus to migrate away from public cloud environments
- 3. Migration from Public Clouds: Why The Exodus? Reasons: β’ Significant benefit β up to 80% lower TCO β’ Flexible (customized) instance sizes β’ Increased Security and compliance PUBLI C MIGRATION FROM PUBLIC CLOUDS
- 4. Migration From Public Clouds: Where To Go? β’ Another public cloud, like AWS to Google β’ Private data center β’ Colocation facility like Equinix, as an example β’ Bare metal cloud infrastructure-as-a-service like SoftLayer (IBM Cloud) or Packet PUBLI C PUBLIC CLOUD IGRATION Public Private Data Center Public Private Colocation Private Bare Metal
- 5. Each Migration Path Has Pros and Cons... β¦ and five top considerations to keep in mind
- 6. Consideration 1: Networking Before making the move from a public cloud, consider how teams will: β’ Manage edge networking β’ Set up BGPs β’ Secure public IPs for services β’ Set up network management
- 7. Consideration 2: Infrastructure Provisioning β’ Infrastructure resources need to be divided and provided to development teams after migration β’ Creating a shared resources platform for developers may require establishment of an OpenStack or Kubernetes based environment for running VMs/containers β’ Running applications on bare metal services, for example, keep the new private environment API-centric
- 8. Consideration 3: Disaster Recovery Strategy The public cloud scores well when it comes to disaster recovery β’ Developers need a way to keep backup data off site β’ Access to automated ways to restore production at another location or geographic area Some companies continue to leverage the public cloud to replicate and backup data
- 9. Consideration 4: Operationalizing Deployment In the private cloud, replicate public cloud by operationalizing deployment: β’ Automate version controls β’ Roll out updates on a wide basis β’ Choose process over more people to fix problems during deployment Version controls Deploy wide Moving from public to private cloud requires enhanced automation control during operations
- 10. Consideration 5: Data Migration One of the most difficult and challenging tasks in cloud migration is moving data from the public cloud. β’ Each situation is unique β’ Make data migration decision on case by case basis Whether replication or backup and restore, determine how the data is moved to production environments PUBLIC PRIVAT E PRIVAT E
- 11. Learn more about Platform9βs Private and Hybrid Cloud Solutions οΌ Visit http://platform9.com οΌ Try the sandbox οΌ Get a free15-day trial οΌ Contact us