Learn AWS application automation concepts, such as scripting and continuous integration (CI) and continuous deployment (CD).
- [Instructor] As we're getting started thinking about processes around application automation, here are some considerations. Automation is always preferred to manual service configuration. What does that mean? It's preferred to have a way of codifying or using code or scripts rather than clicking in the Amazon console. So you can automate with scripts from the CLI, tools and services such as the SDK, and we'll be looking at those in this course. We can automate AWS service configuration.
So for example, an EC2 instance configuration or a DynamoDB table configuration. Your source code pipeline should also be automated. We'll be understanding and working with sets of scripts and code that will enable you to continuously integrate and continuously deploy entire application solutions onto production AWS infrastructure. There will be different phases, commit, build, run tests and deploy, and all of these pipeline phases, although we'll use various types of tools, many of them GUI based that you can click in, will also generate code.
So they key takeaway from this is all code is an artifact that you want to work with. And to underscore this a core tenet of this course is that configuration is code. You want to prefer automation via, as I was saying, scripts, tools and codes to implement and verify and update all AWS service changes. As a general rule of thumb, in any sort of production environment you want to avoid clicking in the AWS console to make any service setups, changes, deletions, so on and so forth.
- Continuous delivery (CD) approaches
- Automation approaches
- Core services of AWS
- Core AWS tools
- Advanced CD
- Advanced automation
- Using third-party tools for CD and automation