Hello and welcome to this lecture, where we shall briefly summarize what we have covered.

By now, you should understand that there are clear differences between AWS container services and Abstract services. These two classifications fall under two different shared responsibility models that offer various levels of AWS and customer management roles. It's important to understand which model your service falls under, whether that be infrastructure, container or Abstract, as this dictates how much of a responsibility you have to manage and architect the correct level of security for your environment.

As a general rule, when using container based services you will have more control and operational management of the service then those of Abstract services. You'll also have greater manipulation as to where the container service physically resides, such as within the private or public subnet, enabling you to utilize network security controls. Whereas your Abstract services will be abstracted from this environment and will be accessed over a service endpoint instead, such as S3, SQS, Glacier and DynamoDB.

With these Abstract services, you'll not need to maintain the underlying network architecture, as this is a shared multi-tenancy infrastructure that AWS maintains where they enforce their own network security controls on their own managed AWS network.

Throughout both container and Abstract services, there are multiple ways, depending on the service, to apply security at numerous different levels. For example, ensuring security exists for data at rest, in transit, via access controls, at a network level, for data durability and reliability and many more. Much of this access can be implemented at a deep and granular level depending on the sensitivity required on the data you're using. Some of this may be dictated by security governance and controls that may be required in your environment.

So to reiterate some key points:

• Container services provide you with more control, operational management and security responsibility than that of Abstract services
• Abstract services are managed and maintained by AWS more so than that of any other service classification, container or infrastructure
• Roles and responsibilities for customer differ when implementing security controls between the two classifications
• Understand the services that your are using and ensure that you are implementing its own security features as an additional layer within your security policies
• Whenever necessary and possible implement encryption when data is at rest and in transit
• Use the network security features offered by the VPCs, such as NACLs, Security Groups, Route Tables, NATs, Bastion Hosts, to restrict traffic between your different network segments and to enhance the security around your container services
• Implement a structured and managed IAM process using groups and roles to manage permissions across your AWS infrastructure ensuring access for users is restricted to only what is necessary

If you have any feedback on this course, positive or negative, please do leave a comment on the course landing page. We do look at the comments in our list and your feedback is greatly appreciated.

So that brings us to the end of this lecture and the end of the course. I hope it has given you a better understanding of AWS, Abstract and container services and that you have found it useful. Thank you for your time and good luck with your continued learning of cloud computing. Thank you.