This document discusses why Docker was chosen for an organization's infrastructure, how it is being used and controlled, and the security measures in place. Docker was selected because it provides isolated environments through immutable images, has an easy to use API, a large community, and facilitates faster deployment and portability. The organization controls Docker services through its deployment system which defines who can deploy, what operations are allowed, includes flow control and auditing. Security measures implemented include MFA, image scanning, private registries, vault for secrets, VPC configuration, and AWS security groups.
1 of 7
Download to read offline
More Related Content
Docker appsflyer
2. Why We Chose Docker?
Isolated environment, immutable
images
Easy to use and well documented API
Large community
Very good ecosystem
Faster deployment
Portability
Ideal for microservices
5. How Do We Control Our Services?
Our deployment system
Who authorized to deploy?
Type of operations (depoy,
restart, stop, start, revert,
branch, etc.)
Flow control
Operation audit
Feedback loop
Testing & Staging environments
6. Security & Control Measures
MFA
Image scanning & traffic
monitoring
Immutable images, local
repositories for internal
dependencies
Private registry hosted in our DC
Deployment flow control & Audit
Vault (for secrets clean code)
VPC & Private subnets
AWS SG