AMAZON CLOUD Course Content


Published on

Amazon Web Services (AWS) began offering IT infrastructure services to businesses in the form of web services -- now commonly known as cloud computing. One of the key benefits of cloud computing is the opportunity to replace up-front capital infrastructure expenses with low variable costs that scale with your business. With the Cloud, businesses no longer need to plan for and procure servers and other IT infrastructure weeks or months in advance. Instead, they can instantly spin up hundreds or thousands of servers in minutes and deliver results faster.

Published in: Technology
1 Like
  • Be the first to comment

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

AMAZON CLOUD Course Content

  1. 1. Architecting for the AWS Cloud
  2. 2. Cloud Computing Attributes Abstract Focus on your needs, not on hardware specs. As your Resources needs change, so should your resources.On-Demand Ask for what you need, exactly when you need it.Provisioning Pay only for what you use. Scalability Scale out or in depending on usage needs.No Up-Front No contracts or long-term commitments. Costs Pay only for what you use.Efficiency of Experts Utilize the skills, knowledge and resources of experts.
  3. 3. What Do We Mean By ScalabilityScalability means the ability to scale up (bigger boxes),scale down (smaller boxes), scale out (more boxes) andscale in (fewer boxes)A truly scalable has service has the followingcharacteristics: Increasing resources results in a proportional increase in performance A scalable service is capable of handling heterogeneity A scalable service is operationally efficient A scalable service is resilient A scalable service becomes more cost effective when it growsA scalable architecture is critical to take advantage of ascalable infrastructure!
  4. 4. AWS Cloud Architecture Lessons1. Design for failure and nothing fails2. Loose coupling sets you free3. Design for dynamism4. Security is everywhere5. Don’t fear constraints6. Leverage a variety of storage options
  5. 5. Design for Failure and Nothing FailsNever expect your systems to be stableNever expect your code to be perfectEverything fails IO controllers Ethernet chips Hard disks Fans Power supplies Cabling Network ports Switches Load-balancersIf you can add it, it can fail
  6. 6. Examples of Handling Failure on AWS• Use Elastic IP addresses for consistent and re-mappable routes• Use multiple Amazon EC2 Availability Zones (AZs)• Create multiple database slaves across AZs• Use real-time monitoring across key access points (Amazon CloudWatch)• Use Amazon Elastic Block Store (EBS) for persistent file systems
  7. 7. Build Loosely Couple SystemsMake no assumptions about the inner workingsof your componentsDesign for a jumble of black boxesLoosely coupled systems on AWS De-coupling systems allows for hybrid models (in- cloud + in-physical data center) Balancing between clusters enables easier scaling Using queues (Amazon SQS) buffers against failures
  8. 8. Design for DynamismComponents should not assume thehealth or location of other componentsBootstrapping and dynamic configurationhelps you scale dynamicallyDynamism on AWS Use Auto Scaling Use Elastic Load Balancing on multiple layers Use configurations in SimpleDB to bootstrap instance
  9. 9. Security is EverywhereWith AWS, physical security is free, network security iseasy, and other security can be addedBuilding secure systems with AWS• Create distinct Security Groups for each Amazon EC2 cluster• Use group-based rules for controlling access between layers• Restrict external access to specific IP ranges• Encrypt data stored in Amazon S3• Encrypt all information transmitted across the wire• Consider encrypted file systems for sensitive data
  10. 10. Don’t Fear ConstraintsArchitectural constraints can be brokenHaving a flexible, on-demand pool of resources allows for differentarchitectures that remove constraintsI need more than xxGB of RAM per instance Distribute load across multiple instances; use a shared distributed cacheI need more than xxK IOPS on my database Run multiple read-only copies; sharding; database clustering softwareMy current server specs are better than an Amazon EC2 instance Run more Amazon EC2 instances but only when you need themI need static IPs for my servers Boot scripts that re-configure software from configuration database
  11. 11. Leverage Many Storage OptionsAmazon S3 is optimized for storing large objects Store persistent dataAmazon CloudFront for performance Push popular objects to 14 worldwide edge locationsAmazon SimpleDB for speed, scale, and simplicity Store small bits of data that have no dependencies, such as metadataAmazon EC2 local disk space for transient dataAmazon EBS acts like a disk drive for persistentstorage Store dynamic content or a traditional RDBMS Use snapshots to S3 for backup
  12. 12. Diverse Use CasesWeb Site HostingApplication HostingMedia DistributionStorage, Backup, Disaster RecoveryContent DeliveryHigh-Performance ComputingSoftware Development and Testing
  13. 13. Sample Architecture: Migrating Your Web Applications
  14. 14. Web Application DesignA typical web application could need: Compute power Storage capacity for images, music, etc. Content distribution Database storage Messaging between components Payment options to enable e-commerce Load balancing for optimal performance
  15. 15. Typical Web App Architecture Database Application Server / Business Logic Web Server / Presentation LayerClient Browser
  16. 16. Web Application Design on AWSAn AWS-based web application could use: Compute power (Amazon EC2) Storage capacity for images, music, etc. (Amazon S3) Content distribution (Amazon CloudFront) Database storage (Amazon EBS) Messaging btw. components (Amazon SQS) Payment options to enable e-commerce (Amazon FPS) Load balancing for optimal performance (Amazon EC2)
  17. 17. Use Amazon S3 for Storage Store persistent files in Amazon S3 for lower costs, higher reliabilityClient Browser
  18. 18. Use Amazon CloudFront Amazon CloudFront is a content delivery network that caches data stored in Amazon S3 across a worldwide network of edge locations: Seattle, Palo Alto, Los Angeles, St. Louis, Dallas, Ashburn, Newark, Miami, Amsterdam,Client Browser Dublin, Frankfurt, London, Hong Kong, Tokyo
  19. 19. Use Amazon EC2 for Compute Configure Amazon EC2 running your choice of web server to handle all incoming web requests. Client Browser
  20. 20. Use Amazon EC2 for Compute Configure multiple Amazon EC2 instances running your choice of application server to process requests. Use Availability Zones and Elastic Client Browser IPs for greater reliability and resiliency.
  21. 21. Use Amazon EBS for Database Configure an Amazon EBS device to host your existing relational database. Snapshots can be automatically Client Browser backed up to Amazon S3.
  22. 22. Use Amazon SQS SQS Amazon SQS makes it easy to coordinate between the web serverClient Browser and application servers.
  23. 23. Use Amazon SimpleDB SimpleDB SQS Amazon SimpleDB can be used to store metadata, logfiles, and otherClient Browser information for your site.
  24. 24. Additional Features and Other Serivces New Features CloudWatch (monitoring), Elastic Load Balancing, and Auto Scaling services just launched AWS Import/Export adds “sneaker net” to S3 Other Services Amazon Elastic MapReduce can be used to crunch and analyze large amounts of data Amazon Flexible Payments Service can handle checkout pipelines and payment methods Amazon Mechanical Turk can be used for tasks best suited for human intervention (e.g., image upload and content approval)
  25. 25. Amazon EC2 ToolsAWS Management ConsoleAWS Toolkit for Eclipse: Eclipse Java IDE plug-iniPhone Apps: Manage EC2 from your iPhone with ec2Phone, ElasticPod or directEC2ElasticFox: Mozilla Firefox extension
  26. 26. AWS Management Console
  27. 27. Other ToolsManaging Amazon S3 & AmazonCloudFront: S3Fox, CloudBerry Explorer, Manager for CloudFrontManaging Amazon SimpleDB: AWSZoneManaging Elastic MapReduce: AWS Management Console
  28. 28. In ConclusionMost Important Lesson From OurCustomers: Start small with a well-defined proof of concept that will highlight the power of AWS Build support in your organization Once one application is launched others will follow…
  29. 29. Thank +91 98455 62620