How can the design requirements be met?

By:
In: SAP-C01
Tagged:
With: 1 Comment
A company wants to host its website on AWS using serverless architecture design patterns for global customers.The company has outlined its requirements as follow:✑ The website should be responsive.✑ The website should offer minimal latency.✑ The website should be highly available.✑ Users should be able to authenticate through social identity providers such as Google, Facebook, and Amazon.✑ There should be baseline DDoS protections for spikes in traffic.

How can the design requirements be met?

Use Amazon CloudFront with Amazon ECS for hosting the website. Use AWS Secrets Manager to provide user management and authentication functions. Use ECS Docker containers to build an API.

Use Amazon Route 53 latency routing with an Application Load Balancer and AWS Fargate in different regions for hosting the website. Use Amazon Cognito to provide user management and authentication functions. Use Amazon EKS containers to build an API.

Use Amazon CloudFront with Amazon S3 for hosting static web resources. Use Amazon Cognito to provide user management and authentication functions. Use Amazon API Gateway with AWS Lambda to build an API.

Use AWS Direct Connect with Amazon CloudFront and Amazon S3 for hosting static web resources. Use Amazon Cognito to provide user management authentication functions. Use AWS Lambda to build an API.

Explanations:

Amazon ECS is not serverless; it requires management of containers. Additionally, AWS Secrets Manager is not specifically designed for user authentication through social identity providers, which is better handled by Amazon Cognito.

While this option uses latency routing and provides high availability, it relies on AWS Fargate and EKS, which are not fully serverless solutions. Furthermore, Amazon Cognito is appropriate for user authentication, but the use of an Application Load Balancer adds complexity.

This option effectively uses Amazon CloudFront for content delivery, Amazon S3 for static hosting, Amazon Cognito for user management and authentication (including social identity providers), and AWS Lambda with API Gateway for a fully serverless architecture, meeting all design requirements with minimal latency and high availability.

AWS Direct Connect is not necessary for hosting static resources and does not directly address user authentication or traffic spikes. Although it includes Amazon CloudFront and S3, the reliance on Direct Connect complicates the architecture without providing benefits relevant to serverless design patterns.

2025-10-03

1 Comment

  1. Alexis
    Author

    I weigh that the answer is:
    Use Amazon CloudFront with Amazon S3 for hosting static web resources. Use Amazon Cognito to provide user management and authentication functions. Use Amazon API Gateway with AWS Lambda to build an API.

Leave a Reply

Your email address will not be published. Required fields are marked *

8 − three =