Amazon Elastic Beanstalk

Transcription

1 Amazon Elastic Beanstalk

2 A Short History of AWS Amazon started as an ECommerce startup Original architecture was restructured to be more scalable and easier to maintain Competitive pressure for time-to-market Engineers still spend 70% of their time on > Scalability > Infrastructure issues > Ensuring enough computing capacity is available Must increase productivity! Solution: Define a scalable universal computing platform (Virtual) machines are the least common denominator and thus AWS (Amazon Web Services) was created!

3 What is AWS? A set of offerings Mostly IaaS (infrastructure as a Service) Very scalable Lots of customers Foundation for a lot of other cloud services Each day AWS adds the equivalent server capacity to power Amazon when it was a globale, $2.76B enterprise (about 2000)

4 AWS: Global Service AWS offers services globally Distributed in Regions > US-East > US-West > EU-West > Asia Pacific (Singapore) > Asia Pacific (Tokyo) > Low latency for the customer Each Region has several Availability Zones > Data center > Isolated from each other > High availability by distribution across Availability Zones SLA: Failure of one Availability Zone is acceptable

5 AWS Services: EC2 Elastic Computing Cloud i.e. virtual machines Can be spun up quickly (minutes) Can scale up by booting up more machines Access using ssh (Key Pairs) Firewalling / port filtering (Security Groups) IP address can be dynamically assigned to an instance (Elastic IP) Usually boot from AMIs (Amazon Machine Images) > Several available from Amazon > Others provided by the community > E.g. for Ubuntu > Can create your own

6 AWS Services: S3 (Simple Storage Service) Storage for large files (1 byte to 5 TB) Public / private access Organized in buckets Folders etc also possible Can be downloaded using HTTP REST / SOAP interface available % durability and 99.99% availability of objects over a given year Sustain the concurrent loss of data in two facilities Reduced Redundancy Storage (RRS) 99.99% durability and 99.99% availability

7 EBS (Elastic Block Storage) Behave like raw, unformatted block devices (i.e. hard disks) Located in a specific Availability Zone Snapshots can be stored in S3 More reliable then physical hard disks EC2 usually uses EBS to store data EC2 also has local storage > Won t survive restarts > Less performance

8 Elastic Load Balancer Load Balancer in one Availability Zone or across Availability Zones Can detect health of EC2 instances Support sticky sessions SSL termination Supports High Availability across Availability Zones Auto Scaling: Additional service Start new EC2 instances when demand increases Stop EC2 instances when demand drops Based on CloudWatch metrics Auto Scaling + Elastic Load Balancer allow for Elastic Scaling

9 The Complete Picture Elastic Load Balancer EC2 EC2 EC2 Auto Scaling EBS EBS EBS

10 AWS: Powerful, but The building blocks for a scalable, global infrastructure are there You need to assemble them You need to deploy applications on the bare (virtual) metal You need to configure it (using CLI tools) Some support available > Amazon Cloud Formation to create templates for Cloud stacks (e.g. Drupal, WordPress, Rails application) > Rightscale has a full business based on it > Automation tools like Chef or Puppet

11 Enter Elastic Beanstalk Elastic Load Balancer Versioned WARs Log Files Web Interface S3 Linux OpenJDK Tomcat Linux OpenJDK Tomcat Linux OpenJDK Tomcat EC2 EC2 EC2 Auto Scaling EBS EBS EBS

12 Elastic Beanstalk Adds > Linux > OpenJDK > Tomcat 6/7 > Easy deployment on the nodes > Versioning for WARs on S3 > Log File storage on S3 and a nice web interface > Deployment > Monitoring > Configuration

13 Basic Elastic Beanstalk Features Application > Versioned WAR file saved in S3 > Environments > Environment Configurations Environment > Installation of a specific version of the WAR file > On AWS infrastructure (Elastic Load Balancer, Auto Scaling, EC2) > Has a specific URL ( ) > Can also create your own using Route 53 (Amazon DNS service) Environment Configuration > Set of parameters (e.g. JVM, Tomcat) for an environment Configuration templates > Starting point for custom configurations

14 Sessions in Elastic Beanstalk Data specific to a user can be stored in a HTTP session HTTP session data has to be stored How do you deal with sessions in a cluster? In Memory > Configure Load Balancer with sticky sessions > i.e. requests for the same session always go to the same node > Implemented using Cookies > However: If node fails session data is lost In database > Configure Tomcat to use a JDBC Based Store for session > Use RDS (Relational Database Service) to save the data > New servers will read the session state from RDS

15 Elastic Beanstalk: Advantages Full access and flexibility > ssh on EC2 instances to customize > Create your own AMIs with custom software > Fine tune Tomcat options Built on established AWS services > EC2, EBS, Elastic Load Balancer, Auto Scaling New versions can be installed without downtime Other services can be used > RDS (Relational Database Service) for MySQL and Oracle > can be used for session replication on Tomcat > Your own database / other software on EC2 instances > SimpleDB for a simple yet scalable database > VPC (Virtual Private Cloud) for a secure channel to your data center > Cloudfront as a Content Delivery Network > Direct Connect: Your own direct connection from data center to EC

16 Elastic Beanstalk: Getting Started Documentation at Different ways to use Beanstalk: > AWS toolkit for Eclipse > AWS online console at > Guided tour to install your first application > Command Line Tool at > SOAP API > (Very advanced)

17 Amazon Elastic Beanstalk: Conclusion Combination of existing building block Very flexible Very scalable Can easily be combined with other AWS services No additional charge over AWS services