A company is designing a batch processing solution on AWS that runs containerized simulation jobs on a daily schedule for 4 hours. The jobs are stateless, fault-tolerant, and designed to checkpoint their progress so they can resume if interrupted. The simulation results must be stored in an Amazon RDS database, while the raw input data is temporarily stored in Amazon S3 for 10 days before being deleted. Which strategy is the most cost-effective to meet these requirements?
- Deploy the simulation jobs on Amazon ECS using Amazon EC2 Spot Instances, and store the raw input data in Amazon S3 Standard.Cevap
- BDeploy the simulation jobs on AWS Lambda functions to eliminate idle compute costs, and store the raw input data in Amazon S3 Standard.
- CDeploy the simulation jobs on Amazon ECS using AWS Fargate, purchase a Compute Savings Plan to cover both the Fargate tasks and the Amazon RDS database, and store the raw input data in Amazon S3 Standard.
- DDeploy the simulation jobs on Amazon ECS using Amazon EC2 Spot Instances, and store the raw input data in Amazon S3 Standard-Infrequent Access (S3 Standard-IA).
Cevap
Deploy the simulation jobs on Amazon ECS using Amazon EC2 Spot Instances, and store the raw input data in Amazon S3 Standard.
Deploying the simulation jobs on Amazon ECS using Amazon EC2 Spot Instances is the most cost-effective compute strategy because Spot Instances offer up to a 90% discount and are designed for stateless, checkpoint-enabled workloads. Additionally, storing raw data in Amazon S3 Standard is correct because it has no minimum storage duration charge, making it cheaper than S3 Standard-IA for data deleted after 10 days.
Adım Adım Çözüm
Anahtar Kavram
Selecting cost-optimized compute purchasing models and storage classes based on workload duration, fault tolerance, and data retention policies.