Companies are frequently using outdated process and tools for delivering infrastructure and applications, and are finding it to be difficult to migrate from on-premises data centers to the cloud. AWS OpsWorks for Chef Automate is a complete solution for the automation of infrastructure, applications, and compliance across the entire technology stack. Join us to learn more how Chef Automate can help by delivering, deploying, and managing infrastructure and apps with increasing speed, improved efficiency, and decreasing risk. Join us to Learn: How to configure, deploy, and scale cloud and on-premises infrastructure simply and securely by automating infrastructure as code. How Chef can help you use configuration management to save time. Best practices of setting up your infrastructure, host configuration and applications. Who Should Attend: Cloud/Solution/Software/Enterprise Architects, DevOps Managers, Senior Technical Managers in Software Development and Operations, Site Reliability Engineers (SREs) AWS Speaker: Isaiah Weiner, Sr. Solutions Architect, AWS Partner Speaker: Sean Carolan, Partner Architect, Chef Customer Speaker: Ronald Lipke , Senior DevOps Engineer, Gannett

1. Achieve Scale & Velocity with
AWS OpsWorks for
Chef Automate
Isaiah Weiner • Senior Solutions Architect, AWS
Sean Carolan • Partner Architect, Chef
Ron Lipke • Senior DevOps Engineer, Gannett

2. DevOps on the AWS Cloud
Isaiah Weiner • Partner Solutions Architect

3. Traditional Development Models are Obsolete
 Business is increasingly software-driven
 End-users expect both continuous improvement and stability from
applications
 IT needs to be able to provision infrastructure as rapidly as developers
demand it
 An organization’s pace of innovation is largely constrained by their
ability to develop applications

4. Increase
 Business agility
 Application stability
 Ability to meet customer demand
 Time spent on innovation
 Security
Decrease
 Length of development cycles
 Time to market
 Deployment failures and rollbacks
 Time to recover upon failure
 Operational overhead
DevOps Can Help
DevOps practices enable companies to innovate at a higher velocity
for customers

5. Infrastructure
as Code
Microservices Logging and
Monitoring
Continuous Integration/
Continuous Delivery
DevOps on AWS
AWS provides on-demand infrastructure resources and tooling built to
enable common DevOps practices

6.  Provision the server, storage, and networking capacity you
need on demand
 Deploy independently, as a single service, or a group of
services
 Make configuration changes repeatable and standardized
 Build custom templates to provision resources in a
controlled and predictable way
 Use version control to keep track of all changes made to
your infrastructure and application stack
Infrastructure as Code
Replace traditional infrastructure provisioning and management with
code-based techniques

7.  Build services around the business capabilities you require
 Scale up and down as required with virtually no notice
 Make configuration code changes repeatable and
standardized
 API-driven model enables management of infrastructure
with language typically used in application code
 Free developers from manually configuring operating
systems, system applications, and server software
Microservices
Build applications as a set of small services that communicates with other
services through APIs

8.  Maintain visibility and auditability of activity in your
application infrastructure
 Assess how application and infrastructure performance
impact end-user experience
 Gain insight into the root causes of problems or
unexpected changes
 Support services that must be available 24/7 as a result of
continuous integration/ continuous delivery
 Create alerts based on thresholds you define
Logging and Monitoring
Capture, categorize, and analyze data and logs generated by applications
and infrastructure

9.  Model and visualize your own custom release workflow
 Automate deployments of new code
 Improve developer productivity and deliver updates faster
 Find and address bugs quicker with more frequent and
comprehensive testing
 Store anything from source code to binaries using existing
Git tools
Continuous Integration and Continuous Delivery
Rapidly and reliably build, test, and deploy your applications, while
improving quality and reducing time to market.

10. Get started quickly
and pay as you go
Automate systems
operations
Scale without
infrastructure constraints
Improve visibility
and security
Leverage fully
managed services
Benefits of DevOps on AWS

11. Chef Automate
Sean Carolan • Partner Architect, Chef

12. About Chef
 Manages deployment and ongoing
automation
 Defines reusable resources and
infrastructure state as code
 Scales elegantly from one managed node
to tens of thousands across multiple
complex environments
 Supports content available for all common
automation tasks
Infrastructure
automation
and delivery
at scale

13. Benefits of Chef Automate
Decreased Risk
 Define compliance rules as code
 Deliver continuous compliance as
part of standard workflow
Increased Speed
 Package infrastructure and app
configuration as code
 Continuously automate
infrastructure and app updates
Improved Efficiency
 Define and execute standard
workflows and automation
 Audit and measure effectiveness
of automation

14. Deployment Options
AWS OpsWorks for
Chef Automate
● Native Service on AWS
● Provides full Chef Automate
● Includes backup and upgrades
● Customer is billed by AWS
● Support is provided by AWS
● Customer Success purchasing
options
Chef Automate from
AWS Marketplace
● Provides full Chef Automate
● Customer needs to manage
backup and upgrades
● Customer is billed by AWS or by
AWS reseller
● Support is provided by Chef
Chef Automate
directly from Chef
● Provides full Chef Automate
● Customer needs to manage
backup and upgrades
● Customer is billed by Chef or
Chef Reseller
● Support is provided by Chef

15. Chef & Gannett
• Chef helped Gannett implement
a DevOps evolution
• Changed the culture, processes,
and tools of a media juggernaut
• Broke down barriers between
development and operations
“We had too much
bureaucracy, too
many handoffs, too
many tickets. We
were depending on
people who weren’t a
part of what we were
trying to accomplish.
—John Dietz, Platform
Architect, Gannett
“

16. Transformation at Gannett
Ron Lipke • Senior DevOps Engineer, Gannett

