A gaming company hosts its dedicated multiplayer session servers on Amazon EC2. While player traffic fluctuates, the company requires a constant baseline of 50 EC2 instances 24/7 to maintain minimum coverage. Additionally, the company runs a continuous background analytics pipeline on Amazon ECS using AWS Fargate that requires a stable allocation of 20 vCPUs and 80 GB of RAM. The backend database runs on Amazon RDS for PostgreSQL 24/7. Which combination of purchasing options will provide the most cost-effective solution for this architecture?
- Purchase a Compute Savings Plan to cover the baseline EC2 instances and AWS Fargate tasks, and purchase Amazon RDS Reserved Instances for the PostgreSQL database.Cevap
- BPurchase a Compute Savings Plan to cover the baseline EC2 instances, AWS Fargate tasks, and the Amazon RDS PostgreSQL database.
- CMigrate the continuous background analytics pipeline to AWS Lambda to run continuously, and purchase a Compute Savings Plan to cover the baseline EC2 instances, the Lambda execution, and the database.
- DPurchase EC2 Instance Savings Plans to cover both the baseline EC2 instances and AWS Fargate tasks, and purchase Amazon RDS Reserved Instances for the database.
Cevap
Purchase a Compute Savings Plan to cover the baseline EC2 instances and AWS Fargate tasks, and purchase Amazon RDS Reserved Instances for the PostgreSQL database.
The correct option is the strategy of purchasing a Compute Savings Plan to cover both the baseline EC2 instances and AWS Fargate tasks, combined with Amazon RDS Reserved Instances for the PostgreSQL database. Compute Savings Plans provide the flexibility to apply discounts across both EC2 and AWS Fargate compute types under a single commitment, while RDS Reserved Instances are the correct vehicle to discount the continuous database compute usage.
Adım Adım Çözüm
Anahtar Kavram
Compute Savings Plans cover EC2, Fargate, and Lambda usage, whereas Amazon RDS requires RDS Reserved Instances for reservation discounts.
Tahmini Süre:2m 0s