{"id":1813,"date":"2019-11-13T18:04:03","date_gmt":"2019-11-13T05:04:03","guid":{"rendered":"http:\/\/www.helenanderson.co.nz\/?p=1813"},"modified":"2020-05-22T21:09:25","modified_gmt":"2020-05-22T09:09:25","slug":"aws-security","status":"publish","type":"post","link":"https:\/\/helenanderson.co.nz\/aws-security\/","title":{"rendered":"AWS security"},"content":{"rendered":"\n

Under the Shared Responsibility Model AWS is responsible for security ‘of the Cloud’<\/strong>, while the customer is responsible for what is ‘in the Cloud’<\/strong>.<\/p>\n\n\n\n

This means that while AWS take responsibility for the physical security of its data centres, database<\/a> patching, and firewall configuration, the customer needs to take responsibility for who has access to their content, access rights and authentication.<\/p>\n\n\n\n

This post will take you through the services that AWS offers and best practices they recommend to keep what’s in the Cloud safe and secure.<\/p>\n\n\n\n


\n\n\n\n

Identity Access Management<\/a>
VPC and GuardDuty<\/a>
S3 and Macie<\/a>
EC2 and Inspector<\/a>
RDS and Redshift<\/a>
CloudTrail and CloudWatch<\/a>
Useful Links<\/a><\/strong><\/p><\/blockquote>\n\n\n\n


\n\n\n\n

IAM<\/h2>\n\n\n\n

Identity and Access Management (IAM) helps you to securely control who has access to your resources and how they access them.<\/p>\n\n\n\n