A company runs a website on Amazon EC2 instances. Users can upload images to an Amazon S3 bucket and publish the images to the website. The company wants to deploy a serverless image-processing…

Question

Options

• AConfigure an Amazon Simple Notification Service (Amazon SNS) topic to invoke the Lambda
• BConfigure an Amazon CloudWatch alarm to invoke the Lambda function when a user uploads a
• CConfigure S3 Event Notifications to invoke the Lambda function when a user uploads a new
• DConfigure an Amazon Simple Queue Service (Amazon SQS) queue to invoke the Lambda

• A
  14% (8)
• B
  3% (2)
• C
  78% (45)
• D
  5% (3)

Explanation

Use Amazon S3 Event Notifications with AWS Lambda to trigger image processing on object creation. S3 natively supports invoking Lambda for events such as s3:ObjectCreated:*, providing a serverless, low-latency pipeline without managing additional services. AWS operational guidance states that "Amazon S3 can directly invoke a Lambda function in response to object- created events," allowing you to pass event metadata (bucket/key) to the function for resizing and writing results back to S3. This approach minimizes operational overhead, scales automatically with upload volume, and integrates with standard retry semantics. SNS or SQS can be added for fan-out or buffering patterns, but they are not required when the requirement is simply "invoke the Lambda function on upload." CloudWatch alarms do not detect individual S3 object uploads and cannot directly satisfy per-object triggers. Therefore, configuring S3 Lambda event notifications meets the requirement most directly and aligns with CloudOps best practices for event-driven, serverless automation.

No community discussion yet for this question.