A containerized application runs on EC2 instances with public IPs. Apache Kafka is self-hosted on those EC2 instances, and PostgreSQL has been migrated to Amazon RDS for PostgreSQL. The company expects a surge in orders for a product release. Which architectural changes will reduce operational overhead and support the increased load?

The correct answer optimizes for reduced operational overhead and scalability. Amazon EKS with AWS Fargate eliminates the need to manage EC2 instances for Kubernetes, and autoscaling handles load spikes. Adding RDS read replicas offloads read traffic from the primary database. Replacing self-managed Kafka with Amazon MSK removes the operational burden of managing a Kafka cluster. Hosting static content in S3 with CloudFront improves performance and reduces load on the application servers. The other options have significant drawbacks. The first option keeps EC2 for the application, which still requires instance management, and doesn't fully address database scalability for writes or high availability. The second option also keeps EC2 for the application and while Multi-AZ improves availability, it doesn't scale reads. The third option introduces Kubernetes on EC2, which still requires EC2 management, and doesn't fully leverage serverless for the application layer.