f a r g a t e Flashcards
What are Fargate Task Sizes?
In Fargate, you define task sizes based on CPU and memory configurations. These must follow predefined CPU-memory pairings (e.g., 0.25 vCPU and 0.5 GB memory, 1 vCPU and 2 GB memory, etc.).
How does logging work in Fargate?
Fargate supports AWS CloudWatch Logs integration, which allows you to aggregate logs from your containers and view them in CloudWatch Logs. You configure this in your task definition.
What is the task ENI (Elastic Network Interface) in Fargate?
Fargate supports Amazon Elastic File System (EFS) integration, which allows containers to access shared file storage. This is useful for stateful applications where data persistence across tasks is needed.
What is the pricing model for Fargate?
Fargate pricing is based on the CPU and memory resources allocated to your tasks. You pay for the time that tasks are running, and there are no upfront costs or EC2 instances to manage.
How does load balancing work in Fargate?
Fargate tasks can be integrated with an AWS Application Load Balancer (ALB) or Network Load Balancer (NLB). This distributes traffic evenly across running tasks and supports features like SSL termination and path-based routing.
What is Service Discovery in ECS with Fargate?
ECS Service Discovery automatically registers your services in Route 53 DNS when they start. This allows other services or external clients to easily discover and connect to your tasks using a DNS name.
How does Fargate ensure task isolation?
Each Fargate task runs in its own VM-like environment with dedicated CPU and memory. This provides security and resource isolation, preventing tasks from affecting each other’s performance.
How can you monitor and troubleshoot Fargate tasks?
You can monitor Fargate tasks using AWS CloudWatch (metrics and logs), AWS X-Ray (tracing), and ECS Console (task and service health). You can also use ECS events to track task lifecycle and issues.
