Infrastructure as Code - AWS CloudFormation
- 1.
- 2. How do youdeploy?
- 3.
- 4.
- 6.
- 7.
- 8. Codified Configuration that can be VersionManaged Code Reviewed Release-managed
- 9.
- 10. AWS specific (surprise!!) JSON/YAML “Templates”create “Stacks” Update/Rollout made easy Visual diagramming
- 11.
- 12.
- 13. Load Balancing Artifact Management Database Management Security and AccessControl Naming Routing Internet Access
- 14.
- 15.
- 16.
- 17.
- 18. Private Customized AMIs AvailabilityAcross Regions Scalable Process for Updates * as Code
- 19.
- 21.
- 22. Parameterize Use Outputs Reusability vsMaintainability Use Autoscaling, Launch Configs and EIPs Use Mappings API calls and IAM Instance Profiles Capabilities are required Be Mindful of Costs
- 23.
Editor's Notes
- #3 Typical deployment story Request for instances by specifying specs Manage specs manually Setup manually or using something like Puppet Go to production
- #4 What happened above Infrastructure management App provisioning (automation of this layer is well known now)
- #6 Manage vs Orchestrate What? Manual management of VMs, Networks vs Automatoin of this confiugraiton through code Why? Snowflake vs Immutable deployment How? Through codification of infrastructure configuration
- #11 Vendor specific JSON or YAML based Separate API exposing AWS resources Rollout is made easy Minor Visual part of the service
- #13 This is the what is usually involved But there’s more to this than this initial config
- #14 Things quickly become complex and the need for a cross-stack management descipline arises We should create a Template’ Continously test Release Do changes only in the template and update
- #15 Create from UI Show created resources Go through the CF script and map to resources and explain how they were created
- #18 Need for private AMIs Introduce Packer To be contd.