Question #1008
A company operates an event registration application on Amazon Elastic Container Service (Amazon ECS) with Amazon CloudFront as the origin. Users with a valid encrypted JSON Web Token (JWT) can access the registration interface, while others are redirected to a waiting room. During peak traffic, the waiting room's load is causing availability issues for the registration system, impacting transaction reliability.
Which solution will MOST improve the reliability of registration transactions during high load?
Create a separate ECS service for the waiting room with independent scaling. Configure the registration service to inspect JWTs and redirect users to the waiting room when necessary.
Migrate the application to Amazon Elastic Kubernetes Service (Amazon EKS). Split the waiting room into a separate pod and deploy the registration service as a StatefulSet. Configure the registration pod to forward requests to the waiting room pod based on JWT validation.
Create a separate ECS service for the waiting room with independent scaling. Implement a CloudFront function to inspect the JWT and route requests directly to the registration service or waiting room service.
Use Amazon API Gateway with a JWT authorizer to validate tokens and route requests to the appropriate ECS service. Deploy separate services for registration and the waiting room with independent scaling configurations.
Explanation
Option C is correct because:
1. CloudFront Functions: Handle JWT validation and routing at the edge, reducing backend load and latency.
2. Independent Scaling: Separating the waiting room and registration into distinct ECS services allows each to scale based on its own demand, preventing resource contention.
3. Efficiency: Direct routing at the edge ensures only valid requests reach the registration service, minimizing unnecessary processing.
Other options are less optimal:
- A: Relies on the registration service for redirection, adding load during peaks.
- B: Migrating to EKS is unnecessary and complicates the architecture.
- D: API Gateway adds latency/cost and requires rearchitecting, whereas CloudFront is already in use.
Key Points: Use edge-based routing (CloudFront) for validation/scaling separation to ensure reliability under high load.
Answer
The correct answer is: C