A financial services company runs a batch processing pipeline on Amazon EC2 instances in an Auto Scaling group. The EC2 instances process raw data and write intermediate transaction metadata to an Amazon RDS for PostgreSQL DB instance configured in a Multi-AZ deployment. The final reports are saved to an Amazon S3 bucket.
During peak processing periods, the database performance degrades significantly. CloudWatch metrics indicate a write latency () of over on the RDS DB instance, while CPU utilization remains below . The DB instance uses General Purpose SSD (gp3) storage with default configurations.
Additionally, during sudden traffic spikes, the EC2 instances struggle to scale out quickly enough to prevent processing queues from backing up. The custom AMI used by the Auto Scaling group takes approximately to bootstrap and start application services. The Auto Scaling group uses a target tracking scaling policy based on CPU utilization with a default cooldown period of .
Which two actions should a Solutions Architect take to resolve these performance bottlenecks?
- Modify the RDS PostgreSQL DB instance storage type to Provisioned IOPS SSD (io2) to increase the available IOPS and throughput capacity.Cevap
- Configure an Auto Scaling warm pool for the EC2 Auto Scaling group to keep pre-warmed instances in a Stopped state, and increase the default cooldown period to .Cevap
- CEnable read-replica auto-scaling on the Multi-AZ secondary standby instance to offload heavy write transactions to the secondary Availability Zone.
- DRequest AWS Support to pre-warm the Application Load Balancer (ALB) to handle the incoming transaction load and bypass the EC2 instance boot time.
- EDecrease the Auto Scaling group cooldown period to to allow the scaling policy to trigger consecutive scaling activities more rapidly during spikes.