Running High Availability Websites with Acquia and AWS


Published on

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
  • In this video we’ll take a look at Managed Cloud – Acquia’s Drupal tuned Platform-as-a-Service.
  • Cloud computing is a better way to run your business. The cloud helps companies of all sizesbecome moreagile. Instead of running your applications yourself you can run them on the cloud where IT infrastructure is offered as a service like a utility. With the cloud, your company saves money: there are no up-front capital expenses as you don’t have to buy hardware for your projects. The massive scale and fast pace of innovation of the cloud drive the costs down for you. In the cloud, you pay only for what you use just like electricity.The cloud can also help your company save time and improve agility – it’s faster to get started: you can build new environments in minutes as you don’t need to wait for new servers to arrive. The elastic nature of the cloud makes it easy to scale up and down as needed. At the end of the day you have more resources left for innovation which allows you to focus on projects that can really impact your businesses like building and deploying more applications. “With the high growth nature of our business, we were looking for a cloud solution to enable us to scale fast. Think twice before buying your next server. Cloud computing is the way forward.” - Sami Lababidi, CTO, Playfish
  • AWS is useful for low-end traditional DR to high-end HA, but…AWS encourages a rethinking of traditional DR / HA practicesEverything in the cloud is “off-site” and (potentially) “multi-site”Using multiple sites (multiple AZs) comes largely for freeUsing multiple geographically-distributed sites (multiple Regions) is significantly cheaper and easierTends to move the default design point away from “cold” Disaster Recovery toward “hot” High AvailabilityMakes it easier to stack multiple mechanismse.g., Basic HA within one Region, DR site in second Region
  • Each item a
  • Each item a
  • Fault Separation Amazon EC2 provides customers the flexibility to place instances within multiple geographic regions as well as across multiple Availability Zones. Each Availability Zone is designed with fault separation. This means that Availability Zones are physically separated within a typical metropolitan region, on different flood plains, in seismically stable areas. In addition to discrete uninterruptable power source (UPS) and onsite backup generation facilities, they are each fed via different grids from independent utilities to further reduce single points of failure. They are all redundantly connected to multiple tier-1 transit providers. It should be noted that although traffic flowing across the private networks between Availability Zones in a single region is on AWS-controlled infrastructure, all communications between regions is across public Internet infrastructure, so appropriate encryption methods should be used to protect sensitive data. Data are not replicated between regions unless proactively done so by the customer.
  • Distinct physical locationsLow-latency network connections between AzsIndependent power, cooling, network, securityAlways partition app stacks across 2 or more AzsElastic Load Balance across instances in multiple AzsDon’t confuse AZ’s with Regions!
  • Note, the question is not “do you need to automate your deployment” or “should I use automation when I’m using the cloud?” the answer to that is YES!The question is; if you’re using fully standard PHP or Java stacks, why manage it? Beanstalk does that great, with zero lock-in. If what you need is more complex, perhaps cloudformation (note, you can do BOTH!)
  • Three-Tier Web App has been “fork-lifted” to the cloudEverything in a single Availability ZoneLoad balanced at the Web tier and App tier using software load balancersMaster and Standby databaseElastic IP on front end load balancer onlyS3 used as DB backup instead of tapeHow can you use AWS features to make this app more highly available?
  • Three-Tier Web App has been “fork-lifted” to the cloudEverything in a single Availability ZoneLoad balanced at the Web tier and App tier using software load balancersMaster and Standby databaseElastic IP on front end load balancer onlyS3 used as DB backup instead of tapeHow can you use AWS features to make this app more highly available?
  • Chaos Monkey link:
  • Running High Availability Websites with Acquia and AWS

    1. 1. Running High Availability DrupalWebsites with Acquia and AWSMiles Ward John O’KeefeSr. Solutions Architect Sr. Director , OperationsAmazon Web Services Acquia Jess Iandiorio Sr. Director, Cloud Product Marketing Acquia
    2. 2. Agenda• Amazon Web Services: • Building Fault-Tolerant Applications in the Cloud • Surmounting HA Barriers • AWS Stack and Availability Zones• Acquia • Building Fully Redundant, Fault-Tolerant environments • Acquia Managed Cloud stack built on Amazon EC2• Q&A
    3. 3. Faults?FacilitiesHardwareNetworkingCodePeople
    4. 4. What is “Fault-Tolerant”?Degrees of risk mitigation - notbinaryAutomatedTested!
    5. 5. Old School Fault-Tolerance: Build Two
    6. 6. Cloud Computing Benefits No Up-Front Low Cost Pay Only for Capital What You Expense Use Self-Service Easily Scale Improve Agility Infrastructure Up and & Time-to- Down Market Deploy
    7. 7. Cloud Computing Fault-ToleranceBenefits No Up-Front Low Cost Pay for DR Only HA Capital Backups When You Use it Expense Self-Service Easily Deliver Fault- Improve Agility & DR Tolerant Time-to-Recovery Infrastructure Applications Deploy
    8. 8. AWS Cloud allows Overcast Redundancy Have the shadow duplicate of your infrastructure ready to go when you need it……but only pay for whatyou actually use
    9. 9. Old Barriers to HAare now Surmountable Cost Complexity Expertise
    10. 10. AWS Building Blocks: Two Strategies Inherently fault- Services that are fault-toleranttolerant services with the right architecture S3 Amazon EC2 SimpleDb VPC DynamoDB Cloudfront EBSSWF, SQS, SNS, SES RDS Route53Elastic Load Balancer Elastic Beanstalk ElastiCache Elastic MapReduce IAM
    11. 11. Resources DeploymentThe Stack: Management Configuration Networking Facilities Geographies
    12. 12. EC2 Instances Amazon Machine ImagesThe Stack: CW Alarms - AutoScaling Cloudformation - Beanstalk Route53 – ElasticIP – ELB Availability Zones Regio n s
    13. 13. Regional DiversityUse Regions for: Latency • Customers • Data Vendors • Staff Compliance Disaster Recovery … and Fault Tolerance!
    14. 14. Proper Use of Multiple Availability Zones
    15. 15. Network Fault-Tolerance Tools107.22.18.45 isn’t fault-tolerant but is:EIPElastic Load BalancingAutomated DNS: Route53New! Latency-Based Routing
    16. 16. Cloudformation – Elastic Beanstalk Q: Is your stack unique?
    17. 17. Cloudwatch – Alarms – AutoScaling
    18. 18. AMI’sMaintenance is criticalAlternatives: Chef, Puppet, cfn-init, etc.New! When in doubt: 64-bitReplicate for DR
    19. 19. EC2 InstancesConsistent, reliable building block100% API controlledReserved InstancesEBSImmense Fleet Scale
    20. 20. New EC2 VPC feature:Elastic Network Interface Up to 2 Addresses Span Subnets Attach/Detach Public or Private
    21. 21. Example:a “fork-lifted” app
    22. 22. Example:Fault-Tolerant
    23. 23. Why mess with all of that?
    24. 24. AcquiaHigh Availability for Drupal Sites
    25. 25. Designing a HA Infrastructure• It’s like Noah’s Ark – 2 of Everything• Automate Scaling Quickly and Reliably• Leverage Amazon Availability Zones• Select Reliable Synchronization Technologies • mySQL Replication • Gluster • “Trust but Verify”
    26. 26. Managed Cloud: HA Infrastructure Load Balancer Load Balancers •Elastic IP addresses •Varnish Cache •Nginx for load balancing Web Web Web Servers Server Server •Drupal-tuned •Any number/size of servers Database DB DB •MySQL 5.5 •Master-master replication FS FS File system •High Availability file system via GlusterFS •POSIX compatible
    27. 27. If Availability is Your Lifeblood –Consider Multi-Region Failover• Run Your Site From at Least Two AWS Regions• Use an Enterprise-class Database Replication Technology – Tungsten from Continuent• Implement a Content Distribution Network (CDN) • Durability • Manageability • Security
    28. 28. Managed Cloud: RegionsGovCloud US West US West US East South Europe Asia Asia (US ITAR (Northern (Oregon) (Northern America (Ireland) Pacific Pacific Region) California) Virginia) (Sao Paulo) (Singapore) (Tokyo) AWS Regions
    29. 29. Managed Cloud: HA Infrastructure Availability Zone 1 Availability Zone 2 Load Balancer Active Load Balancer Standby Load Balancer Web Web Web Web Server Server Server Server Database Database File System File System
    30. 30. Nothing is Irreplaceable• All Components of the Platform Can Tolerate Failure• Create Failures – Netflix’s “Chaos Monkey”• General Best Practices: • Disaster recovery • Replication • Backups
    31. 31. How is Managed Cloud Different? Infrastructure & Security Scanning Third party tools Application Health Acquia Security Team Customer Team Acquia Operations Team
    32. 32. Worry free, Enterprise-class Drupal
    33. 33. Questions• For more information visit:• Contact us: or 888.9.ACQUIA• Follow us: @acquia• Comments welcome:••• Today’s webinar recording will be posted to: