Presented on 2/6/2018 at the AWS Chicago meetup https://www.meetup.com/AWS-Chicago/events/246045072/

1. A Tale of Three AWS
Migrations
Allie Richards
Senior DevOps Engineer
Centro
@hpuxgirl

2. Who is Allie and why should I listen to her?
• 18 years in the tech industry,
focused mostly on
operations/infrastructure
• Worked for a range of companies
(15 people – 50k people)
• Devopsdays Chicago Organizer
• Or maybe just listen to Radish

3. What about Centro?

4. Why move to AWS? Why not?

5. Why move to AWS? Management reasons
• “Best of breed” cloud
hosting solution
• Attract top talent
• “Will it be cheaper?”
• Narrator: it was not!

6. Why move to AWS? Dev reasons
• Provision own environments
• pre-prod can look more like
prod
• Something about Docker

7. Why move to AWS? Ops reasons
• Hardware refresh
• Weak security posture
• Some workloads needed more
power
• Disaster Recovery strategy
needed some help

8. Why move to AWS? Summary
• Cost
• Elasticity
• Security
• Disaster Recovery
• Performance

9. There is no secret sauce
• Best practices are still emerging
• You will need to build a lot of
tooling
NOPE

10. Centro’s recipe
• RDS, Elasticache, ASGs, VPCs
• Consul
• Vault
• OpenVPN
• Terraform
• Packer
• Saltstack
• Datadog
• StackStorm (“chatops”)

11. Quick ChatOps “demo”

12. Migration the First Jenkins
• Hybrid
• Done really quickly. Like really fast
• Cost
• Elasticity
• Security
• Disaster Recovery
• Performance

13. Migration the Second SaaS Platform
• No! not that much like prod • Cost
• Elasticity
• Security
• Disaster Recovery
• Performance

14. Migration the Third Data Warehouse
• There is no magic pixie fairy dust • Cost
• Elasticity
• Security
• Disaster Recovery
• Performance

15. A note about cost
• Usage patterns will change, likely
driving costs up

16. Bonus cat picture

17. Thank you
Allie Richards
Senior DevOps Engineer
Centro
@hpuxgirl