Configuration Management Flashcards
Why do you need configuration management?
how doe you apply changes to:
- installed applications
- configuration for application and services (https.conf,IIS configuration)
- Dozens or hundreds of ec2 instances
how do you make sure that various settings required for an instance remain in a known good state?
Infrastructure
requires ongoing management common components: - package updates - new software - new configurations - new application deployments - environment -specific changes
Ongoing management
requires proper tooling
common challenges:
Best practices
ensure solution covers all infrastructure components
Inventory and Control
make inventory o
AWS Config
is like a continuous configuration auditor
AWS Config
is like a continuous configuration auditor
- assess, audit, and evaluate the
AWS Config use cases
not on by default - discover resources - change management and realization of impacts b/w resources - continous audit and compliance - compliance-as-code -
AWS Config Rules
Check whether a change made to a resource’s configuration meets your desired configuration standard
Aggregate compliance into a central account
Rules
- more than 170
Automatic remediation of noncompliant resources
can use Automation AWS service
Automation AWS service
??
Change orchestration
coordination and management of changes to AWS resources (creation, modification, and termination)
orchestration tools:
AWS CloudFormation
AWS Service Catalog - collection of CloudFormation templates
AWS Systems Manager
AWS Elastic Beanstalk
AWS OpsWorks
3rd party tools (HashiCorp Terraform and more)
OS and application stack management
managed services available to assist with installation and ongoing management
tools:
- AWS Elastic Beanstalk
- AWS OpsWorks
AWS OpsWorks
configuration management tool that provides managed instances of Chef and Puppet
AWS OpsWorks Stacks
Stack:
Layer:
Instances:
App:
only Chef