AWS CloudFormation, Lambda, and S3 Trigger: A Comprehensive Guide

In the world of cloud computing, AWS offers a plethora of services that can be combined to create powerful and scalable applications. Two of these services, AWS Lambda and Amazon S3, are often used together to build event - driven architectures. AWS CloudFormation, on the other hand, simplifies the process of provisioning and managing AWS resources. In this blog post, we will explore how to use AWS CloudFormation to set up a Lambda function that is triggered by an event in an S3 bucket. This combination can be used for various use - cases such as data processing, image resizing, and more.

Table of Contents#

  1. Core Concepts
    • AWS CloudFormation
    • AWS Lambda
    • Amazon S3
    • S3 Trigger for Lambda
  2. Typical Usage Scenarios
  3. Common Practice
    • Prerequisites
    • Writing the CloudFormation Template
    • Deploying the Stack
  4. Best Practices
  5. Conclusion
  6. FAQ
  7. References

Article#

Core Concepts#

AWS CloudFormation#

AWS CloudFormation is an infrastructure - as - code service provided by Amazon Web Services. It allows you to define your AWS resources in a declarative JSON or YAML template. You can use CloudFormation to create, update, and delete entire stacks of AWS resources in a controlled and predictable manner. This makes it easier to manage the lifecycle of your infrastructure and ensures that your resources are consistently configured across different environments.

AWS Lambda#

AWS Lambda is a serverless computing service that lets you run your code without provisioning or managing servers. You simply upload your code, and Lambda takes care of all the underlying infrastructure management, including scaling, high availability, and security. Lambda functions can be triggered by various events, such as changes in an S3 bucket, incoming API requests, or scheduled events.

Amazon S3#

Amazon Simple Storage Service (S3) is an object storage service that offers industry - leading scalability, data availability, security, and performance. You can use S3 to store and retrieve any amount of data at any time, from anywhere on the web. S3 buckets are used to organize objects, and each object can have a unique key.

S3 Trigger for Lambda#

An S3 trigger for Lambda allows you to automatically invoke a Lambda function when a specific event occurs in an S3 bucket. For example, you can configure an S3 trigger to invoke a Lambda function when an object is created, deleted, or modified in a bucket. This event - driven architecture enables you to perform actions such as data processing, content moderation, or backup operations in real - time.

Typical Usage Scenarios#

  • Data Processing: When new data is uploaded to an S3 bucket, you can trigger a Lambda function to process the data, such as converting it to a different format, aggregating it, or performing analytics on it.
  • Image Resizing: If your application stores images in an S3 bucket, you can use an S3 trigger to invoke a Lambda function that resizes the images to different dimensions for various use - cases, such as thumbnails or different device sizes.
  • Content Moderation: Whenever a new object is uploaded to an S3 bucket, a Lambda function can be triggered to scan the content for inappropriate material.

Common Practice#

Prerequisites#

  • An AWS account.
  • Basic knowledge of AWS Lambda, Amazon S3, and AWS CloudFormation.
  • AWS CLI installed and configured on your local machine.

Writing the CloudFormation Template#

Here is an example of a CloudFormation template in YAML format to create an S3 bucket, a Lambda function, and configure an S3 trigger for the Lambda function:

Resources:
  MyS3Bucket:
    Type: 'AWS::S3::Bucket'
    Properties:
      BucketName: my - example - bucket
 
  MyLambdaExecutionRole:
    Type: 'AWS::IAM::Role'
    Properties:
      AssumeRolePolicyDocument:
        Version: '2012 - 10 - 17'
        Statement:
          - Effect: Allow
            Principal:
              Service:
                - lambda.amazonaws.com
            Action:
              - 'sts:AssumeRole'
      Policies:
        - PolicyName: LambdaExecutionPolicy
          PolicyDocument:
            Version: '2012 - 10 - 17'
            Statement:
              - Effect: Allow
                Action:
                  - 'logs:CreateLogGroup'
                  - 'logs:CreateLogStream'
                  - 'logs:PutLogEvents'
                Resource: 'arn:aws:logs:*:*:*'
              - Effect: Allow
                Action:
                  - 's3:GetObject'
                Resource: !GetAtt MyS3Bucket.Arn
 
  MyLambdaFunction:
    Type: 'AWS::Lambda::Function'
    Properties:
      Code:
        ZipFile: |
          import json
          def lambda_handler(event, context):
            for record in event['Records']:
              bucket = record['s3']['bucket']['name']
              key = record['s3']['object']['key']
              print(f"New object created in {bucket}: {key}")
            return {
              'statusCode': 200,
              'body': json.dumps('Hello from Lambda!')
            }
      Handler: index.lambda_handler
      Role: !GetAtt MyLambdaExecutionRole.Arn
      Runtime: python3.8
 
  MyS3BucketNotification:
    Type: 'AWS::S3::BucketNotification'
    Properties:
      Bucket: !Ref MyS3Bucket
      NotificationConfiguration:
        LambdaConfigurations:
          - Event: 's3:ObjectCreated:*'
            Function: !GetAtt MyLambdaFunction.Arn
 
 
Outputs:
  LambdaFunctionArn:
    Value: !GetAtt MyLambdaFunction.Arn
    Description: The ARN of the Lambda function
  S3BucketName:
    Value: !Ref MyS3Bucket
    Description: The name of the S3 bucket

Deploying the Stack#

  1. Save the above template as template.yaml.
  2. Use the following AWS CLI command to create a new CloudFormation stack:
aws cloudformation create - stack --stack - name my - s3 - lambda - stack --template - body file://template.yaml --capabilities CAPABILITY_IAM
  1. You can monitor the stack creation progress in the AWS CloudFormation console. Once the stack is created successfully, any new object created in the S3 bucket will trigger the Lambda function.

Best Practices#

  • Error Handling: Implement proper error handling in your Lambda function. If the function fails to process an S3 event, it should log the error details and, if possible, retry the operation.
  • Permissions Management: Only grant the necessary permissions to your Lambda function. For example, if your function only needs to read objects from an S3 bucket, don't grant write permissions.
  • Testing: Test your Lambda function and S3 trigger in a staging environment before deploying to production. You can use tools like AWS SAM Local to test your Lambda functions locally.

Conclusion#

AWS CloudFormation, Lambda, and S3 triggers provide a powerful combination for building event - driven architectures. By using CloudFormation, you can easily manage the deployment and configuration of your S3 buckets, Lambda functions, and the associated triggers. This setup can be used for a wide range of use - cases, from data processing to content moderation. By following the best practices, you can ensure the reliability and security of your applications.

FAQ#

Q: Can I have multiple S3 triggers for a single Lambda function? A: Yes, you can configure multiple S3 buckets to trigger the same Lambda function. You can also configure different types of events (e.g., object creation and deletion) from the same or different buckets to trigger the function.

Q: How much does it cost to use AWS CloudFormation, Lambda, and S3? A: AWS CloudFormation is free to use. You are only charged for the underlying AWS resources (such as S3 storage and Lambda compute time) that are created and managed by CloudFormation. The cost of S3 and Lambda depends on your usage, such as the amount of data stored in S3 and the number of Lambda invocations.

Q: Can I use a Lambda function written in languages other than Python? A: Yes, AWS Lambda supports multiple programming languages, including Java, Node.js, C#, and Go. You can write your Lambda function in any of the supported languages and use CloudFormation to deploy it.

References#

2025-10