There is a certain correlation that can be made between the size of the change and the risk of introducing critical bugs in the product, as the following diagram demonstrates:
- Title Page
- Copyright
- Credits
- About the Author
- About the Reviewer
- www.PacktPub.com
- Customer Feedback
- Preface
- The Cloud and the DevOps Revolution
- Deploying Your First Web Application
- Treating Your Infrastructure As Code
- Managing your infrastructure with CloudFormation
- Adding a configuration management system
- Getting started with Ansible
- Installing Ansible on your computer
- Creating our Ansible playground
- Creating our Ansible repository
- Executing modules
- Running arbitrary commands
- Ansible playbooks
- Running Ansible in pull mode
- Installing Git and Ansible on our EC2 instance
- Integrating Ansible with CloudFormation
- Monitoring
- Summary
- Adding Continuous Integration and Continuous Deployment
- Building a continuous integration pipeline
- Building a continuous deployment pipeline
- Creating new web servers for continuous deployment
- Integrating our Hello World application with CodeDeploy
- Building our deployment pipeline with AWS CodePipeline
- Summary
- Scaling Your Infrastructure
- Running Containers in AWS
- Monitoring and Alerting
- Instrumenting our application for monitoring
- AWS CloudWatch
- Using CloudWatch to monitor our helloworld application
- Advanced logging infrastructure with ElasticSearch, Kibana, and Firehose
- Monitoring our infrastructure
- Creating alarms using CloudWatch and SNS
- Summary
- Instrumenting our application for monitoring
- Hardening the Security of Your AWS Environment
- Understanding where to focus your effort
- Improving the security of the IAM layer
- Strengthening the security at the network level
- Protecting against targeted attacks
- Summary
Too much code changing at once
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.