AWS Management Tools Blog

Tag: AWS OpsWorks

Perform continuous cookbook integration testing and delivery for AWS OpsWorks for Chef Automate

Any Chef server should be a hub of tested and trusted cookbooks that can be added to node run lists easily. However, the testing and delivery of cookbooks to the server itself can be an arduous task. To simplify and expedite this necessary process, we’ve leveraged AWS technologies to create a pipeline that executes integration testing […]

Read More

How to set up AWS OpsWorks Stacks auto healing notifications in Amazon CloudWatch Events

In this post, we describe how to set up Amazon CloudWatch Events so that you are notified when AWS OpsWorks Stacks auto healing triggers stop and start events on an Amazon EC2 instance. Recently, AWS OpsWorks Stacks announced support for CloudWatch Events. You can now send state changes in OpsWorks Stacks, such as instance stopped […]

Read More

Updating chef-client on AWS OpsWorks for Chef Automate nodes

Throughout the life of your AWS OpsWorks for Chef Automate environments there will be numerous updates and changes to one of the most crucial components – the chef-client. How can you ensure that you have the most up-to-date version of chef-client running on your OpsWorks for Chef Automate infrastructure? Can you make these updates in […]

Read More

Distributing your AWS OpsWorks for Chef Automate infrastructure

Organizations that manage many nodes over larger geographical AWS Regions may wish to reduce latency and load between nodes in their AWS OpsWorks for Chef Automate implementation. By distributing nodes between multiple servers, organizations encounter the challenge of how to ensure that cookbooks and other configurations are consistently deployed across two or more Chef Servers […]

Read More

Using AWS OpsWorks for Chef Automate in a federated environment

Many large enterprises operate on a federated model. That is, they are separated into different business units or organizations, with different goals, procedures, and skill sets. These enterprises typically use a system to manage their infrastructure configuration and changes. You might ask, “Can we apply a federated model to configuration management? If so, what are […]

Read More

2017 Year in Review: AWS OpsWorks for Chef Automate and Puppet Enterprise

AWS OpsWorks for Chef Automate and AWS OpsWorks for Puppet Enterprise provide fully managed Chef and Puppet servers with a suite of automation tools for infrastructure and application management. Enterprise customers rely on OpsWorks for easy configuration management and secure maintenance as the service automatically patches, updates, and backs up servers. This blog post gives […]

Read More

AWS OpsWorks for Puppet Enterprise and an alternate implementation for policy based auto signing

AWS OpsWorks for Puppet Enterprise was released in November of 2017. It has a secure API (associate node) that provides a secure, convenient, and AWS-integrated method to sign certificates for clients of OpsWorks for Puppet Enterprise. This secure API is ideal for use within a user data script when being used for AWS CloudFormation (which […]

Read More

How to Manage Credentials in AWS OpsWorks for Puppet Enterprise using Hiera-eyaml

For customers new to configuration management with AWS OpsWorks for Puppet Enterprise (OWPE), a frequently-asked question is “How do I store sensitive data, such as database passwords, for use in my manifests?” Hiera allows you to manage and access data from various backends (data storage locations). By default, Hiera 5 supports YAML, JSON, and HOCON […]

Read More

AWS OpsWorks for Chef Automate Now Supports Compliance

AWS OpsWorks for Chef Automate gives you a fully managed Chef server with a suite of automation tools.  The release of Chef Automate version 1.6 includes the new Compliance view for Chef Automate UI. With AWS OpsWorks for Chef Automate integrated with compliance, you can track the compliance of your infrastructure based on a predefined policy. […]

Read More