With AWS companies now have the ability to develop and run their applications with speed and flexibility like never before. Working with an infrastructure that can be 100% API driven enables businesses to use lean methodologies and realize these benefits. This in turn leads to greater success for those who make use of these practices. In this session we'll talk about some key concepts and design patterns for Continuous Deployment and Continuous Integration, two elements of lean development of applications and infrastructures.

1. Adrian White
Continuous Deployment with Amazon Web Services
Solutions Architect, AWS
Daniel Zollinger
Senior Web Developer, CricHQ
Guest presenter:

2. CONTINUOUS
INTEGRATION

3. DEVELOPER

4. SOURCE CODE
REPOSITORY

5. SOURCE CODE
REPOSITORY
PROJECT MANAGEMENT
SERVER

6. SOURCE CODE
REPOSITORY
PROJECT MANAGEMENT
SERVER
CONTINUOUS
INTEGRATION SERVER

7. SOURCE CODE
REPOSITORY
PROJECT MANAGEMENT
SERVER
CONTINUOUS
INTEGRATION SERVER
PICK
TASKS

8. SOURCE CODE
REPOSITORY
PROJECT MANAGEMENT
SERVER
CONTINUOUS
INTEGRATION SERVER
SUBMIT
CODE

9. SOURCE CODE
REPOSITORY
PROJECT MANAGEMENT
SERVER
CONTINUOUS
INTEGRATION SERVER
SCHEDULE
BUILD

10. SOURCE CODE
REPOSITORY
PROJECT MANAGEMENT
SERVER
CONTINUOUS
INTEGRATION SERVER
RECURENT
BUILDS

11. SOURCE CODE
REPOSITORY
PROJECT MANAGEMENT
SERVER
CONTINUOUS
INTEGRATION SERVER
CODE
FETCH

12. SOURCE CODE
REPOSITORY
PROJECT MANAGEMENT
SERVER
CONTINUOUS
INTEGRATION SERVER
CODE QUALITY
TESTS
TEST
RESULTS

13. SOURCE CODE
REPOSITORY
PROJECT MANAGEMENT
SERVER
CONTINUOUS
INTEGRATION SERVER
BUILD OUTPUT

14. SOURCE CODE
REPOSITORY
PROJECT MANAGEMENT
SERVER
CONTINUOUS
INTEGRATION SERVER
DOCS
BINARIES /
PACKAGES

16. SOURCE CODE
REPOSITORY
DNS
CONTINUOUS
INTEGRATION SERVER
PROJECT
MANAGEMENT SERVER
BUILDS

18. KEY = ITERATION

19. ITERATIVELY MODIFY THE
SYSTEM TO BETTER MEET
THE EXPECTATIONS OF
YOUR USERS

20. ON-DEMAND
PAY AS YOU GO
ELASTIC

21. =
PROGRAMMABLE
PLATFORM

25. AWS
CLOUDFORMATION
STACK-BASED DEPLOYMENT
SERVICE

26. CLOUDFORMATION
TEMPLATE

28. {
"Description" : "Create RDS with username and password",
"Resources" : {
"MyDB" : {
"Type" : "AWS::RDS::DBInstance",
"Properties" : {
"AllocatedStorage" : "500",
"DBInstanceClass" : "db.m1.small",
"Engine" : "MySQL",
"EngineVersion" : "5.5",
"MasterUsername" : "MyName",
"MasterUserPassword" : "MyPassword"
}
}
}
}

29. "AWS::CloudFormation::Init" : {
"config" : {
"packages" : {
"yum" : {
"mysql" : [],
"mysql-server" : [],
"httpd" : [],
"php" : [],
"php-mysql" : []
}
},
"sources" : {
"/var/www/html" :
"https://s3.amazonaws.com/my-builds/build-v4.zip"
}
}
}

30. {
"Parameters" : {
"KeyName" : {
"Description" : "Name of an existing EC2
KeyPair to enable SSH
access to the instance",
"Type" : "String"
}
},
}

31. CLOUDFORMATION
TEMPLATE
PROCEDURAL
DEFINITION
Create it programmatically
KNOWN
CONFIGURATION
Store stack configuration in
source control
PARAMETER
DRIVEN
Dynamic and user-driven
templates
COLLABORATION
Share templates with ease
as just files

34. Template ELBs to front
secondary cache
~100 Nginx
secondary cache
servers
2-3 Nginx mid-
tier cache
servers
Stack
CLOUDFORMATION
TEMPLATE
VIDEO CACHING
INFRASTRUCTURE

35. APPLICATION
VERSIONS
&
INFRASTRUCTURE
VERSIONS

36. CLOUDFORMATION
TEMPLATE

37. TEST ENVIRONMENTS

39. 30,000 REQUESTS / SECOND
1 TB TRAFFIC / DAY

40. “…AWS seemed to be the best solution
available to allow a small, independent
company to rapidly develop and test a
completely new infrastructure, and host it.
We also loved the flexibility that AWS
allowed us, when spinning up smaller test
environments, for beta trials, QA,
localization, and during development. The
low initial cost was also crucial.”
Alex Evans, CTO

41. CONTINUOUS
DEPLOYMENT
SMALL, FREQUENT CHANGES
CONSTANTLY INTEGRATING INTO
PRODUCTION.

