By using Amazon S3 and AWS Lambda together, you can create a serverless architecture that provides highly scalable and available image resizing capabilities. Here's how the solution would work: Set up an Amazon S3 bucket to store the original images uploaded by users. Configure an event trigger on the S3 bucket to invoke an AWS Lambda function whenever a new image is uploaded. The Lambda function can be designed to retrieve the uploaded image, perform the necessary resizing operations based on device requirements, and store the resized images back in the S3 bucket or a different bucket designated for resized images. Configure the Amazon S3 bucket to make the resized images publicly accessible for serving to users.

image = static = S3 or cloudfront but image is unstructured data so you dont store it in a relational database like RDS and Step Function is not for processing So A

Scalability = S3, Lamda automatically resize images = Lambda

How can end user upload an image to S3 bucket with static hosting. I believe it should be dynamic website (Answer D)

This meets all the key requirements: S3 static website provides high availability and auto scaling to handle unpredictable traffic Lambda functions invoked from the S3 site can resize images on the fly Storing images in S3 buckets provides durability, scalability and high throughput Serverless approach with S3 and Lambda maximizes scalability and availability

OK. A is better, although I chose D originally. I guess it shouldn't be D simply because it overkills for this scenario and introduces higher operational overhead (even though option D can handle more complex workloads than Lambda if needed).

Is Static Website Read only ? Eventhough I have selected Answer as A