Hello, and welcome to this final lecture, where I want to briefly summarize some of the key points that I'd covered throughout the previous lectures. 

I started off by providing an overview of what AWS CloudFormation is, and here we learned that AWS CloudFormation can provision your infrastructure resources via a text-based file. CloudFormation can perform these actions securely and across multiple regions and accounts. A CloudFormation template describes your resources that you need provisioned, along with their configurations. And CloudFormation will also work out the service dependency. 

Some of the benefits of CloudFormation include security, as it removes the factor of human error and reduces the chance of vulnerabilities. Infrastructure replication. AWS CloudFormation allows you to quickly and easily replicate your infrastructure within your AWS account. And through the use of templates, you can deploy your resources across multiple regions and accounts, making these templates the source of truth for your infrastructure. It's simply code. As the entire infrastructure is deployed via a scripted code, it makes it easy for other members of your team or outside of your team, to review and verify your code to ensure that it's correct before deployment. Notification and automation. As AWS CloudFormation integrates with SNS, it easily allows you to provide updates of the status of changes with your deployments. Sample Templates. These allow you to get you started quickly, with some common deployment options to save you having to create them yourself.

Now, following this lecture, I looked at some of the core components of AWS CloudFormation, which covered Stacks, Templates, Stack Sets, and Designer.

Stacks. A CloudFormation stack is a set of AWS resources that you can provision, update or delete all at the once. Resources within the stack are identified by associating a CloudFormation template.

Templates. Templates are comprised of JSON or YAML files, and are text files that describe your environment and resources to build within your account. The template is then used by a stack to assist in the deployment of resources.

Stack Sets. A stack set allows you to create, update or delete your stacks across a number of AWS accounts, in different regions, with a single template. Stack sets also use a component known as a stack instance, which references to another stack in a different AWS account, in a particular region.

Designer. The designer allows you to visually create your environment through a drag and drop interface, which allows CloudFormation to automatically create a template for you, based off of your design.

Finally, I provided a demonstration of how to create a CloudFormation stack, using an AWS sample template. 

That has now brought me to the end of this lecture, and to the end of this introductory course. You should now have a greater understanding of what AWS CloudFormation is, and what it's used for. To gain additional hands-on experience with AWS CloudFormation, I suggest you take a look at the following labs that we have: Deploying Wordpress using CloudFormation, and Hands-on CloudFormation for Deploy Scalability. 

If you have feedback on this course, positive or negative, please contact us by sending an email to support@cloudacademy.com. Your feedback is greatly appreciated. 

Thank you for your time, and good luck with your continued learning of cloud computing. Thank you.