Which solution will meet these requirements with the LEAST operational overhead?
Create an Amazon Simple Queue Service (Amazon SQS) queue. Integrate the queue with an Amazon EventBridge rule to receive payment notifications from mobile devices. Configure the rule to validate payment notifications and send the notifications to the backend application. Deploy the backend application on Amazon Elastic Kubernetes Service (Amazon EKS) Anywhere. Create a standalone cluster.
Create an Amazon API Gateway API. Integrate the API with an AWS Step Functions state machine to receive payment notifications from mobile devices. Invoke the state machine to validate payment notifications and send the notifications to the backend application. Deploy the backend application on Amazon Elastic Kubernetes Service (Amazon EKS). Configure an EKS cluster with self-managed nodes.
Create an Amazon Simple Queue Service (Amazon SQS) queue. Integrate the queue with an Amazon EventBridge rule to receive payment notifications from mobile devices. Configure the rule to validate payment notifications and send the notifications to the backend application. Deploy the backend application on Amazon EC2 Spot Instances. Configure a Spot Fleet with a default allocation strategy.
Create an Amazon API Gateway API. Integrate the API with AWS Lambda to receive payment notifications from mobile devices. Invoke a Lambda function to validate payment notifications and send the notifications to the backend application. Deploy the backend application on Amazon Elastic Container Service (Amazon ECS). Configure Amazon ECS with an AWS Fargate launch type.
Explanations:
This option uses Amazon Elastic Kubernetes Service (EKS) which requires management of the cluster and nodes. EKS Anywhere also adds complexity and operational overhead, making it less suitable for the requirement of minimizing operational overhead.
While using API Gateway and Step Functions could work for validation, deploying the backend application on self-managed EKS nodes still requires significant management and operational overhead, contrary to the requirement of reducing management burden.
Although this option uses Amazon SQS and EventBridge to handle payment notifications, deploying the backend application on EC2 Spot Instances necessitates management of the EC2 infrastructure and does not provide the lowest operational overhead.
This option leverages API Gateway and AWS Lambda, allowing for a serverless architecture with automatic scaling and minimal management overhead. The backend application is deployed on Amazon ECS using Fargate, which abstracts the infrastructure management completely, aligning with the requirement for low operational overhead.
As I recall, the answer is:
Create an Amazon API Gateway API. Integrate the API with AWS Lambda to receive payment notifications from mobile devices. Invoke a Lambda function to validate payment notifications and send the notifications to the backend application. Deploy the backend application on Amazon Elastic Container Service (Amazon ECS). Configure Amazon ECS with an AWS Fargate launch type.