There are many infrastructure artifacts that need to be addressed when migrating enterprise workloads to AWS: compute, storage, database, security, load balancers, firewalls, data encryption, management, monitoring, patching, anti-virus, and intrusion detection to name a few. There are also development artifacts that need to be addressed: packaging, testing, deployment, versioning, and upgrades to name a few. These on premise constructs need to the mapped to the same, equivalent, or new constructs on AWS.
There are also a number of migration approaches that can be employed: lift and shift, leverage and extend, or re-engineering. The approach taken depends upon the application attributes - Oracle and SAP Commercial Off-The-Shelf (COTS), Microsoft and other 3RD party packaged applications, or custom systems. There are strength and weaknesses of each approach.
AWS offerings services that are not readily accessible in your on premise environment. There are services, including CloudFront and Auto Scaling, that can be used to increase performance and reduce cost without changing a line of application code.
In future blogs, I will began to identify and address the mappings, approaches, and services that can be used to migrate enterprise workloads to AWS.
There are also a number of migration approaches that can be employed: lift and shift, leverage and extend, or re-engineering. The approach taken depends upon the application attributes - Oracle and SAP Commercial Off-The-Shelf (COTS), Microsoft and other 3RD party packaged applications, or custom systems. There are strength and weaknesses of each approach.
AWS offerings services that are not readily accessible in your on premise environment. There are services, including CloudFront and Auto Scaling, that can be used to increase performance and reduce cost without changing a line of application code.
In future blogs, I will began to identify and address the mappings, approaches, and services that can be used to migrate enterprise workloads to AWS.
