Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Implementing DevOps on AWS

You're reading from   Implementing DevOps on AWS Engineering DevOps for modern businesses

Arrow left icon
Product type Paperback
Published in Jan 2017
Publisher Packt
ISBN-13 9781786460141
Length 258 pages
Edition 1st Edition
Tools
Concepts
Arrow right icon
Author (1):
Arrow left icon
Vaselin Kantsev Vaselin Kantsev
Author Profile Icon Vaselin Kantsev
Vaselin Kantsev
Arrow right icon
View More author details
Toc

Table of Contents (11) Chapters Close

Preface 1. What is DevOps and Should You Care? FREE CHAPTER 2. Start Treating Your Infrastructure as Code 3. Bringing Your Infrastructure Under Configuration Management 4. Build, Test, and Release Faster with Continuous Integration 5. Ever-Ready to Deploy Using Continuous Delivery 6. Continuous Deployment - A Fully Automated Workflow 7. Metrics, Log Collection, and Monitoring 8. Optimize for Scale and Cost 9. Secure Your AWS Environment 10. AWS Tips and Tricks

Chapter 3.  Bringing Your Infrastructure Under Configuration Management

As hinted at the end of the previous chapter, there is some more work to be done before we can claim to have fully implemented IaC.

The first step was to describe the hardware side of our infrastructure in code; now it is time to look at the software or configuration aspect of it.

Let us say we have provisioned a few EC2 nodes and would like to have certain packages installed on them, and relevant configuration files updated. Prior to Configuration Management (CM) tools gaining popularity, such tasks would have been performed manually by an engineer either following a checklist, running a collection of shell scripts, or both. As you can imagine, such methods do not scale well as they generally imply one engineer setting up one server at a time.

In addition, checklists or scripts:

  • Are hard to write when it comes to configuring a host plus a full application stack running on it
  • Are usually targeted at a given host...
lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime