Aws migration strategy
-
Upload
suliman-lei -
Category
Presentations & Public Speaking
-
view
220 -
download
7
Transcript of Aws migration strategy
MIGRATION CONSIDERATIONS
Migration Approach & Best Practices Understand Application Stack’s (not Servers)
components that make up the application CPU/Ram /Disk average utilization
Security (public facing vs. private facing)
Know the application owner
Asking the right question! How is the application currently configured ?
Is there current documentation
Networking / Storage / Compute capacity.
IDENTIFY APPLICATIONS TO MOVE
Standalone applications easy to move
Applications with loosely coupled integrations are good candidates.
Tightly integrated applications are hard to move (e.g. Active directory is tightly coupled, may be better to build new and start replication).
INVEST IN PROOF OF CONCEPT EARLY
Proof of concept will answer tons of questions quickly
Will identify gaps and touch points
Give you a good estimation of the task ahead.
CLOUD FORMATION (CF)
Allows you to create and provision resources in a reusable template fashion.
Allows you to source control your infrastructure by building templates that enable you create/delete resources on demand.
Templates are built using Java Script Object Notation (JSON) syntax Can use git to version your infrastructure Boto is a awsome and powerful tool
ANATOMY OF CF TEMPLATE
Template is made up of 6 sections Declaration – Must follow AWS Template format version. Parameters – Values that can be passed at creation time Mappings – Key/Value pairs of information Conditions Resources – Can be database, EC2, S3, DynamoDb – Only Required
portion. Outputs
TOOL KITS
Use open source when possible Nagios Graphite virtuallyGhetto (vmware tools and scripts)
Good Migration tool kits (paid) CloudEndure
Block by block copy of instance to AWS