• Like
Journey Through the AWS Cloud; Building Powerful Web Applications
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Journey Through the AWS Cloud; Building Powerful Web Applications

  • 3,036 views
Published

The penultimate in our series of webinars, 'Journey Through the AWS Cloud'. This complimentary presentation discusses how to build powerful web applications in the AWS Cloud. Bringing together many …

The penultimate in our series of webinars, 'Journey Through the AWS Cloud'. This complimentary presentation discusses how to build powerful web applications in the AWS Cloud. Bringing together many concepts from previous webinars in the series, we summarise a rule book to give you a reference point for architecting with AWS.

Listen to the recording of this webinar: http://www.youtube.com/watch?v=IHRlQPpgbEs

Published in Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
  • Recording can be found here: http://www.youtube.com/watch?v=IHRlQPpgbEs
    Are you sure you want to
    Your message goes here
No Downloads

Views

Total Views
3,036
On SlideShare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
155
Comments
1
Likes
12

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Building powerful webapplications with AWS Ryan Shuttleworth – Technical Evangelist @ryanAWS
  • 2. Your feedback is importantTell us:What’s good, what’s notWhat you want to see at these eventsWhat you want AWS to deliver foryou
  • 3. background
  • 4. Consumer Business Seller IT Infrastructure Business Business Tens of millions of Sell on Amazon Cloud computing active customer websites infrastructure for accounts hosting web-scale Use Amazon solutions technology for your own retail website Eight countries: Hundreds of US, UK, Germany, Leverage Amazon’s thousands of Japan, France, Canada, massive fulfillment registered customers China, Italy center network in over 190 countries
  • 5. About Amazon Web How did Amazon… ServicesDeep experience in building and operating global web scale systems ? …get into cloud computing?
  • 6. Over 10 years in the makingEnablement of sellers on AmazonInternal need for scalable deployment environmentEarly forays proved developers were hungry for more
  • 7. AWS MissionEnable businesses and developers to use web services* to build scalable, sophisticated applications. *What people now call “the cloud”
  • 8. Not excess capacity!
  • 9. Each day AWS adds the equivalent server capacity to power Amazon when it was a global, $2.76B enterprise (circa 2000)
  • 10. Pace of innovationApril 2012: May 2012: June 2012:AWS CloudFormation Support for Creating VPC Resources Amazon Elastic MapReduce Now Supports Hive 0.8.1 AWS Elastic Beanstalk Announces Updated Command Line InterfaceAmazon DynamoDB Now Available in Three Additional Amazon RDS Announces Oracle Enterprise Manager SupportRegions Amazon SES Announces Bounce and Complaint Notifications Announcing VM Export for Amazon EC2AWS Elastic Beanstalk Now Available in the Asia Pacific Cluster Compute Eight Extra Large Instance Type Now Available in(Tokyo) Region AWS Console Enhancements for Elastic Load Balancing: Listener, EU-West Certificate, and Cipher ManagementAmazon DynamoDB Announces BatchWriteItem Feature AWS CloudFormation Supports Amazon DynamoDB and Amazon Amazon RDS announces support for MySQL Read Replica in Amazon CloudFront Dynamic ContentIntroducing AWS Marketplace VPC New Sydney, Australia Edge Location for Amazon CloudFront &AWS Announces The Availability of the Microsoft SharePoint AWS Elastic Beanstalk Now Available in the EU (Ireland) Region Amazon Route 53Server on AWS Reference Architecture White Paper Amazon Simple Email Service Announces Domain Verification AWS Support Expands Free Tier, Adds New Features, Lowers PricesAWS Announces CloudSearch Amazon CloudFront Now Supports Dynamic Content Amazon Elastic MapReduce Announces Support for HBaseAnnouncing the Availability of Reserved Cache Nodes forAmazon ElastiCache Monitor Your AWS Charges with Billing Alerts Using Amazon Amazon RDS MySQL on t1.micro, starting at just $19 a month CloudWatchLive Smooth Streaming for Amazon CloudFront Announcing AWS Identity and Access Management (IAM) roles for Announcing API and AWS Identity & Access Management Support for EC2 instances AWS Storage Gateway Announcing Internal Load Balancing in Amazon Virtual Private New Managed Services for Windows Developers Worldwide Cloud New and Updated Microsoft SQL Server Offerings on Amazon EC2 Announcing Spot Integration with Auto Scaling and CloudFormation New Amazon RDS for Oracle Capabilities and Multi-AZ Enhancements AWS Billing enables enhanced CSV reports and programmatic access Amazon ElastiCache Launches Free Trial Program
  • 11. Pace of innovationApril 2012: May 2012: June 2012:AWS CloudFormation Support for Creating VPC Resources Amazon Elastic MapReduce Now Supports Hive 0.8.1 AWS Elastic Beanstalk Announces Updated Command Line InterfaceAmazon DynamoDB Now Available in Three Additional Amazon RDS Announces Oracle Enterprise Manager SupportRegions` Amazon SES Announces Bounce and Complaint Notifications Announcing VM Export for Amazon EC2AWS Elastic Beanstalk Now Available in the Asia Pacific Cluster Compute Eight Extra Large Instance Type Now Available in(Tokyo) RegionAmazon DynamoDB Announces BatchWriteItem Feature Q2 2012 AWS Console Enhancements for Elastic Load Balancing: Listener, Certificate, and Cipher Management EU-West AWS CloudFormation Supports Amazon DynamoDB and Amazon Amazon RDS announces support for MySQL Read Replica in Amazon CloudFront Dynamic ContentIntroducing AWS Marketplace VPC 35 New Sydney, Australia Edge Location for Amazon CloudFront &AWS Announces The Availability of the Microsoft SharePoint AWS Elastic Beanstalk Now Available in the EU (Ireland) Region Amazon Route 53Server on AWS Reference Architecture White Paper Amazon Simple Email Service Announces Domain Verification AWS Support Expands Free Tier, Adds New Features, Lowers PricesAWS Announces CloudSearch Amazon CloudFront Now Supports Dynamic Content Amazon Elastic MapReduce Announces Support for HBaseAnnouncing the Availability of Reserved Cache Nodes forAmazon ElastiCache Monitor Your AWS Charges with Billing Alerts Using Amazon Amazon RDS MySQL on t1.micro, starting at just $19 a monthLive Smooth Streaming for Amazon CloudFront CloudWatch new features Announcing AWS Identity and Access Management (IAM) roles for Announcing API and AWS Identity & Access Management Support for EC2 instances AWS Storage Gateway Announcing Internal Load Balancing in Amazon Virtual Private New Managed Services for Windows Developers Worldwide Cloud New and Updated Microsoft SQL Server Offerings on Amazon EC2 Announcing Spot Integration with Auto Scaling and CloudFormation New Amazon RDS for Oracle Capabilities and Multi-AZ Enhancements AWS Billing enables enhanced CSV reports and programmatic access Amazon ElastiCache Launches Free Trial Program
  • 12. Relational Database Service Virtual Private Cloud Simple Notification Service Elastic Map Reduce Route 53 Auto Scaling RDS Multi-AZ Reserved Instances 2009 Singapore Region Elastic Load Balancer 2010 Identity Access Management 48 61 Cluster Instances Elastic Beanstalk Simple Email Service CloudFormation 2008 RDS for Oracle ElastiCache 24 SimpleDB CloudFront H1 2012 2011 EBS Availability Zones Elastic IPs 63 822007 Amazon FPS9 Red Hat EC2 DynamoDB Simple Workflow CloudSearch Storage Gateway Route 53 Latency Based Routing number of released features, sample services described
  • 13. Objects in S3 1 Trillion 1000.000 750.000 500.000 250.000 0.000 750k+ peak transactions per second
  • 14. Utility computing
  • 15. Utility computing On demand Pay as you go Uniform Available
  • 16. Utility computing On demand Pay as you go Uniform Available
  • 17. Utility computing
  • 18. Utility computing On demand Pay as you go Compute Scaling Security CDN Backup DNS Database Storage Load Balancing Workflow Monitoring Networking Uniform Messaging Available
  • 19. On a global footprint Region US-WEST (N. California) EU-WEST (Ireland) GOV CLOUD ASIA PAC (Tokyo) US-EAST (Virginia)US-WEST (Oregon) ASIA PAC (Singapore) SOUTH AMERICA (Sao Paulo)
  • 20. On a global footprint Availability Zone
  • 21. On a global footprint Edge Locations London(2) Seattle South Bend New York (2) Amsterdam Newark Stockholm Dublin Palo Alto TokyoSan Jose Frankfurt(2) Paris(2) Ashburn(2) Milan Osaka Los Angeles (2) Jacksonville Dallas(2) Hong Kong St.Louis Miami Singapore(2) Sydney Sao Paulo
  • 22. At the end of a web serviceec2-run-instances ami-b232d0db ec2-run-instances ami-b232d0db --instance-count 3 --instance-count 5 --availability-zone eu-west-1a --availability-zone eu-west-1c --instance-type m1.small --instance-type m1.medium
  • 23. At the end of a web service ec2-run-instances ami-b232d0db --instance-count 2 --availability-zone eu-east-1d --instance-type m1.xlargeec2-run-instances ami-b232d0db --instance-count 2 --availability-zone us-east-1b --instance-type m1.xlarge
  • 24. At the end of a web service as-create-auto-scaling-group MyGroup ec2-authorize default -p 80 --launch-configuration MyConfig --availability-zones eu-west-1c --min-size 2 --max-size 200 elb-create-lb myLoadBalancer
  • 25. and rich console services
  • 26. Elasticity
  • 27. Elastic capacity Traditional IT capacityCapacity Time Your IT needs
  • 28. Elastic capacity On and Off Fast Growth Variable peaks Predictable peaks
  • 29. Elastic capacity WASTE On and Off Fast Growth Variable peaks Predictable peaks CUSTOMER DISSATISFACTION
  • 30. Elastic capacityCapacity Traditional IT capacity Elastic cloud capacity Time Your IT needs
  • 31. Elastic capacity On and Off Fast Growth Variable peaks Predictable peaks
  • 32. 503 Service Temporarily UnavailableThe server is temporarily unable to serviceyour request due to maintenance downtime or capacity problems. Please try again later.
  • 33. 503 Service Temporarily UnavailableThe server is temporarily unable to serviceyour request due to maintenance downtime or capacity problems. Please try again later.
  • 34. From one instance…
  • 35. …to thousands
  • 36. Time: +00h <10 coresElastic Capacity
  • 37. Time: +24h >1500 coresElastic Capacity
  • 38. Time: +72h <10 coresElastic Capacity
  • 39. Time: +120h >600 coresElastic Capacity
  • 40. 40 servers to 5000 in 3 days EC2 scaled to peak of 5000 instances Number of EC2 Instances “Techcrunched” Launch of Facebook modification Steady state of ~40 instances 4/12/2008 4/13/2008 4/14/2008 4/15/2008 4/16/2008 4/17/2008 4/18/2008 4/19/2008 4/20/2008
  • 41. What your users want…
  • 42. What your users want…Fast, performant experience
  • 43. What your users want… Always on,Fast, performant accessible experience anywhere
  • 44. What your users want… Always on,Fast, performant accessible experience anywhere Personalized and rich application
  • 45. What your users want… Always on,Fast, performant accessible experience anywhere Lots of new Personalized andfeatures all of the rich application time
  • 46. Always on,Fast, performant accessible experience anywhere Powerful web applications Lots of new Personalized andfeatures all of the rich application time
  • 47. How?
  • 48. Building powerful web applications
  • 49. Rule 1: Service all web requestsRule 2: Service requests as fast as possibleRule 3: Handle requests at any scaleRule 4: Simplify architecture with servicesRule 5: Automate operational managementRule 6: Leverage unique cloud properties
  • 50. Rule 1: Service all web requestsa) Make sure requests get to your ‘front door’ DNS Application Data
  • 51. Rule 1: Service all web requests a) Make sure requests get to your ‘front door’Request DNS Application Data
  • 52. Rule 1: Service all web requests a) Make sure requests get to your ‘front door’Request DNS Application Data
  • 53. Rule 1: Service all web requests a) Make sure requests get to your ‘front door’Request DNS Application Data Clients can’t resolve …then this is you? irrelevant
  • 54. Rule 1: Service all web requests a) Make sure requests get to your ‘front door’ Request DNS Application Data Feature Details Global Supported from AWS global edge locations for fast and reliable domain name resolution “100% Scalable Automatically scales based upon query volumes Available” Route53 Latency based routing Supports resolution of endpoints based upon latency, enabling multi- SLA region application delivery Integrated Integrates with other AWS services allowing Route 53 to front loadhttp://aws.amazon.com/route53/sla balancers, S3 and EC2 Secure Integrates with IAM giving fine grained control over DNS record access
  • 55. Rule 1: Service all web requests a) Make sure requests get to your ‘front door’ b) Make sure you open the door when they arriveRequest DNS Application Data Route53
  • 56. Rule 1: Service all web requests a) Make sure requests get to your ‘front door’ b) Make sure you open the door when they arriveRequest DNS Application Data Region Availability Zone Elastic load balancing Route53 Availability Zone Multi-availability zone Multi-region Availability Zone Elastic Load Balancer Availability Zone Region
  • 57. Rule 1: Service all web requests a) Make sure requests get to your ‘front door’ b) Make sure you open the door when they arrive c) Have the data to form a responseRequest DNS Application Data Region Availability Zone Route53 Availability Zone Availability Zone Elastic Load Balancer Availability Zone Region
  • 58. Rule 1: Service all web requests a) Make sure requests get to your ‘front door’ b) Make sure you open the door when they arrive c) Have the data to form a response Request DNS Application Data RegionMulti-AZ RDS Availability Zone(Master-slave) Route53 Availability ZoneInter-regionreplication Availability ZoneRead-replicas Elastic Load Balancer Availability Zone Region
  • 59. Rule 1: Service all web requestsRule 2: Service requests as fast as possibleRule 3: Handle requests at any scaleRule 4: Simplify architecture with servicesRule 5: Automate operational managementRule 6: Leverage unique cloud properties
  • 60. Rule 2: Service requests as fast as possible
  • 61. Rule 2: Service requests as fast as possiblea) Choose the fastest route Request Route53 Region Region B A
  • 62. Rule 2: Service requests as fast as possiblea) Choose the fastest route Request Route53 16ms 92ms Region Region B A
  • 63. Rule 2: Service requests as fast as possiblea) Choose the fastest route Request Route53 16ms 92ms Region Region B A
  • 64. Rule 2: Service requests as fast as possiblea) Choose the fastest route Request Route53 Region A DNS entry 16ms Region Region B A
  • 65. Rule 2: Service requests as fast as possible a) Choose the fastest route b) Offload your application serversCloudFront 3 Served from S3World-wide content distribution network /images/*Easily distribute content to end users with lowlatency, high data transfer speeds, and nocommitments. London 2 Served from EC2 *.php Paris 1 Single CNAME NY www.mysite.com
  • 66. Rule 2: Service requests as fast as possiblea) Choose the fastest routeb) Offload your application servers Without CloudFront EC2 webservers/app servers loaded by user requests
  • 67. Rule 2: Service requests as fast as possiblea) Choose the fastest routeb) Offload your application servers With CloudFront Load of user requests pushed into CloudFront, EC2 cluster can scale down Offload Scale Down
  • 68. Rule 2: Service requests as fast as possible a) Choose the fastest route b) Offload your application serversNo CDN CDN for CDN for Static Static & Content Dynamic Content Offload Scale Down Response TimeResponse Time Response Time Server Load Server Server Load Load
  • 69. Rule 2: Service requests as fast as possible a) Choose the fastest route b) Offload your application servers c) Cache it if you canElastiCacheMemcached compatible cachinglayerServe frequently requested & slowchanging data from scalable cacheclustersReduce load on database and otherservers
  • 70. Rule 2: Service requests as fast as possible a) Choose the fastest route b) Offload your application servers c) Cache it if you can d) Single digit latencies where it mattersDatabase Query Performance Desired consistency, predictability Scale
  • 71. Rule 2: Service requests as fast as possible a) Choose the fastest route b) Offload your application servers c) Cache it if you can d) Single digit latencies where it mattersDatabase Query Performance Desired consistency, predictability Actual degraded performance with scale Scale
  • 72. Rule 2: Service requests as fast as possible a) Choose the fastest route b) Offload your application servers c) Cache it if you can d) Single digit latencies where it mattersDatabase Query Performance Desired consistency, predictability Management problems Data sharding Data caching Actual Provisioning degraded Cluster management performance Fault management with scale Scale
  • 73. Rule 2: Service requests as fast as possible a) Choose the fastest route b) Offload your application servers c) Cache it if you can d) Single digit latencies where it mattersDatabase Query Performance Dynamo DB Query Performance DynamoDB Low latency Large scale Zero admin Predictable performance Relational Database Query Performance Scale
  • 74. Rule 2: Service requests as fast as possible a) Choose the fastest route b) Offload your application servers c) Cache it if you can d) Single digit latencies where it mattersDatabase Query Performance Dynamo DB Query Performance DynamoDB Low latency Large scale Average single-digit milliseconds server side Zero admin latencies Predictable performance Runs on solid state drives, and is built to maintain consistent, fast latencies at any scale Scale
  • 75. Rule 1: Service all web requestsRule 2: Service requests as fast as possibleRule 3: Handle requests at any scaleRule 4: Simplify architecture with servicesRule 5: Automate operational managementRule 6: Leverage unique cloud properties
  • 76. Rule 3: Handle requests at any scalea) Scale up Vertical Scaling From $0.02/hr Scale up with Elastic Compute Cloud (EC2) Basic unit of compute capacity Range of CPU, memory & local disk options 14 Instance types available, from micro through cluster compute to SSD backed
  • 77. Rule 3: Handle requests at any scalea) Scale upb) Scale out as-create-auto-scaling-group MyGroupTriggerauto-scaling --launch-configuration MyConfigpolicy --availability-zones eu-west-1a --min-size 4 --max-size 200 Auto-scaling Automatic re-sizing of compute clusters based upon demand
  • 78. Rule 3: Handle requests at any scalea) Scale upb) Scale out Manually By Schedule Send an API call or use CLI to Scale up/down based on date and timelaunch/terminate instances – Only need to specify capacity change (+/-) By Policy Auto-RebalanceScale in response to changing conditions, Instances are automatically based on user configured real-time launched/terminated to ensure the monitoring and alerts application is balanced across multiple Azs
  • 79. Rule 3: Handle requests at any scalea) Scale upb) Scale out Manually By Schedule Preemptive manual scaling of Send an API call or use CLI to Regular scaling up and down of Scale up/down based on date and timelaunch/terminate instances – Only need capacity instances e.g. before a marketing event add(+/-) to specify capacity change 10 more e.g. scale from 0 to 2 to process SQS instances messages every night or double capacity on a Friday night By Policy Auto-RebalanceScale in response to changing conditions, Instances are automatically Dynamic scale based upon based on user configured real-time Maintain capacity across launched/terminated to ensure the monitoringmetrics custom and alerts application is balancedzones multiple availability across e.g. SQS queue depth, Average CPU load, e.g. Instance availability maintained in Azs ELB latency event of AZ becoming unavailable
  • 80. Rule 3: Handle requests at any scale a) Scale up b) Scale out c) Dial it up Elastic Block Store DynamoDBProvisioned IOPS up to 1000 per EBS Provisioned read/write performance per volume table Predictable performance for Predictable high performance scaled via demanding workloads such as console or API databases
  • 81. “AWS gave us the flexibility to bring a massive amount of capacity online in a short period of DynamoDB: time and allowed us to do so in an operationally over 500,000 writes per straightforward way. second AWS is now Shazam’s cloud provider of choice,” Amazon EMR:more than 1 million writes Jason Titus, per second CTO
  • 82. Rule 1: Service all web requestsRule 2: Service requests as fast as possibleRule 3: Handle requests at any scaleRule 4: Simplify architecture with servicesRule 5: Automate operational managementRule 6: Leverage unique cloud properties
  • 83. Rule 4: Simplify architecture with services 30% 70% On-Premise Your Managing All of theInfrastructure Business “Undifferentiated Heavy Lifting”
  • 84. Rule 4: Simplify architecture with services 30% 70% On-Premise Your Managing All of theInfrastructure Business “Undifferentiated Heavy Lifting” AWS More Time to Focus on Configuring Your Cloud-Based Your Business Cloud AssetsInfrastructure 70% 30%
  • 85. Rule 4: Simplify architecture with services Relational Database ServiceUse RDS for databases Database-as-a-Service No need to install or manage database instances Scalable and fault tolerant configurations DynamoDB Use DynamoDB for Provisioned throughput NoSQL database high performance key- Fast, predictable performance value DB Fully distributed, fault tolerant architecture
  • 86. Rule 4: Simplify architecture with services Amazon SQS Reliable messageProcessing results Reliable, highly scalable, queue service queuing without for storing messages as they travel Amazon SQS between instances additional software 1 Processing task/processing trigger 2Push inter-process Simple Workflow Task Aworkflows into the Reliably coordinate processing steps Task B 3 across applicationscloud with SWF (Auto-scaling) Integrate AWS and non-AWS resources Manage distributed state in complex systems Task C
  • 87. Rule 4: Simplify architecture with services Document Server Cloud SearchDon’t install search Elastic search engine based uponsoftware, use Amazon A9 search engine Fully managed service withCloudSearch Search sophisticated feature set Server Scales automatically Results Elastic MapReduce Elastic Hadoop cluster Process large volumes Integrates with S3 & DynamoDB of data cost effectively Leverage Hive & Pig analytics scripts with EMR Integrates with instance types such as spot
  • 88. “Amazon CloudSearch is a game-changingproduct that has allowed us to deliver powerfulnew search capabilities. Our customers can now find what they are looking for faster and more easily than ever before… ….We saved many months of re-architecture and development time by going with Amazon CloudSearch” Don MacAskill CEO & Chief Geek SmugMug
  • 89. Rule 1: Service all web requestsRule 2: Service requests as fast as possibleRule 3: Handle requests at any scaleRule 4: Simplify architecture with servicesRule 5: Automate operational managementRule 6: Leverage unique cloud properties
  • 90. Rule 5: Automate operational management a) Everything is programmableAccess everything Achieve the highest levels via CLI, API or Compute of automation Console Security Scaling sophistication with ease CDN Backup DNS Database Storage Load Balancing Workflow Monitoring Networking Messaging
  • 91. Rule 5: Automate operational managementa) Everything is programmableb) Think disposable, one click deployments Cloud Formation Automate creation of ‘stacks’ in a repeatable way Scripting framework for AWS resource creation Feature Details Platform support Support for AWS resources from EC2 to IAM Resource creation Creates AWS resources behind the scenes and reports on progress Declarative Specify stacks in JSON format and source control your environments Customizable Drive stack creation with paramaters
  • 92. Rule 5: Automate operational management a) Everything is programmable b) Think disposable, one click deployments c) Design for failure, implement self healing Bootstrapping Auto-scaling Cloud Watch Customize instance Maintain capacity of Know what’s going on, startup instances take automated actions Get instances to ask ‘who am Using a minimum pool Use CloudWatch standard andI?’ question on startup and be size will maintain custom metrics to create configured dynamically upon capacity in the event of alarms. being asnwered instance failures Respond with automated administration actions
  • 93. Rule 5: Automate operational managementa) Everything is programmableb) Think disposable, one click deploymentsc) Design for failure, implement self healing
  • 94. Rule 1: Service all web requestsRule 2: Service requests as fast as possibleRule 3: Handle requests at any scaleRule 4: Simplify architecture with servicesRule 5: Automate operational managementRule 6: Leverage unique cloud properties
  • 95. Rule 6: Leverage unique cloud propertiesa) Optimize costs with instance types Hi-Mem 4XL 68.4 GB 26 ECUs 8 virtual cores Cluster Compute 8XL 60.5 GB 88 ECUs 8 core 2 x Intel Xeon Hi-Mem 2XL 34.2 GB 13 ECUs 4 virtual cores Cluster Compute 4XL 23 GB 33.5 ECUs Hi-Mem XL 17.1 GB 8 Nehalem virtual cores 6.5 ECUs 2 virtual cores Cluster GPU 4XL 22 GB Extra Large 15 GB 33.5 ECUs 8 ECUs 8 Nehalem virtual cores 4 virtual cores 2 x NVIDIA Tesla “Fermi” M2050 GPUs Large 7.5 GB High-CPU XL 7 GB 4 ECUs 20 ECUs 2 virtual cores 8 virtual cores Medium 3.75 GBSmall 1.7 GB, 2 ECUs1 ECU 1 virtual cores1 virtual core High-CPU Med 1.7 GB Micro 613 MB 5 ECUs Up to 2 ECUs (for 2 virtual cores short bursts)
  • 96. Rule 6: Leverage unique cloud properties a) Optimize costs with instance types On-demand instances Reserved instances Spot instances Unix/Linux instances start at 1- or 3-year terms Bid on unused EC2 capacity $0.02/hour Pay low up-front fee, receive significant hourly Spot Price based on supply/demand, Pay as you go for compute power discount determined automatically Low cost and flexibility Low Cost / Predictability Cost / Large Scale, dynamic workload handlingPay only for what you use, no up-front Helps ensure compute capacity is available commitments or long-term contracts when needed Use Cases: Use Cases: Use Cases: Applications with flexible start and end timesApplications with short term, spiky, or unpredictable workloads; Applications with steady state or predictable Applications only feasible at very low compute usage prices Application development or testing Applications that require reserved capacity, including disaster recovery
  • 97. Rule 6: Leverage unique cloud propertiesa) Optimize costs with instance types 7000 6000 Spot 5000 4000 On Demand 3000 2000 Reserved Instances 1000 0
  • 98. Rule 6: Leverage unique cloud properties a) Optimize costs with instance types b) Get insight fast with Elastic MapReduceElastic MapReduce Feature DetailsManaged, elastic Hadoop cluster Scalable Use as many or as few compute instances running Hadoop as you want. Modify the number ofIntegrates with S3 & DynamoDB instances while your job flow is runningLeverage Hive & Pig analytics scriptsIntegrates with instance types such as spot Integrated with Works seamlessly with S3 as origin and output. other services Integrates with DynamoDB Comprehensive Supports languages such as Hive and Pig for defining analytics, and allows complex definitions in Cascading, Java, Ruby, Perl, Python, PHP, R, or C++ Cost effective Works with Spot instance types Monitoring Monitor job flows from with the management console
  • 99. Rule 6: Leverage unique cloud properties a) Optimize costs with instance types b) Get insight fast with Elastic MapReduce S3 + DynamoDB Input dataCode Elastic Name Output MapReduce node S3 + SimpleDB Queries HDFS + BI Via JDBC, Pig, Hive Elastic cluster
  • 100. Features powered by Amazon Elastic MapReduce: People Who Viewed this Also Viewed Review highlights Auto complete as you type on search Search spelling suggestions Top searches Ads200 Elastic MapReduce jobs per day Processing 3TB of data
  • 101. “With AWS, our developers can now do things they couldn’t before……Our systems team can focus their energies on other challenges.” Dave Marin Search and data-mining engineer
  • 102. Rule 6: Leverage unique cloud properties a) Optimize costs with instance types b) Get insight fast with Elastic MapReduce c) Create a supercomputer backend when you need itCluster compute instances Network placement groupsImplement HVM process execution Cluster instances deployed in a ‘Placement Group’ enjoy lowIntel® Xeon® E5-2670 processors latency, full bisection 10 Gbps bandwidth10 Gigabit Ethernet 80 EC2 Compute Units 60GB RAM 3TB Local Disk Cluster Compute 10Gbps
  • 103. Rule 1: Service all web requestsRule 2: Service requests as fast as possibleRule 3: Handle requests at any scaleRule 4: Simplify architecture with servicesRule 5: Automate operational managementRule 6: Leverage unique cloud properties
  • 104. What your users want… Always on,Fast, performant accessible experience anywhere Lots of new Personalized andfeatures all of the rich application time
  • 105. With AWS Elastic utility capacity ✔ Always on, accessible anywhere Lots of new Personalized andfeatures all of the rich application time
  • 106. With AWS Elastic utility capacity ✔ Highly available global coverage ✔ Lots of new Personalized andfeatures all of the rich application time
  • 107. With AWSElastic utility capacity ✔ Highly available global coverage ✔ ✔ Agility & Personalized andautomated rich applicationoperations
  • 108. With AWSElastic utility capacity ✔ Highly available global coverage ✔ ✔ ✔ Agility & Cost effectiveautomated storage, big data &operations analytics
  • 109. NASA TV Route 53 DNS Multi-region & AZ Elastic Loadbalancing Amazon Live Streaming Cloud Front Cloud Formation
  • 110. aws.amazon.com get started with the free tier
  • 111. Thank youRyan Shuttleworth – Technical Evangelist @ryanAWS