1. Continuous Deployment Practices, with Production, Test
and Development Environments Running on AWS
Chris Munns, Solutions Architect, Chris Barclay, Senior
Product Manager, and Mike Limcaco, Solutions Architect

2. This talk:
• Not going to spend a lot of time talking about Continuous
Integration(CI) and Continuous Deployment(CD) philosophy
• Will spend more time talking about how AWS can help you if
practicing CI and CD are your goals
• Examples to get you thinking, but not the only way
• AWS + Open Source solutions

3. • Continuous Integration
• Continuous Deployment

4. • Continuous Integration Techniques and tools to
• Continuous Deployment implement continuous
processes of applying quality
control in general small
pieces of effort, applied
frequently, to improve the
quality of software, and to
reduce the time taken to
deliver it.

5. • Continuous Integration Techniques and tools to
• Continuous Deployment improve the process of
software delivery, resulting in
the ability to rapidly, reliably,
and repeatedly push out
enhancements and bug fixes
to customers at low risk and
with minimal manual
overhead.

6. • Continuous Integration Getting code from
• Continuous Deployment developers’ brains,
through their fingers,
to production quickly
and efficiently, with
positive results.

7. Continuous Integration & Deployment on AWS
• Treat infrastructure as code
• Automate the testing/deploy process end to end
• Make sure environments mimic each other as closely as possible
• Use repeatable patterns between environments at a different scale
• Use different cost models where it makes sense
• Simplify and streamline the deploy process
• Let AWS services handle control flows
• Track everything (instance metrics, application metrics, logs)

8. es

9. In today’s infrastructure, everything is code.
From the applications developers are writing, to
your configuration management tools, to things like
CloudFormation templates or scripts that call AWS APIs.

10. Since Infrastructure is code, let’s treat it like code!
– Not JUST Revision control!
– Make use of bug tracking/ticketing systems
– Peer reviews of changes before they happen
– Establish infrastructure code patterns/designs
– Test infrastructure changes like code changes

11. Let’s talk about
the journey our
code is going to
take to production

12. 1.Code gets written
2.Code gets tested
3.Code gets deployed
4.Code gets consumed

13. 1.Code gets written
– Someone writes code and commits to revision
control system
– Hooks in revision control, system kicks off CI work
2.Code gets tested
– Unit tests, integration tests, db tests, smoke tests,
UI tests
– “Light green, trap clean” OR GOTO STEP 1
3.Code gets deployed
– Ship out that code
4.Code gets consumed
– Customers use it, love it, victory, profit, vacation in
Bora Bora

14. 1.Software ( tools, services, scripts )
2.Infrastructure Environments ( dev, test, prod )
3.Process ( deploy, monitor, alert, track )

15. 1.Software ( tools, services, scripts )
2.Infrastructure Environments ( dev, test, prod )
3.Process ( deploy, monitor, alert, track )
We need tools to help work with all of the
above quickly and more efficiently