This document discusses AWS CodeDeploy, a service that automates software deployments to EC2 instances and on-premises servers. It provides an overview of CodeDeploy's key concepts including applications, deployment groups, deployment configurations, and hooks. It also shows examples of how CodeDeploy can be used for automated deployments across development, test, and production environments. The document suggests additional features like CloudFormation support and integration with CI/CD tools.

1. AWS CodeDeploy:
Automating Your Software Deployments
Matthew Trescot
Manager, Solutions Architecture

2. (Where my dogs at?)

3. I’m quitting!
(Joke)

5. We got the business plan together…
1. Dog addressable market - 525 million dogs
2. Dogs need suits
3. The existing dog suit market is ready to be disrupted…
the quality of dog fashion lacks our unique perspective.
We’re not selling dog suites, we’re selling a lifestyle.
4. ???
5. Profit.

6. Building Block Service
1. Easy to
integrate
2. Available
everywhere
3. Scaled for
our biggest
customers

8. Application
“Any collection of content that you want
to distribute to your servers in a single
deployment”
Web Server
Framework
Content

9. Deployment Group
“A collection of instances you want
to deploy to as a group”
Dev Test Prod
v2.0 v1.2 v1.1
v2.0 v1.2 v1.1
v2.0 v1.2 v1.1

10. AppSpec fileos: linux
files:
- source: Config/config.txt
destination: webapps/Config
- source: Service
destination: /webapps/DogSuit
hooks:
ApplicationStop:
- location: Scripts/Deactivate_Service
BeforeInstall:
- location: Scripts/Flush_Logs.sh
AfterInstall:
- location: Scripts/Decrypt_Secrets.sh
ApplicationStart:
- location: Scripts/Start_Pooch_Style_Service.sh
timeout: 3600
ValidateService:
- location: Scripts/Check_Dogs_Barking.sh
runas: codedeployuser

11. AppSpec fileos: linux
files:
- source: Config/config.txt
destination: webapps/Config
- source: Service
destination: /webapps/DogSuit
hooks:
ApplicationStop:
- location: Scripts/Deactivate_Service
BeforeInstall:
- location: Scripts/Flush_Logs.sh
AfterInstall:
- location: Scripts/Decrypt_Secrets.sh
ApplicationStart:
- location: Scripts/Start_Pooch_Style_Service.sh
timeout: 3600
ValidateService:
- location: Scripts/Check_Dogs_Barking.sh
runas: codedeployuser

12. AppSpec fileos: linux
files:
- source: Config/config.txt
destination: webapps/Config
- source: Service
destination: /webapps/DogSuit
hooks:
ApplicationStop:
- location: Scripts/Deactivate_Service
BeforeInstall:
- location: Scripts/Flush_Logs.sh
AfterInstall:
- location: Scripts/Decrypt_Secrets.sh
ApplicationStart:
- location: Scripts/Start_Pooch_Service.sh
timeout: 3600
ValidateService:
- location: Scripts/Check_Dogs_Barking.sh
runas: codedeployuser
ApplicationStop
BeforeInstall
AfterInstall
ApplicationStart
ValidateService
DownloadBundle
Install
Start
End

13. Deployment Config
v2 v2 v2 v2 v2 v2 v2 v2All-at-once
Min. healthy hosts = 0
v2 v2 v2 v2 v1 v1 v1 v1Half-at-a-time
Min. healthy hosts = 50%
v2 v2 v1 v1 v1 v1 v1 v1[Custom]
Min. healthy hosts = 75%
v2 v1 v1 v1 v1 v1 v1 v1One-at-a-time
Min. healthy hosts = 99%

14. • minimal host footprint
• quick to get started
• little to no automated
validation
Development
(Early fit algorithm needs work.)

16. Development
• Minimal host footprint
• quick to get started
• little to no automated
validation
• Host footprint enables
load testing
• Debug messaging
present
• Automated validation
Test
(Dated style, but good fit)

17. What’s changing in test?
Auto Scaling supportRequest Routing with ELBValidation and testing

19. • Over scaled for
production workloads
• Debugging through
logs
• More validation
Production
(Looking Sharp.)

20. if [ "$DEPLOYMENT_GROUP_NAME" == “Production" ]
then
/user/bin/ConfigSalesBanner
fi
How do deployments change to Production?
Large Fleets, with redundancyCustom Deployment Configs
“1/3 at a time”
Environment Variables

22. Test ProductionDevelopment
(See you at the launch party!)

23. CloudFormation Support
What else can we do with CodeDeploy?
Reactive DeploymentsCI/CD and Config MGMT PartnersMultiple PlatformsSNS Notifications

24. CIRCLECI + AWS CODE DEPLOY
Who we are and what we do
CircleCI was founded in 2011 with the mission of building a state of
the art Continuous Integration and Delivery platform for developers.
We provide clean, modern tooling to take your build and test
automation out of the dark ages. With CircleCI, it’s easy to scale
your builds and tests without a team to manage a dedicated
cluster. Designed for productivity, CircleCI provides tools like auto-
parallelization, SSH-based debugging, and automatic project
setup, allowing developers to ship faster and more reliably.

25. TURING CODE
LEV LAZINSKIY

26. TURNING CODE INTO SOFTWARE
Version Control System Production
BUILD TESTDEPLOY
C
O
D
E
SOFTWARE

27. DEFINITIONS
▸ Continuous feedback loop for development team
▸ Test every change made to the code base
▸ Unit
▸ Integration
▸ Functional
▸ Static Analysis
CONTINUOUS INTEGRATION

28. DEFINITIONS
CONTINUOUS DEPLOYMENT
▸ Continuously deploying changes made to your code base to your staging and
production environments
▸ Confidence Increases with proper CI
▸ Automated, Decentralized and Repeatable

29. DEFINITIONS
CONTINUOUS DELIVERY
▸ Making the delivery of your product seamless and transparent for your customers
▸ Shipped vs. Shippable

30. LIVE DEMO

31. QUESTIONS?

32. Thank you!
…Questions?