• It is a configuration management service
  • configure and operate applications in AWS by using
    • Chef
    • Puppet
  • AWS Impelementation of CHEF configuration management & automation system; allows to provision infra, but abstracts some details.
  • It is good choice amongst Cloudformation (has overhead of JSON and configurability) and Elastic Beanstalk (it has more power and customization)
  • There are 2 variants: AWS OpsWorks Stacks and AWS OpsWorks for Chef Automate.
  • OpsWorks Stacks Chef Automate can use Chef cookbooks
  • Puppet Enterprise configure Puppet Enterprise master server in AWS.

OpsWorks Structure

  • OpsWorks Stack – group of resources as per need
  • OpsWorks Layer – set of shared functionailty applied to a group of components
  • OpsWorks Instance – actaul units of compute; inherits some from stack/layer
  • OpsWorks Application – software application deployed into instances

OpsWorks Details

  • OpsWorks Agent –
    • For CHEF
    • responsible for machine configuration
    • also for machine reconfiguration as per recipes
  • OpsWorks Automation Engine – responsible for creating, deleting, updating EC2 instances and other services; handle load balancing, Auto
  • scaling, Auto healing, Lifecycle events
  • Recipes – enlists OpsWorks about end result to be
  • Cookbooks has recipes and related data to support it

OpsWorks for Puppet Enterprise

  • Can create AWS-managed Puppet master servers
  •  A Puppet master server can
    • manages nodes
    • stores facts about those nodes
    • serve as central repository for Puppet modules.
  • Puppet modules are Puppet code for infrastructure configuration, which are
    • Reusable
    • shareable units
  • For custom modules
    • Download community modules from Puppet Forge
    • Can also use Puppet Development Kit
  • manage module deployment with Puppet Code Manager.
  • Use Puppet to automate how nodes are
    • Configured
    • Deployed
    • Managed
  • Full-stack automation is provided which includes
    • software and operating system configurations
    • package installations
    • database setups
    • change management
    • policy enforcement
    • monitoring

OpsWorks for Chef Automate

  • Create AWS-managed Chef servers having Chef Automate premium features
  • Uses Chef DK
  • other Chef tooling can also be used
  • A Chef server is used to
    • manage nodes in AWS
    • stores information about those nodes
    • serve as central repository for Chef cookbooks
  • Cookbooks contain recipes executed by Chef Infra client agent on each node
  • Available Chef tools to manage nodes and cookbooks on a Chef server
    • knife
    • Test Kitchen
  • Chef Automate installs and manages
    • Chef Automate
    • Chef Infra
    • Chef InSpec
  • Can also use community-authored or custom Chef cookbooks

OpsWorks Stacks

  • A stack is groups of AWS resources like group of instances
  • OpsWorks Stacks, creates and manages stacks and applications.
  • Deploy and monitor applications in stacks.
  • Manage AWS resources in specialized groups called layers.
  • A layer is a set of EC2 instances serving a particular purpose like database, web hosting
  • Does not require or create Chef servers
  • Can be accessed globally
  • use to create and manage instances globally
  • Can integrate with IAM for resource access control
  • Stacks can
    • monitor instance health
    • provision new instances, if needed
    • makes use of Auto Healing and Auto Scaling.

Opsworks Events

  • Events can run manually using events stack run command functionality; When event occurs it runs set of recipes assigned to that event.
  • Every layer has event specific  recipes
  • Event of SETUP, after instance finished booting
  • Event of CONFIGURE happens when
    • instance enters or leaves online
    • associate or disassociate EIP
    • attach or detach LB to a layer
  • Event of DEPLOY if deploy command is executed
  • Event of UNDEPLOY happens when
    • Execute Undeploy command
    • delete an application

Event of SHUTDOWN – happens with instance shutdown, but before termination, for cleanup

Opsworks Events

  • Events can run manually using events stack run command functionality; When event occurs it runs set of recipes assigned to that event.
  • Every layer has event specific  recipes
  • Event of SETUP, after instance finished booting
  • Event of CONFIGURE happens when
    • instance enters or leaves online
    • associate or disassociate EIP
    • attach or detach LB to a layer
  • Event of DEPLOY if deploy command is executed
  • Event of UNDEPLOY happens when
    • Execute Undeploy command
    • delete an application

Event of SHUTDOWN – happens with instance shutdown, but before termination, for cleanup

Event of SHUTDOWN – happens with instance shutdown, but before termination, for cleanup

Menu