Which solution will meet these requirements MOST cost-effectively?
Host the dynamic contact form in Amazon Elastic Container Service (Amazon ECS). Set up Amazon Simple Email Service (Amazon SES) to connect to a third-party email provider.
Create an Amazon API Gateway endpoint that returns the contact form from an AWS Lambda function. Configure another Lambda function on the API Gateway to publish a message to an Amazon Simple Notification Service (Amazon SNS) topic.
Host the website by using AWS Amplify Hosting for static content and dynamic content. Use server-side scripting to build the contact form. Configure Amazon Simple Queue Service (Amazon SQS) to deliver the message to the company.
Migrate the website from Amazon S3 to Amazon EC2 instances that run Windows Server. Use Internet Information Services (IIS) for Windows Server to host the webpage. Use client-side scripting to build the contact form. Integrate the form with Amazon WorkMail.
Explanations:
Amazon ECS is unnecessary for the low traffic of fewer than 100 visits per month, making this solution more complex and costly. Additionally, using Amazon SES with a third-party email provider adds complexity without added benefits.
This solution uses API Gateway and AWS Lambda for the contact form, which is cost-effective for low-traffic sites. Publishing the message to an SNS topic enables sending an email notification easily and at a low cost.
AWS Amplify and Amazon SQS are not required for this use case. Amplify Hosting is typically used for more complex setups, and SQS is unnecessary for low volume messaging, increasing cost and complexity.
Migrating to EC2 and using Windows Server with IIS adds substantial costs and complexity. Client-side scripting is inadequate for secure form submission, and Amazon WorkMail integration does not add any particular advantage here.