ITGSS Certified DevOps Engineer Practice Test

What do ECS and EKS both support for managing security roles per resource?

1. Cluster

2. Task/container

3. Service

4. Pod

The correct answer is: Task/container

ECS (Elastic Container Service) and EKS (Elastic Kubernetes Service) both utilize tasks and containers to manage security roles effectively. In ECS, a task represents a set of containers that share resources and can be managed as a single unit, allowing for specific IAM roles to be assigned at the task level. This means that each ECS task can have its own set of permissions, enabling fine-grained access control based on the specific requirements of that task. Similarly, in EKS, the security context is often managed at the container level within pods. While the Kubernetes construct of Pods can encapsulate one or more containers, it's the individual containers within those pods that can have their security roles defined. Kubernetes leverages RBAC (Role-Based Access Control) to manage access controls, and service accounts can be assigned to pods that dictate the permissions of the containers within. Both ECS and EKS allow for secure and isolated execution environments by managing permissions at the task/container level, ensuring that each unit can operate with the appropriate security context without compromising other resources in the environment. This approach enhances security and compliance especially in cloud-native applications.