17.  National and local newspaper/media company
 National brand is USATODAY
 Network comprised of 108 media companies in 33 states
 In the Top 10 U.S. news and information category
 Content delivered to 110 million unique visitors monthly
 U.S. newspapers add an additional audience of 9 million
readers every weekday

18. Chef Pipeline Tools at Gannett
 Chef Server – all users share one org
 Private Supermarket – CI keeps supermarket in sync with chef-server
 Jenkins CI Server – the only way to publish cookbooks at Gannett
 Artifactory – mirrored repos, gems and application binaries
 Amazon EC2 AMIs – CI testing and production
 Vagrant Box – local testing
 Packer/Atlas – for creating and storing images
 Scalr – Cloud Management provider with governance and RBAC

19. Gannett Chef Workflow
Cookbook Pipeline
Create feature
branch/repo in Github
tied to Jira ticket
Develop locally using
kitchen-vagrant
Push branch to Github
and create pull request
to master
Jenkins kicks off
testing for all PRs
Jenkins run same tests
on changes to master
Publish to internal
supermarket
Publish to chef-server
(Congrats, your cookbook
is in production!)
Peer review of successful
test and merge
1 2 3 4
5 6 7 8

20. What are we testing?
 Foodcritic – Chef linting with custom rules, we fail on everything
except FC005: Avoid repetition of resource declarations
 Rubocop – ruby linting, we exclude our test files and set max line
length 160, ignore hash rockets and enforce other style standards
 Chefspec – unit testing, target 100% coverage with accurate
context and platforms
 Serverspec – integration testing, expected end state and audit for
best practices

21. Advantages
 Ensure security compliance
 Front load common packages and config to speed up Chef runs on instance
launch
 Audit changes between image releases and Centos/Windows OS version
upgrades
 Consistent experience in testing and production encourages developer
adoption
Image Pipeline for Local and Amazon EC2 Testing

22. Image Pipeline for Local and Amazon EC2 Testing
Overview
 Base cookbook used on all images
 Role cookbooks for specific images (haproxy, database, application languages
(python, go, node) – accessed as preconfigured “roles” in Scalr)
 Built from minimal Centos
 Serverspec tests run on image creation and remote Serverspec runs on a
deployed EC2 instance via test environment in Scalr
 Images are then promoted to production and immediately available in CI
pipeline

23. Image Pipeline Workflow
Github repo with
packer scripts
and config
Jenkins kicks off
Packer builds
from ISO on repo
changes
Packer runs chef-
zero to configure
image
Packer import
image to Amazon
EC2
Use the Scalr API
to publish images
Create instances
in Scalr with the
new images
Validate existing
cookbooks can
converge on the
new image
Test with remote
serverspec from
Jenkins and
promote images
on success
chef-client provisioner - Packer template
1 2 3 4 5 6 7 8

24. AWS OpsWorks for
Chef Automate
Sean Carolan • Partner Architect, Chef

25. The Chef Automate Platform
Continuous Automation for High Velocity IT
Workflow • Local development • Integration • Tooling (APIs & SDKs)
COLLABORATE
▪ Package
▪ Test
▪ Approve
BUILD
▪ Provision
▪ Configure
▪ Execute
▪ Update
DEPLOY
▪ Secure
▪ Comply
▪ Audit
▪ Measure
▪ Log
MANAGE
Infrastructure Automation Compliance AutomationApplication Automation
AUTOMATION ENGINES

26. Benefits of Chef Automate (Revisited)
Decreased Risk
 Define compliance rules as code
 Deliver continuous compliance as
part of standard workflow
Increased Speed
 Package infrastructure and app
configuration as code
 Continuously automate
infrastructure and app updates
Improved Efficiency
 Define and execute standard
workflows and automation
 Audit and measure effectiveness
of automation

27. Choose AWS OpsWorks for Chef Automate
“Most enterprises
are going to
operate in hybrid
mode for many
years to come.
—Andy Jassy, CEO, Amazon
Web Services (re:Invent 2016)
“
● Full-fidelity Chef experience
● Scaling made easy
● Chef as a managed service
● AWS native service
● Manage hybrid environments
● Easily access Chef’s commercial features

28. Chef & AWS: Partnering for your success
”
AWS minimizes infrastructure effort while Chef delivers a scalable
automation platform built for DevOps workflows
- Ken Cheney, CMO, Chef
● Build on your existing relationship with AWS
● AWS OpsWorks for Chef Automate is an AWS product
● AWS provides front-line support for customers
● Chef Software Inc. provides level 3 support for AWS
● The power of Chef backed by the cloud provider you
know and trust

29. Autoscaling Made Easy
● Overcome challenges scaling Chef
managed nodes in AWS
● API endpoints to register/deregister nodes
● Alternative to custom boot logic
● Alternative to using knife-ec2
● Reference via AWS docs
http://docs.aws.amazon.com/opsworks-cm/latest/APIReference

30. Migrating to AWS OpsWorks for Chef
Automate
● Manage on-premises Chef servers
and Chef-managed nodes with AWS
OpsWorks for Chef Automate
● Migrate existing Chef code to AWS
OpsWorks
● OpsWorks Stacks users can expect
to see migration tooling soon

31. Pay-As-You-Go Pricing
● Pricing behaves like any native AWS service
● Utility-based pricing ($0.0155/node/hr)
● Discounts available for bulk usage
● Chef appears as a line-item on your AWS bill

32. Register today at chefconf.chef.io | Save 10% by using “AWSOpsWorks” as the discount code

33. Register today at: aws.amazon.com/summits/san-francisco/

34. Q & A
For more information please visit:
https://www.chef.io/opsworks/
or
https://aws.amazon.com/opsworks/