#Cis benchmark for aws eks series

When it comes to infrastructure security, AWS will assume additional responsibilities as you move from self-managed workers, to managed node groups, to Fargate. IAM, pod security, runtime security, network security, and so forth. As a consumer of EKS, you are largely responsible for the topics in this guide, e.g.

This includes the Kubernetes control plane nodes, the ETCD database, and other infrastructure necessary for AWS to deliver a secure and reliable service.

With EKS, AWS is responsible for managing of the EKS managed Kubernetes control plane. Generally speaking, AWS is responsible for security 'of' the cloud whereas you, the customer, are responsible for security 'in' the cloud. Security and compliance are considered shared responsibilities when using a managed service like EKS. Understanding the Shared Responsibility Model ¶ The topics do not need to be read in a particular order. Each topic starts with a brief overview, followed by a list of recommendations and best practices for securing your EKS clusters. The guide is organized into different topic areas for easier consumption. This guide is meant for security practitioners who are responsible for implementing and monitoring the effectiveness of security controls for EKS clusters and the workloads they support. Guides for Performance, Operational Excellence, Cost Optimization, and Reliability will be available in the coming months.

#Cis benchmark for aws eks series

The guidance herein is part of a series of best practices guides that AWS is publishing to help customers implement EKS in accordance with best practices.

This guide provides advice about protecting information, systems, and assets that are reliant on EKS while delivering business value through risk assessments and mitigation strategies. Monitoring for Network performance issuesĪmazon EKS Best Practices Guide for Security ¶ Understanding the Shared Responsibility Model