A logistics company operates a central distribution dashboard that consists of a fleet of Amazon ECS tasks running on AWS Fargate to handle constant, predictable API requests throughout the day. The backend stores shipment records in an Amazon RDS for PostgreSQL database instance that also runs continuously. The company wants to minimize compute costs for these resources without modifying the application code or architecture. Which combination of purchasing strategies should a solutions architect recommend to meet these requirements? (Select TWO.)
- Purchase a Compute Savings Plan to cover the AWS Fargate tasksCevap
- Purchase Amazon RDS Reserved Instances for the PostgreSQL databaseCevap
- CPurchase a Compute Savings Plan to cover the Amazon RDS database instance usage
- DMigrate the database to Amazon DynamoDB using Provisioned Capacity Mode to manage unpredictable query traffic
- EMigrate the API processing components to AWS Lambda to handle the constant, 24/7 requests
Cevap
Purchase a Compute Savings Plan to cover the AWS Fargate tasks, and purchase Amazon RDS Reserved Instances for the PostgreSQL database.
Purchasing a Compute Savings Plan provides significant savings for AWS Fargate compute usage, which fits the predictable API traffic profile. Purchasing Amazon RDS Reserved Instances provides a discounted hourly rate for the database instance, which runs continuously 24/7. Together, these strategies minimize compute costs for both components without requiring application modifications.
Adım Adım Çözüm
Anahtar Kavram
Matching appropriate AWS purchasing models (Compute Savings Plans, RDS Reserved Instances) to specific compute and database workloads to maximize cost savings.