DevOps for the Enterprise: Automating Deployments

2,249
-1

Published on

This session explains the different services and techniques to automate deployments on AWS, using tools such as AWS CloudFormation, OpsWorks, or PowerShell.

Who should attend:

Developers, DevOps Manager, Configuration Managers, Test Managers and Architects

Demos associated with this webinar:
• Creating a CloudFormation script that describes the target environment
• Deploying the build artifacts onto the target environment

View the webinar: http://youtu.be/5WwWylmZE7Y

Published in: Technology

DevOps for the Enterprise: Automating Deployments

  1. 1. DEVOPS WEBINAR SERIES – EPISODE 3
 
 ENABLING BUSINESS AGILITY:
 AUTOMATING DEPLOYMENTS ianmas@amazon.com @IanMmmm
  2. 2. BASELINE B R A N C H B R A N C H B R A N C H ELASPED TIME IN TEG R ATIO N IN TEG R ATIO N IN TEG R ATIO N OLD WORLD: INFRASTRUCTURE IN weeks ENTERPRISES CAN’T AFFORD TO BE SLOW THE MORE I PRACTICE THE LUCKIER I GET - GARY PLAYER CLOUDFORMATION TEMPLATE PR EVIO U SLY…
  3. 3. ARTEFACT PRODUCTION 
 ! ! ! 
 PROD / TEST ENVIRONMENTS DEPLOY
  4. 4. AUTOMATED DEPLOYMENT
  5. 5. AUTOMATION
 Deterministic & reproducible results
 Faster reproduction of time-consuming tasks
  6. 6. C ASE STU D Y
  7. 7. HTTP://SORCERY.SMUGMUG.COM/
  8. 8. 1. Produce the artifact from the CI platform
 2. Store the artifact in a repository
 3. Deploy the artifact from the repository into the target environment
  9. 9. DEMO ! AUTOMATED DEPLOYMENT WITH JENKINS, AWS CLOUDFORMATION, AMAZON S3 & AMAZON EC2
  10. 10. DEPLOYMENT OPTIONS STATIC vs DYNAMIC
  11. 11. CREATE A MACHINE IMAGE CONFIGURE AT LAUNCH STATIC DYNAMIC Time consuming configuration (startup time) Static configurations (less change management)
  12. 12. CREATE A MACHINE IMAGE CONFIGURE AT LAUNCH STATIC DYNAMIC Continuous deployment (latest code) Environment specific (dev- test-prod)
  13. 13. CREATE A MACHINE IMAGE CONFIGURE AT LAUNCH STATIC DYNAMIC Continuous deployment (latest code) Environment specific (dev- test-prod) Time consuming configuration (startup time) Static configurations (less change management)
  14. 14. AWS OPSWORKS INTEGRATED APPLICATION MANAGEMENT
  15. 15. A stack represents your application. One stack might be used for staging and another for production. A layer defines how to setup and configure a set of instances and related resources such as volumes and software. Tell OpsWorks where it can find your code and define any additional deployment tasks. OpsWorks will take care of deploying your app. Scale your stack based on time or load. Clone your production stack to a different region. Automate workflows for common tasks.
  16. 16. A stack represents your application. One stack might be used for staging and another for production. A layer defines how to setup and configure a set of instances and related resources such as volumes and software. Tell OpsWorks where it can find your code and define any additional deployment tasks. OpsWorks will take care of deploying your app. Scale your stack based on time or load. Clone your production stack to a different region. Automate workflows for common tasks.
  17. 17. A stack represents your application. One stack might be used for staging and another for production. A layer defines how to setup and configure a set of instances and related resources such as volumes and software. Tell OpsWorks where it can find your code and define any additional deployment tasks. OpsWorks will take care of deploying your app. Scale your stack based on time or load. Clone your production stack to a different region. Automate workflows for common tasks.
  18. 18. A stack represents your application. One stack might be used for staging and another for production. A layer defines how to setup and configure a set of instances and related resources such as volumes and software. Tell OpsWorks where it can find your code and define any additional deployment tasks. OpsWorks will take care of deploying your app. Scale your stack based on time or load. Clone your production stack to a different region. Automate workflows for common tasks.
  19. 19. AWS Elastic
 Beanstalk AWS
 OpsWorks AWS
 CloudFormation Amazon EC2
  20. 20. AWS Elastic
 Beanstalk AWS
 OpsWorks AWS
 CloudFormation Amazon EC2 CONVENIENCE CONTROL
  21. 21. AWS Elastic
 Beanstalk AWS
 OpsWorks AWS
 CloudFormation Amazon EC2 CONVENIENCE CONTROL HIGH-LEVEL DO IT YOURSELF
  22. 22. CHEF & CLOUDFORMATION CloudFormation is for environment initialization Chef is for deployment & updates
  23. 23. BEST PRACTICES
  24. 24. IF YOU NEED TO SSH INTO YOUR SERVERS FOR DEPLOYMENT, YOUR DEPLOYMENT PROCESS IS BROKEN
  25. 25. DEPLOYMENTS
 HAVE TO BE AUTHORIZED
  26. 26. CONTROL WHO CAN DO WHAT IN YOUR AWS ACCOUNT
  27. 27. USE AWS IAM
 IDENTITY & ACCESS MANAGEMENT BEST PR AC TIC E
  28. 28. DEV & TEST ENVIRONMENT AWS ACCOUNT A PRODUCTION
 ENVIRONMENT AWS ACCOUNT B BEST PR AC TIC E
  29. 29. aws.amazon.com/blogs/aws ! aws.amazon.com/new @AWScloud @AWS_UKI
  30. 30. DEVOPS WEBINAR SERIES – EPISODE 2
 
 ENABLING BUSINESS AGILITY:
 DEVOPS FOR THE ENTERPRISE ianmas@amazon.com @IanMmmm
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×