Downloaded 41 times
![config/database.yml production: <<: *default adapter: postgresql encoding: unicode database: <%= ENV['RDS_DB_NAME'] %> username: <%= ENV['RDS_USERNAME'] %> password: <%= ENV['RDS_PASSWORD'] %> host: <%= ENV['RDS_HOSTNAME'] %> port: <%= ENV['RDS_PORT'] %> These environment variables will be automatically declared by Elastic Beanstalk when we create an RDS instance](https://image.slidesharecdn.com/20160928thefamily-160929142031/75/Deploying-your-web-application-with-AWS-ElasticBeanstalk-20-2048.jpg)
![.ebextensions/packages.config packages: yum: postgresql94-devel: [] This directive will install the postgres94-devel package on your instances. It is required to install the ‘pg’ Ruby gem. .ebextensions provides lots of options to configure and customize your Elastic Beansltalk applications. The documentation is your friend https://docs.aws.amazon.com/fr_fr/elasticbeanstalk/latest/dg/ebextensions.html](https://image.slidesharecdn.com/20160928thefamily-160929142031/75/Deploying-your-web-application-with-AWS-ElasticBeanstalk-21-2048.jpg)
![Accessing other AWS services // Login to one of our app servers $ eb ssh // Connect to our RDS instance [ec2-user] psql -h RDS_ENDPOINT -p 5432 -U user -d ebdb ebdb=> dt ebdb=> select * from posts // Connect to our ElastiCache cluster [ec2-user] echo "stats" | nc ELASTICACHE_ENDPOINT 11211 [ec2-user] printf "set mykey 0 60 4 rndatarn" | nc ELASTICACHE_ENDPOINT 11211 [ec2-user] echo "get mykey" | nc ELASTICACHE_ENDPOINT 11211](https://image.slidesharecdn.com/20160928thefamily-160929142031/75/Deploying-your-web-application-with-AWS-ElasticBeanstalk-24-2048.jpg)
Uploaded byJulien SIMON
Deploying your web application with AWS ElasticBeanstalk
This document summarizes AWS Elastic Beanstalk, which is a PaaS that allows developers to deploy and manage applications in the AWS cloud. It supports many programming languages and frameworks out of the box. Elastic Beanstalk handles the infrastructure management including provisioning servers, load balancing, auto-scaling and monitoring. Developers can focus on their code without worrying about managing the underlying infrastructure. The document provides an example of deploying a Ruby on Rails application to Elastic Beanstalk and accessing other AWS services.
Deploying your web application with AWS ElasticBeanstalk
- 1. © 2015, AmazonWeb Services, Inc. or its Affiliates. All rights reserved. Deploying your web application with AWS Elastic Beanstalk Julien Simon Principal Technical Evangelist julsimon@amazon.fr @julsimon
- 2. Breaking news! AWS willopen a Region in France in 2017
- 3.
- 4. ElasticBeanstalk vs. DIY Yourcode HTTP server Application server Language interpreter Operating system Host Elastic Beanstalk configures each EC2 instance in your environment with the components necessary to run applications for the selected platform. No more worrying about logging into instances to install and configure your application stack. Focus on building your application
- 5. All you needis code 01 02 03 04 Region Stack (container) type Single-instance Load balanced with Auto Scaling Or Database (RDS) Optional Your code Supported platforms ‘eb’ CLI
- 6.
- 7.
- 8. Managed infrastructure • Preconfiguredinfrastructure: • Single-instance (dev, low cost) • Load-balanced, Auto Scaling (production) • Web and worker tiers • Elastic Beanstalk provisions necessary infrastructure resources, such as the load balancer, Auto Scaling group, security groups, database (optional), etc. • Provides a unique domain name for your application (e.g., yourapp.elasticbeanstalk.com)
- 9.
- 10.
- 11. Create a Gitrepository with AWS CodeCommit $ aws codecommit create-repository --repository-name blog --region us-east-1 --repository-description "ElasticBeanstalk demo" $ git clone ssh://git-codecommit.us-east- 1.amazonaws.com/v1/repos/blog
- 12. Create a newRails application $ rails new blog $ cd blog $ git add . $ git commit -m "Initial version"
- 13. Create a newRails application $ rails new blog $ cd blog $ git add . $ git commit -m "Initial version"
- 14. Add a ‘post’resource to the application $ rails generate scaffold post title:string body:text $ bundle exec rake db:migrate $ git add . $ git commit -m "Add post resource" $ rails server $ open http://localhost:3000/posts
- 15. Initialize a Rubyapplication in Elastic Beanstalk $ eb init blog -p Ruby -r eu-west-1 $ git add .gitignore $ git commit -m "Ignore .elasticbeantalk directory"
- 16. Create a ‘blog-dev’environment Single instance: no Auto Scaling, no load balancing Size: t2.micro instance (default value) $ eb create blog-dev --single --keyname aws-eb --envvars SECRET_KEY_BASE=`rake secret`
- 17. Update a pageand redeploy on ‘blog-dev’ $ vi app/views/posts/index.html.erb $ git add app/views/posts/index.html.erb $ eb use blog-dev $ eb deploy –staged $ git commit -m "Add message on post page" $ eb deploy
- 18. Create a productionbranch for the blog $ git branch prod $ git checkout prod Now we have to modify 3 files to add support for Postgres: Gemfile config/database.yml .ebextensions/packages.config
- 19. Gemfile group :development, :testdo # Use sqlite3 as the database for Active Record gem 'sqlite3’ end group :production do # Use PostgreSQL as the database for Active Record gem 'pg', '~> 0.18.1’ end
- 20. config/database.yml production: <<: *default adapter: postgresql encoding:unicode database: <%= ENV['RDS_DB_NAME'] %> username: <%= ENV['RDS_USERNAME'] %> password: <%= ENV['RDS_PASSWORD'] %> host: <%= ENV['RDS_HOSTNAME'] %> port: <%= ENV['RDS_PORT'] %> These environment variables will be automatically declared by Elastic Beanstalk when we create an RDS instance
- 21. .ebextensions/packages.config packages: yum: postgresql94-devel: [] This directivewill install the postgres94-devel package on your instances. It is required to install the ‘pg’ Ruby gem. .ebextensions provides lots of options to configure and customize your Elastic Beansltalk applications. The documentation is your friend https://docs.aws.amazon.com/fr_fr/elasticbeanstalk/latest/dg/ebextensions.html
- 22. Commit these changesto the production branch $ git add Gemfile config/database.yml .ebextensions $ git commit -m "Use Postgres for production” $ git push Now let’s create a proper production environment : running in a VPC, auto-scaled, load-balanced, with larger instances and backed by RDS Postgres. Ready?
- 23. Create a ‘blog-prod’environment $ aws ec2 describe-subnets $ export VPC_SUBNETS=subnet-63715206,subnet-cbf5bdbc,subnet-59395b00 $ eb create blog-prod -k aws-eb --vpc.id=vpc-def884bb --vpc.elbpublic --vpc.publicip --vpc.elbsubnets $VPC_SUBNETS --vpc.ec2subnets $VPC_SUBNETS --vpc.dbsubnets $VPC_SUBNETS --instance_type m4.large --database.engine postgres --database.version 9.4.5 --database.instance db.m4.large --database.size 5 --database.username YOUR_USERNAME --database.password YOUR_PASSWORD --envvars SECRET_KEY_BASE=`rake secret`
- 24. Accessing other AWSservices // Login to one of our app servers $ eb ssh // Connect to our RDS instance [ec2-user] psql -h RDS_ENDPOINT -p 5432 -U user -d ebdb ebdb=> dt ebdb=> select * from posts // Connect to our ElastiCache cluster [ec2-user] echo "stats" | nc ELASTICACHE_ENDPOINT 11211 [ec2-user] printf "set mykey 0 60 4 rndatarn" | nc ELASTICACHE_ENDPOINT 11211 [ec2-user] echo "get mykey" | nc ELASTICACHE_ENDPOINT 11211
- 25. More CLI $ ebstatus $ eb health $ eb scale $ eb logs $ eb terminate $ aws elasticbeanstalk …
- 26.
- 27. Testing and tuningyour application • Pick performance metrics you want to optimize for (e.g., latency, concurrent users, number of web requests, etc.) • Load test your application: • Start with Auto Scaling minimum and maximum of 1 to understand how your application degrades under an overload condition • Understand available metrics and how they correspond to your performance metric • Configure Auto Scaling to optimize for performance metrics: • Number of instances to add on scale out • Breach duration • Metric to scale on • Tune the back end (DynamoDB, RDS, etc.) for optimal performance; leave enough headroom for full scale out
- 28. Deployment option (rolling) Pros: •Deployments are fast (20-60 sec.) Cons: • Slower rollback because the previous application version must be redeployed • Possibility of state build-up on long-running environments
- 29. Deployment option (blue/green) Pros: •Fast rollback because the environment running the previous version has not been modified in any way • Ensures no state build up on environments Cons: • Deployments take longer than rolling deployments (2-5 min.) because a new environment must be created • Clients (i.e., mobile devices) might cache DNS addresses and not respect DNS TTL, resulting in staggered/non-deterministic traffic rollover to the new environment
- 30. AWS Elastic Beanstalk •Platform as a Service • Supports PHP, Java, .NET, Node.js, Python, Go, Ruby, IIS, Glassfish, Tomcat and Docker • Developer-friendly CLI : ‘eb’ • Built-in monitoring (Amazon Cloudwatch), networking (Amazon VPC), load balancing (Amazon ELB) and scaling (Auto Scaling) • Relational data tier is available through Amazon Relational Data Service (RDS) • Can also integrate with many AWS services The simplest and most intuitive way to deploy your applications This should really be your default option for deployment https://aws.amazon.com/fr/elasticbeanstalk/ https://aws.amazon.com/fr/blogs/aws/category/aws-elastic- beanstalk/https://aws.amazon.com/releasenotes/AWS-Elastic-Beanstalk
- 31.
- 32. AWS Enterprise Summit– 27/10/2016, Paris http://amzn.to/1X2yp0i
- 33. Thank you! Julien Simon PrincipalTechnical Evangelist julsimon@amazon.fr @julsimon