42. SOFTWARE DEPLOY
≠
PRODUCT LAUNCH

44. 1.5 BILLION PAGE VIEWS
$83 MILLION IN TRANSACTIONS
4.2 MILLION ITEMS SOLD
OCTOBER 2012

45. 30 DEPLOYS PER DAY
= 1 DEPLOY EVERY 20 MINUTES

46. "Production is truly the only place you
can validate your code."

51. HTTP://CODEASCRAFT.ETSY.COM/
HTTPS://GITHUB.COM/ETSY/DEPLOYINATOR

56. HTTP://SORCERY.SMUGMUG.COM/

57. AWS OPSWORKS
INTEGRATED APPLICATION
MANAGEMENT

58. MODEL, CONTROL AND AUTOMATE
AT ANY SCALE AND COMPLEXITY

59. A stack represents
your application. One
stack might be used
for staging and
another for production.
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.
A layer defines how to
setup and configure a
set of instances and
related resources such
as volumes
and software.

60. A stack represents
your application. One
stack might be used
for staging and
another for production.
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.
A layer defines how to
setup and configure a
set of instances and
related resources such
as volumes
and software.

61. A stack represents
your application. One
stack might be used
for staging and
another for production.
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.
A layer defines how to
setup and configure a
set of instances and
related resources such
as volumes
and software.

62. 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.

63. FREE OF CHARGE

64. AWS Elastic
Beanstalk
AWS
OpsWorks
AWS
CloudFormation
Amazon EC2

65. AWS Elastic
Beanstalk
AWS
OpsWorks
AWS
CloudFormation
Amazon EC2
CONVENIENCE CONTROL

66. AWS Elastic
Beanstalk
AWS
OpsWorks
AWS
CloudFormation
Amazon EC2
CONVENIENCE CONTROL
HIGH-LEVEL DO IT YOURSELF

67. LOAD TESTING

72. 11.6s
Mean time between
deployments
(weekday)
1,079
Max number of
deployments in a
single hour
10,000
Mean number of
hosts
simultaneously
receiving a
deployment
30,000
Max number of
hosts
simultaneously
receiving a
deployment
DEPLOYMENTS AT
AMAZON.COM

73. CONTINUOUS
INTEGRATION
CONTINUOUS
DEPLOYMENT

74. CONTINUOUS
DEPLOYMENT
=
CONTINUOUS
EXPERIMENTATION

75. CONTINUOUS
DEPLOYMENT
=
CONTINUOUS
IMPROVEMENT

76. INNOVATE

77. « Want to increase innovation?
Lower the cost of failure »
Joi Ito

78. SPEED AND AGILITY
Experiment
Often
Fail quickly at
a low cost
More Innovation
Experiment
Infrequently
Failure is
expensive
Less Innovation
“ON-PREMISE”

79. Daniel Zollinger, Dave Robertson & Leo Gui

83. Introduction to OpsWorks
• OpsWorks is a deployment platform, like Elastic Beanstalk & CloudFormation
• A Stack contains EC2 instances that represent a deployment environment
• A Layer consists of instances that play a certain role in the stack
• Built on Chef, a configuration management tool
• Instances are configured via Chef Recipes
• You deploy Applications to Layer instances

85. OpsWorks & Chef
• Open Source recipes and enthusiastic fledgling community
• Full Stack optimized for standard web apps
• But easily configurable and extendable via Chef recipes
• Visibility of Chef recipes to allow for rapid extensibility and configuration
• Life cycle, adding nodes to a stack is easy to configure through chef recipes,
callbacks and hooks
• Chef Recipes are triggered on lifecycle events
• Scale by schedule and capacity

89. Business Benefits
• Zero downtime (mostly)
• Small team, no SysAdmins, prefer DevOps-orientated solutions

91. Business Benefits
• Zero downtime (mostly)
• Small team, no SysAdmins, prefer DevOps-orientated solutions
• OpsWorks gives you the same cost/benefit as EC2
• Schedule & capacity scaling

93. Business Benefits
• Zero downtime (mostly)
• Small team, no SysAdmins, prefer DevOps-orientated solutions
• OpsWorks gives you the same cost/benefit as EC2
• Schedule & capacity scaling
• Development  production parity, quickly and cheaply deploy new test
environments
• Responsive development process

96. Integrating with AWS
• Basic IAM integration & EC2 security groups
• While RDS and ElastiCache may be coming soon. They are still configurable
out of the box with OpsWorks and are available as services.
• CricHQ has successfully integrated both services without much hassle
• Recently added ELB support shows active improvements
• No integration with CloudFormation
• Access to Raw EC2 instances, and ability to extend default functionality

97. The Future
• Its early days, but things look very promising
• OpsWorks isn’t perfect, but it is powerful enough to easily configure for your
own business requirements
• Wish list: More services, layers, flexibility & better scaling

99. The Future
• It’s early days, but things look very promising
• OpsWorks isn’t perfect, but it is powerful enough to easily configure for your
own business requirements
• Wish list: More services, layers, flexibility & better scaling
• Our Arduino continuous deployment, build failure, staff targeting nerf missile
launcher
• Come chat to us…

100. Thank you!