Question

Difficulty: HardAWS Compute Services

A company is deploying a containerized network monitoring tool on AWS. The tool must capture network traffic by running in privileged mode to access raw network sockets on the host. The application runs continuously, and the company wants to use a managed container orchestration service to manage the containers while retaining the ability to configure the host operating system when necessary. Which AWS compute option best meets these requirements?

  1. Amazon Elastic Container Service (Amazon ECS) hosted on Amazon Elastic Compute Cloud (Amazon EC2)Answer
  2. B
    Amazon Elastic Container Service (Amazon ECS) hosted on AWS Fargate
  3. C
    AWS Lambda function package deployed as a container image
  4. D
    Amazon Lightsail container service

Answer

Amazon Elastic Container Service (Amazon ECS) hosted on Amazon Elastic Compute Cloud (Amazon EC2)
Amazon Elastic Container Service (Amazon ECS) hosted on Amazon Elastic Compute Cloud (Amazon EC2) is correct because it provides container orchestration while allowing full administrative root access to the underlying EC2 instances. This allows the customer to run containers in privileged mode and modify the host operating system settings to capture raw network traffic.

Step-by-Step Solution

1
Analyze the workload runtime and orchestration requirements
The application must run continuously as a container, requiring a service that supports long-running containerized tasks (eliminating serverless functions like AWS Lambda).
AWS Lambda has a 15-minute maximum execution timeout and is not suited for continuous monitoring tools.
2
Evaluate host access and privilege requirements
The containerized tool requires privileged mode to access raw network sockets and custom host configuration.
Serverless container options like AWS Fargate manage the host infrastructure and restrict access to the host OS, making privileged container execution impossible.
3
Select the correct compute deployment model
Amazon ECS on Amazon EC2 provides container management while keeping the underlying virtual servers (EC2 instances) visible and configurable by the customer.
This configuration satisfies both the container orchestration requirement and the need for administrative access to the underlying host operating system.

Key Concept

Distinguishing between serverless container hosting (AWS Fargate) and server-based container hosting (Amazon ECS on Amazon EC2) based on host-level control and privileged access requirements.
Estimated Time:2m 0s
Rate this question