Leveraging Chef, Packer, and Habitat for Effortless AMI Deployments
summary
Describes a layered AMI pipeline that uses Packer plus Chef Infra to bake a base AMI with OS patches and Habitat installed, then a second application AMI that embeds a built artifact pulled from Artifactory via PowerShell, and uses SSM parameters for secrets and env vars. Chef Habitat packages are built, uploaded to Builder, and the Habitat supervisor on boot auto-pulls updates with strategy at once, replacing the need for a Chef Server; chef-client runs on a five minute cadence for local config. The setup runs in production at uShip and enables artifactized, repeatable, environment-specific deployments.
AI-written summary · about
chapters (7)
- 0:00Introduction and background
- 3:55Repeatable AMI deployments with Packer
- 9:17Configurable infrastructure with Habitat
- 11:28Effortless infrastructure concept
- 17:50Environment configuration and deployment
- 20:41Pipeline and updates workflow
- 21:42Q&A and resources
related talks
39mAchieving Cloud Agnostic Application Deployment with Habitat
14mAMI Creation And IaC Deploys via Semaphore
05mIgnite: Introduction to Habitat
31mHabitat Builder: Cloud Native Application Automation - Elliott Davis & Fletcher Nichol, Chef.io
11mAutomating AMIs for reliability, security, and cost (PRT074)
42mHow Habitat can Boost your Chef Ecosystem
40mJenkins and Chef: Infrastructure CI and Application Deployment
28mHabitat Automation that travels with the app