AWS: Fast Environments =Fast and Flexible Deployments

Matthew Cwalinski

The ProcessLast in line gets the blame.

The ProcessThe order of things

Source

DevelopPlan Deploy

The ProcessThe order of things

Source

DevelopPlan Deploy

The ProcessWhy the deployment step was a problem

Source

• Manual Process

• Does New Code Break Server? (yes)

• Snowflake (unique) Servers - Every server was different

• No Change Management - Find the code and push the code

The ChangeBe an agent of change

The ChangeAutomate Everything

Source

• Automate Testing,Security and the entire process

• All code/changes should be production ready

• Treat your servers like cattle. Phoenix upgrading.

• Continuously Integrate and Deploy

The ChangeMost Importantly

Automate InfrastructureInfrastructure as Code

The HowHow do we automate infrastructure?

The HowHow do we automate infrastructure?

Source

• Set of tools

• Repeatable process

• If it’s boring - it’s working

The HowOur Tools of the Trade

Amazon Web ServicesThe Big Guns

GruntDoer of Dirty Work

GitHubThe Control Freak

JenkinsThe Keeper of Order

AWS: CloudFormation

Deployment StepsRepeated over and over again

Source

1 2 43

Grunt + GitHub Jenkins AWS Application

UneventfulBoring deployments = successful deployments

The ReviewHave we fixed the problem?

Source

• Manual Process• Continuous Integration and Deployment

• Does New Code Break Server?• No

• Snowflake (unique) Servers - Every server was different• Each server is identical and new

• No Change Management - Find the code and push the code• It is always production ready and tested

The ReviewDid we automate everything?

Source

• Automate Testing and Security• Grunt!

• All code/changes should be production ready• GitHub

• Treat your servers like cattle. Phoenix upgrading.• CloudFormation

• Continuously Integrate and Deploy• Jenkins

ConclusionI must conclude here.