Unboxing S3 Object Lambda

Michael Wittig – 05 May 2021

Amazon S3 Object Lambda offers a way to execute a Lambda function when someone wants to download a file (GetObject) from an S3 bucket. You can implement whatever logic you wish and return any data as the response via the WriteGetObjectResponse API. Keep in mind that the Lambda function must finish within 60 seconds and is called synchronously.

Unboxing S3 Object Lambda

Our unboxing series gives a first insight into new services or features. An unboxing is not as detailed as a service review.

How S3 Object Lambda works

The following figure shows the needed components:

S3 Object Lambda

S3 Security Guide

Protect your S3 buckets!

Follow four simple rules to avoid data leaking from S3. Download our S3 Security Guide!

Let’s look at the parts more closely:

  • S3 Object Lamda Access Point: References your Lambda function and your S3 Access Point. Block Public Access is always enabled.
  • Lambda function: Invoked when a GetObject request is made to the S3 Object Lambda Access Point.
  • S3 Access Point: Takes care of the non GetObject requests (such as ListObjects) and serves the pre-signed URL of the original file passed into the Lambda function.
  • S3 Bucket: Stores the original file (in fact, the original file could be non-existent).

In the following video, I go into more details and share code with you:

  • Introducing S3 Object Lambda
  • Use Cases
  • Demo: Generating content
  • Understanding Pricing
  • Pitfall: Keep the Lambda function running

Pricing

You pay for the following:

  • S3 Get Object API (as usual)
  • Lambda invocation
  • Lambda GB-second
  • $0.005 per GB returned via WriteGetObjectResponse

Source Code

---
AWSTemplateFormatVersion: '2010-09-09'
Description: 'S3 Object Lambda Demo'
Resources:
Bucket:
Type: 'AWS::S3::Bucket'
Properties: {}
FunctionLogGroup:
Type: 'AWS::Logs::LogGroup'
Properties:
LogGroupName: !Sub '/aws/lambda/${Function}'
RetentionInDays: 14
FunctionRole:
Type: 'AWS::IAM::Role'
Properties:
AssumeRolePolicyDocument:
Version: '2012-10-17'
Statement:
- Effect: Allow
Principal:
Service: 'lambda.amazonaws.com'
Action: 'sts:AssumeRole'
Policies:
- PolicyName: 's3-object-lambda'
PolicyDocument:
Statement:
- Effect: Allow
Action: 's3-object-lambda:WriteGetObjectResponse'
Resource: '*'
FunctionPolicy:
Type: 'AWS::IAM::Policy'
Properties:
Roles:
- !Ref FunctionRole
PolicyName: lambda
PolicyDocument:
Statement:
- Effect: Allow
Action:
- 'logs:CreateLogStream'
- 'logs:PutLogEvents'
Resource: !GetAtt 'FunctionLogGroup.Arn'
Function:
Type: 'AWS::Lambda::Function'
Properties:
Code:
ZipFile: |
const AWS = require('aws-sdk');
const s3 = new AWS.S3({apiVersion: '2006-03-01'});
exports.handler = async (event) => {
console.log(JSON.stringify(event));
await s3.writeGetObjectResponse({
RequestRoute: event.getObjectContext.outputRoute,
RequestToken: event.getObjectContext.outputToken,
Body: 'hello'
}).promise()
return {};
};
Handler: 'index.handler'
MemorySize: 128
Role: !GetAtt 'FunctionRole.Arn'
Runtime: 'nodejs12.x'
Timeout: 60
AccessPoint:
Type: 'AWS::S3::AccessPoint'
Properties:
Bucket: !Ref Bucket
LambdaAccessPoint:
Type: 'AWS::S3ObjectLambda::AccessPoint'
Properties:
Name: !Ref 'AWS::StackName'
ObjectLambdaConfiguration:
SupportingAccessPoint: !Sub 'arn:${AWS::Partition}:s3:${AWS::Region}:${AWS::AccountId}:accesspoint/${AccessPoint}'
TransformationConfigurations:
- Actions:
- GetObject
ContentTransformation:
AwsLambda:
FunctionArn: !GetAtt 'Function.Arn'
Outputs:
BucketName:
Value: !Ref Bucket
LambdaAccessPointArn:
Value: !GetAtt 'LambdaAccessPoint.Arn'

To invoke the S3 Object Lambda Access Point, run with your ARN: aws s3api get-object --bucket arn:aws:s3-object-lambda:us-east-1:123456789123:accesspoint/s3-object-lambda --key file.txt outfile.txt

Michael Wittig

Michael Wittig

I launched cloudonaut.io in 2015 with my brother Andreas. Since then, we have published hundreds of articles, podcast episodes, and videos. It’s all free and means a lot of work in our spare time. We enjoy sharing our AWS knowledge with you.
Have you learned something new by reading, listening, or watching our content? If so, we kindly ask you to support us in producing high-quality & independent AWS content. We look forward to sharing our AWS knowledge with you.

Support us

Feedback? Questions? You can reach me via Email, Twitter, or LinkedIn.