Amazon EC2 to Amazon VPC: A case study

3,081 views
2,933 views

Published on

Originally presented at AWS re:Invent 2013 in Las Vegas, NV with Eric Shultze, product manager of VPC.

Published in: Technology, Business
0 Comments
4 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
3,081
On SlideShare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
44
Comments
0
Likes
4
Embeds 0
No embeds

No notes for slide

Amazon EC2 to Amazon VPC: A case study

  1. 1. EC2 to VPC: A case study Eric Schultze, AWS Matthew Barlocker, Lucid Software Inc November 14, 2013 © 2013 Amazon.com, Inc. and its affiliates. All rights reserved. May not be copied, modified, or distributed in whole or in part without the express consent of Amazon.com, Inc.
  2. 2. About Me • • • Chief Architect at Lucid Software Inc Bachelors degree from BYU in Computer Science I love to • • • • • play board games go 4-wheeling wrestle my sons fly airplanes Follow me on nineofclouds.blogspot.com
  3. 3. Lucid Software • • • • • • • Online Diagram Software Online Print & Digital Publishing Large Documents Real-time Collaboration All Changes Tracked Vector Graphics High Quality Images
  4. 4. Tech at Lucid • • • • • • Google Closure Javascript PHP Sharded MongoDB Sharded MySQL NodeJS • • • • • • SOA Scala Play! Chef Zabbix, Graphite AWS
  5. 5. Lucid on AWS • • • • • • • • Elastic Compute Cloud Virtual Private Cloud Elastic Block Store Auto Scaling Elastic Load Balancing Simple Storage Service CloudFront Export/Import • Relational Database Service • Route53 • Simple Notification Service • Simple Email Service • Availability Zones • Regions
  6. 6. Why Lucid Chose Amazon VPC • • • • Pricing Interoperability Enhanced Features Security
  7. 7. Other Benefits • • • • • ELB security groups Network ACLs Elastic IP associations VPN support Reserved instance transfers
  8. 8. Drawbacks • • • • • NAT cost and maintenance Setup time New terminology Private subnet accessibility Internal DNS names defaults
  9. 9. Things You Should Know • EIPs or Public IPs in public subnets • NAT • Not special • Public subnet • Subnets • Route tables • Network ACLs • DHCP
  10. 10. Migration Plan
  11. 11. Migration Constraints • EC2 & VPC communication • NAT traffic • Not Shared: – – – – – Security groups Load balancers Auto Scale groups Elastic IPs EIP Limits • Shared: – – – – – – Instance Limit EBS volumes Snapshots Instance Sizes Zones Regions
  12. 12. Migration Plan • • • • Move top layer first Move one layer at a time Meticulously manage security groups Move monitoring/utility servers last • http://nineofclouds.blogspot.com/search/label/VPC
  13. 13. Starting Layout
  14. 14. Move Webservers First
  15. 15. Move Services Next
  16. 16. Move Databases Last
  17. 17. Top 5 Pain Points
  18. 18. 5. Setup & Terminology • • • • • • Subnets DHCP Network ACLs Routes Internet Gateway Unavoidable
  19. 19. 4. Security Groups • • • • Groups Not Shared EC2 open to NAT Use Scripts Avoidable using public subnets
  20. 20. 3. Access Private Subnets • • • • OpenVPN High Availability SSH Tunnels Unavoidable
  21. 21. 2. MongoDB Migration • Election Algorithm • Intermediate Move to Public Subnet • 15 min Downtime
  22. 22. 1. NAT Bandwidth • • • • NAT was t1.micro Databases in EC2 Applications in VPC Not enough bandwidth through NAT • Avoidable
  23. 23. Please give us your feedback on this presentation CPN301 As a thank you, we will select prize winners daily for completed surveys!
  24. 24. Join the Team! • • • • • • Building the next generation of collaborative web applications VC funded High growth rate Profitable Graduates from Harvard, MIT, Stanford Former Google, Amazon, Microsoft employees https://www.lucidchart.com/jobs

×