Tutorial: Transforming data for your application with S3 Object Lambda - Amazon Simple Storage Service

Tutorial: Transforming data for your application with S3 Object Lambda

When you store data in Amazon S3, you can easily share it for use by multiple applications. However, each application might have unique data format requirements, and might need modification or processing of your data for a specific use case. For example, a dataset created by an ecommerce application might include personally identifiable information (PII). When the same data is processed for analytics, this PII is not needed and should be redacted. However, if the same dataset is used for a marketing campaign, you might need to enrich the data with additional details, such as information from the customer loyalty database.

With S3 Object Lambda, you can add your own code to process data retrieved from S3 before returning it to an application. Specifically, you can configure an AWS Lambda function and attach it to an S3 Object Lambda Access Point. When an application sends standard S3 GET requests through the S3 Object Lambda Access Point, the specified Lambda function is invoked to process any data retrieved from an S3 bucket through the supporting S3 access point. Then, the S3 Object Lambda Access Point returns the transformed result back to the application. You can author and execute your own custom Lambda functions, tailoring the S3 Object Lambda data transformation to your specific use case, all with no changes required to your applications.

This is an S3 Object Lambda workflow diagram.
Objective

In this tutorial, you learn how to add custom code to standard S3 GET requests to modify the requested object retrieved from S3 so that the object suit the needs of the requesting client or application. Specifically, you learn how to transform all the text in the original object stored in S3 to uppercase through S3 Object Lambda.

Note

This tutorial uses Python code to transform the data, for examples using other AWS SDKs see Transform data for your application with S3 Object Lambda in the AWS SDK Code Examples Library.

Prerequisites

Before you start this tutorial, you must have an AWS account that you can sign in to as an AWS Identity and Access Management (IAM) user with correct permissions. You also must install Python version 3.8 or later.

Create an IAM user with permissions in your AWS account (console)

You can create an IAM user for the tutorial. To complete this tutorial, your IAM user must attach the following IAM policies to access relevant AWS resources and perform specific actions. For more information about how to create an IAM user, see Creating IAM users (console) in the IAM User Guide.

Your IAM user requires the following policies:

Note

For simplicity, this tutorial creates and uses an IAM user. After completing this tutorial, remember to Delete the IAM user. For production use, we recommend that you follow the Security best practices in IAM in the IAM User Guide. A best practice requires human users to use federation with an identity provider to access AWS with temporary credentials. Another best practice is to require workloads to use temporary credentials with IAM roles to access AWS. To learn about using AWS IAM Identity Center to create users with temporary credentials, see Getting started in the AWS IAM Identity Center User Guide.

This tutorial also uses full-access AWS managed policies. For production use, we recommend that you instead grant only the minimum permissions necessary for your use case, in accordance with security best practices.

Install Python 3.8 or later on your local machine

Use the following procedure to install Python 3.8 or later on your local machine. For more installation instructions, see the Downloading Python page in the Python Beginners Guide.

  1. Open your local terminal or shell and run the following command to determine whether Python is already installed, and if so, which version is installed.

    python --version
  2. If you don't have Python 3.8 or later, download the official installer of Python 3.8 or later that's suitable for your local machine.

  3. Run the installer by double-clicking the downloaded file, and follow the steps to complete the installation.

    For Windows users, choose Add Python 3.X to PATH in the installation wizard before choosing Install Now.

  4. Restart your terminal by closing and reopening it.

  5. Run the following command to verify that Python 3.8 or later is installed correctly.

    For macOS users, run this command:

    python3 --version

    For Windows users, run this command:

    python --version
  6. Run the following command to verify that the pip3 package manager is installed. If you see a pip version number and python 3.8 or later in the command response, that means the pip3 package manager is installed successfully.

    pip --version

Step 1: Create an S3 bucket

Create a bucket to store the original data that you plan to transform.

To create a bucket
  1. Sign in to the AWS Management Console and open the Amazon S3 console at https://console.aws.amazon.com/s3/.

  2. In the left navigation pane, choose Buckets.

  3. Choose Create bucket.

    The Create bucket page opens.

  4. For Bucket name, enter a name (for example, tutorial-bucket) for your bucket.

    For more information about naming buckets in Amazon S3, see General purpose bucket naming rules.

  5. For Region, choose the AWS Region where you want the bucket to reside.

    For more information about the bucket Region, see Buckets overview.

  6. For Block Public Access settings for this bucket, keep the default settings (Block all public access is enabled).

    We recommend that you keep all Block Public Access settings enabled unless you need to turn off one or more of them for your use case. For more information about blocking public access, see Blocking public access to your Amazon S3 storage.

  7. For the remaining settings, keep the defaults.

    (Optional) If you want to configure additional bucket settings for your specific use case, see Creating a bucket.

  8. Choose Create bucket.

Step 2: Upload a file to the S3 bucket

Upload a text file to the S3 bucket. This text file contains the original data that you will transform to uppercase later in this tutorial.

For example, you can upload a tutorial.txt file that contains the following text:

Amazon S3 Object Lambda Tutorial: You can add your own code to process data retrieved from S3 before returning it to an application.
To upload a file to a bucket
  1. Sign in to the AWS Management Console and open the Amazon S3 console at https://console.aws.amazon.com/s3/.

  2. In the left navigation pane, choose Buckets.

  3. In the Buckets list, choose the name of the bucket that you created in Step 1 (for example, tutorial-bucket) to upload your file to.

  4. On the Objects tab for your bucket, choose Upload.

  5. On the Upload page, under Files and folders, choose Add files.

  6. Choose a file to upload, and then choose Open. For example, you can upload the tutorial.txt file example mentioned earlier.

  7. Choose Upload.

Step 3: Create an S3 access point

To use an S3 Object Lambda Access Point to access and transform the original data, you must create an S3 access point and associate it with the S3 bucket that you created in Step 1. The access point must be in the same AWS Region as the objects that you want to transform.

Later in this tutorial, you'll use this access point as a supporting access point for your Object Lambda Access Point.

To create an access point
  1. Sign in to the AWS Management Console and open the Amazon S3 console at https://console.aws.amazon.com/s3/.

  2. In the left navigation pane, choose Access Points.

  3. On the Access Points page, choose Create access point.

  4. In the Access point name field, enter the name (for example, tutorial-access-point) for the access point.

    For more information about naming access points, see Rules for naming Amazon S3 access points.

  5. In the Bucket name field, enter the name of the bucket that you created in Step 1 (for example, tutorial-bucket). S3 attaches the access point to this bucket.

    (Optional) You can choose Browse S3 to browse and search the buckets in your account. If you choose Browse S3, choose the desired bucket, and then choose Choose path to populate the Bucket name field with that bucket's name.

  6. For Network origin, choose Internet.

    For more information about network origins for access points, see Creating access points restricted to a virtual private cloud.

  7. By default, all Block Public Access settings are turned on for your access point. We recommend that you keep Block all public access enabled.

    For more information, see Managing public access to access points.

  8. For all other access point settings, keep the default settings.

    (Optional) You can modify the access point settings to support your use case. For this tutorial, we recommend keeping the default settings.

    (Optional) If you need to manage access to your access point, you can specify an access point policy. For more information, see Access point policy examples.

  9. Choose Create access point.

Step 4: Create a Lambda function

To transform original data, create a Lambda function for use with your S3 Object Lambda Access Point.

Write Lambda function code and create a deployment package with a virtual environment

  1. On your local machine, create a folder with the folder name object-lambda for the virtual environment to use later in this tutorial.

  2. In the object-lambda folder, create a file with a Lambda function that changes all text in the original object to uppercase. For example, you can use the following function written in Python. Save this function in a file named transform.py.

    import boto3 import requests from botocore.config import Config # This function capitalizes all text in the original object def lambda_handler(event, context): object_context = event["getObjectContext"] # Get the presigned URL to fetch the requested original object # from S3 s3_url = object_context["inputS3Url"] # Extract the route and request token from the input context request_route = object_context["outputRoute"] request_token = object_context["outputToken"] # Get the original S3 object using the presigned URL response = requests.get(s3_url) original_object = response.content.decode("utf-8") # Transform all text in the original object to uppercase # You can replace it with your custom code based on your use case transformed_object = original_object.upper() # Write object back to S3 Object Lambda s3 = boto3.client('s3', config=Config(signature_version='s3v4')) # The WriteGetObjectResponse API sends the transformed data # back to S3 Object Lambda and then to the user s3.write_get_object_response( Body=transformed_object, RequestRoute=request_route, RequestToken=request_token) # Exit the Lambda function: return the status code return {'status_code': 200}
    Note

    The preceding example Lambda function loads the entire requested object into memory before transforming it and returning it to the client. Alternatively, you can stream the object from S3 to avoid loading the entire object into memory. This approach can be useful when working with large objects. For more information about streaming responses with Object Lambda Access Points, see the streaming examples in Working with GetObject requests in Lambda.

    When you're writing a Lambda function for use with an S3 Object Lambda Access Point, the function is based on the input event context that S3 Object Lambda provides to the Lambda function. The event context provides information about the request being made in the event passed from S3 Object Lambda to Lambda. It contains the parameters that you use to create the Lambda function.

    The fields used to create the preceding Lambda function are as follows:

    The field of getObjectContext means the input and output details for connections to Amazon S3 and S3 Object Lambda. It has the following fields:

    • inputS3Url – A presigned URL that the Lambda function can use to download the original object from the supporting access point. By using a presigned URL, the Lambda function doesn't need to have Amazon S3 read permissions to retrieve the original object and can only access the object processed by each invocation.

    • outputRoute – A routing token that is added to the S3 Object Lambda URL when the Lambda function calls WriteGetObjectResponse to send back the transformed object.

    • outputToken – A token used by S3 Object Lambda to match the WriteGetObjectResponse call with the original caller when sending back the transformed object.

    For more information about all the fields in the event context, see Event context format and usage and Writing Lambda functions for S3 Object Lambda Access Points.

  3. In your local terminal, enter the following command to install the virtualenv package:

    python -m pip install virtualenv
  4. In your local terminal, open the object-lambda folder that you created earlier, and then enter the following command to create and initialize a virtual environment called venv.

    python -m virtualenv venv
  5. To activate the virtual environment, enter the following command to execute the activate file from the environment's folder:

    For macOS users, run this command:

    source venv/bin/activate

    For Windows users, run this command:

    .\venv\Scripts\activate

    Now, your command prompt changes to show (venv), indicating that the virtual environment is active.

  6. To install the required libraries, run the following commands line by line in the venv virtual environment.

    These commands install updated versions of the dependencies of your lambda_handler Lambda function. These dependencies are the AWS SDK for Python (Boto3) and the requests module.

    pip3 install boto3
    pip3 install requests
  7. To deactivate the virtual environment, run the following command:

    deactivate
  8. To create a deployment package with the installed libraries as a .zip file named lambda.zip at the root of the object-lambda directory, run the following commands line by line in your local terminal.

    Tip

    The following commands might need to be adjusted to work in your particular environment. For example, a library might appear in site-packages or dist-packages, and the first folder might be lib or lib64. Also, the python folder might be named with a different Python version. To locate a specific package, use the pip show command.

    For macOS users, run these commands:

    cd venv/lib/python3.8/site-packages
    zip -r ../../../../lambda.zip .

    For Windows users, run these commands:

    cd .\venv\Lib\site-packages\
    powershell Compress-Archive * ../../../lambda.zip

    The last command saves the deployment package to the root of the object-lambda directory.

  9. Add the function code file transform.py to the root of your deployment package.

    For macOS users, run these commands:

    cd ../../../../
    zip -g lambda.zip transform.py

    For Windows users, run these commands:

    cd ..\..\..\
    powershell Compress-Archive -update transform.py lambda.zip

    After you complete this step, you should have the following directory structure:

    lambda.zip$ │ transform.py │ __pycache__ | boto3/ │ certifi/ │ pip/ │ requests/ ...

Create a Lambda function with an execution role (console)

  1. Sign in to the AWS Management Console and open the AWS Lambda console at https://console.aws.amazon.com/lambda/.

  2. In the left navigation pane, choose Functions.

  3. Choose Create function.

  4. Choose Author from scratch.

  5. Under Basic information, do the following:

    1. For Function name, enter tutorial-object-lambda-function.

    2. For Runtime, choose Python 3.8 or a later version.

  6. Expand the Change default execution role section. Under Execution role, choose Create a new role with basic Lambda permissions.

    In Step 5 later in this tutorial, you attach the AmazonS3ObjectLambdaExecutionRolePolicy to this Lambda function's execution role.

  7. Keep the remaining settings set to the defaults.

  8. Choose Create function.

Deploy your Lambda function code with .zip file archives and configure the Lambda function (console)

  1. In the AWS Lambda console at https://console.aws.amazon.com/lambda/, choose Functions in the left navigation pane.

  2. Choose the Lambda function that you created earlier (for example, tutorial-object-lambda-function).

  3. On the Lambda function's details page, choose the Code tab. In the Code Source section, choose Upload from and then .zip file.

  4. Choose Upload to select your local .zip file.

  5. Choose the lambda.zip file that you created earlier, and then choose Open.

  6. Choose Save.

  7. In the Runtime settings section, choose Edit.

  8. On the Edit runtime settings page, confirm that Runtime is set to Python 3.8 or a later version.

  9. To tell the Lambda runtime which handler method in your Lambda function code to invoke, enter transform.lambda_handler for Handler.

    When you configure a function in Python, the value of the handler setting is the file name and the name of the handler module, separated by a dot. For example, transform.lambda_handler calls the lambda_handler method defined in the transform.py file.

  10. Choose Save.

  11. (Optional) On your Lambda function's details page, choose the Configuration tab. In the left navigation pane, choose General configuration, then choose Edit. In the Timeout field, enter 1 min 0 sec. Keep the remaining settings set to the defaults, and choose Save.

    Timeout is the amount of time that Lambda allows a function to run for an invocation before stopping it. The default is 3 seconds. The maximum duration for a Lambda function used by S3 Object Lambda is 60 seconds. Pricing is based on the amount of memory configured and the amount of time that your code runs.

Step 5: Configure an IAM policy for your Lambda function's execution role

To enable your Lambda function to provide customized data and response headers to the GetObject caller, your Lambda function's execution role must have IAM permissions to call the WriteGetObjectResponse API.

To attach an IAM policy to your Lambda function role

  1. In the AWS Lambda console at https://console.aws.amazon.com/lambda/, choose Functions in the left navigation pane.

  2. Choose the function that you created in Step 4 (for example, tutorial-object-lambda-function).

  3. On your Lambda function's details page, choose the Configuration tab, and then choose Permissions in the left navigation pane.

  4. Under Execution role, choose the link of the Role name. The IAM console opens.

  5. On the IAM console's Summary page for your Lambda function's execution role, choose the Permissions tab. Then, from the Add Permissions menu, choose Attach policies.

  6. On the Attach Permissions page, enter AmazonS3ObjectLambdaExecutionRolePolicy in the search box to filter the list of policies. Select the check box next to the name of the AmazonS3ObjectLambdaExecutionRolePolicy policy.

  7. Choose Attach policies.

Step 6: Create an S3 Object Lambda Access Point

An S3 Object Lambda Access Point provides the flexibility to invoke a Lambda function directly from an S3 GET request so that the function can process data retrieved from an S3 access point. When creating and configuring an S3 Object Lambda Access Point, you must specify the Lambda function to invoke and provide the event context in JSON format as custom parameters for Lambda to use.

To create an S3 Object Lambda Access Point
  1. Sign in to the AWS Management Console and open the Amazon S3 console at https://console.aws.amazon.com/s3/.

  2. In the left navigation pane, choose Object Lambda Access Points.

  3. On the Object Lambda Access Points page, choose Create Object Lambda Access Point.

  4. For Object Lambda Access Point name, enter the name that you want to use for the Object Lambda Access Point (for example, tutorial-object-lambda-accesspoint).

  5. For Supporting Access Point, enter or browse to the standard access point that you created in Step 3 (for example, tutorial-access-point), and then choose Choose supporting Access Point.

  6. For S3 APIs, to retrieve objects from the S3 bucket for Lambda function to process, select GetObject.

  7. For Invoke Lambda function, you can choose either of the following two options for this tutorial.

    • Choose Choose from functions in your account, and then choose the Lambda function that you created in Step 4 (for example, tutorial-object-lambda-function) from the Lambda function dropdown list.

    • Choose Enter ARN, and then enter the Amazon Resource Name (ARN) of the Lambda function that you created in Step 4.

  8. For Lambda function version, choose $LATEST (the latest version of the Lambda function that you created in Step 4).

  9. (Optional) If you need your Lambda function to recognize and process GET requests with range and part number headers, select Lambda function supports requests using range and Lambda function supports requests using part numbers. Otherwise, clear these two check boxes.

    For more information about how to use range or part numbers with S3 Object Lambda, see Working with Range and partNumber headers.

  10. (Optional) Under Payload - optional, add JSON text to provide your Lambda function with additional information.

    A payload is optional JSON text that you can provide to your Lambda function as input for all invocations coming from a specific S3 Object Lambda Access Point. To customize the behaviors for multiple Object Lambda Access Points that invoke the same Lambda function, you can configure payloads with different parameters, thereby extending the flexibility of your Lambda function.

    For more information about payload, see Event context format and usage.

  11. (Optional) For Request metrics - optional, choose Disable or Enable to add Amazon S3 monitoring to your Object Lambda Access Point. Request metrics are billed at the standard Amazon CloudWatch rate. For more information, see CloudWatch pricing.

  12. Under Object Lambda Access Point policy - optional, keep the default setting.

    (Optional) You can set a resource policy. This resource policy grants the GetObject API permission to use the specified Object Lambda Access Point.

  13. Keep the remaining settings set to the defaults, and choose Create Object Lambda Access Point.

Step 7: View the transformed data

Now, S3 Object Lambda is ready to transform your data for your use case. In this tutorial, S3 Object Lambda transforms all the text in your object to uppercase.

View the transformed data in your S3 Object Lambda Access Point

When you request to retrieve a file through your S3 Object Lambda Access Point, you make a GetObject API call to S3 Object Lambda. S3 Object Lambda invokes the Lambda function to transform your data, and then returns the transformed data as the response to the standard S3 GetObject API call.

  1. Sign in to the AWS Management Console and open the Amazon S3 console at https://console.aws.amazon.com/s3/.

  2. In the left navigation pane, choose Object Lambda Access Points.

  3. On the Object Lambda Access Points page, choose the S3 Object Lambda Access Point that you created in Step 6 (for example, tutorial-object-lambda-accesspoint).

  4. On the Objects tab of your S3 Object Lambda Access Point, select the file that has the same name (for example, tutorial.txt) as the one that you uploaded to the S3 bucket in Step 2.

    This file should contain all the transformed data.

  5. To view the transformed data, choose Open or Download.

Run a Python script to print the original and transformed data

You can use S3 Object Lambda with your existing applications. To do so, update your application configuration to use the new S3 Object Lambda Access Point ARN that you created in Step 6 to retrieve data from S3.

The following example Python script prints both the original data from the S3 bucket and the transformed data from the S3 Object Lambda Access Point.

  1. Sign in to the AWS Management Console and open the Amazon S3 console at https://console.aws.amazon.com/s3/.

  2. In the left navigation pane, choose Object Lambda Access Points.

  3. On the Object Lambda Access Points page, choose the radio button to the left of the S3 Object Lambda Access Point that you created in Step 6 (for example, tutorial-object-lambda-accesspoint).

  4. Choose Copy ARN.

  5. Save the ARN for use later.

  6. Write a Python script on your local machine to print both the original data (for example, tutorial.txt) from your S3 Bucket and the transformed data (for example, tutorial.txt) from your S3 Object Lambda Access Point). You can use the following example script.

    import boto3 from botocore.config import Config s3 = boto3.client('s3', config=Config(signature_version='s3v4')) def getObject(bucket, key): objectBody = s3.get_object(Bucket = bucket, Key = key) print(objectBody["Body"].read().decode("utf-8")) print("\n") print('Original object from the S3 bucket:') # Replace the two input parameters of getObject() below with # the S3 bucket name that you created in Step 1 and # the name of the file that you uploaded to the S3 bucket in Step 2 getObject("tutorial-bucket", "tutorial.txt") print('Object transformed by S3 Object Lambda:') # Replace the two input parameters of getObject() below with # the ARN of your S3 Object Lambda Access Point that you saved earlier and # the name of the file with the transformed data (which in this case is # the same as the name of the file that you uploaded to the S3 bucket # in Step 2) getObject("arn:aws:s3-object-lambda:us-west-2:111122223333:accesspoint/tutorial-object-lambda-accesspoint", "tutorial.txt")
  7. Save your Python script with a custom name (for example, tutorial_print.py ) in the folder (for example, object-lambda) that you created in Step 4 on your local machine.

  8. In your local terminal, run the following command from the root of the directory (for example, object-lambda) that you created in Step 4.

    python3 tutorial_print.py

    You should see both the original data and the transformed data (all text as uppercase) through the terminal. For example, you should see something like the following text.

    Original object from the S3 bucket: Amazon S3 Object Lambda Tutorial: You can add your own code to process data retrieved from S3 before returning it to an application. Object transformed by S3 Object Lambda: AMAZON S3 OBJECT LAMBDA TUTORIAL: YOU CAN ADD YOUR OWN CODE TO PROCESS DATA RETRIEVED FROM S3 BEFORE RETURNING IT TO AN APPLICATION.

Step 8: Clean up

If you transformed your data through S3 Object Lambda only as a learning exercise, delete the AWS resources that you allocated so that you no longer accrue charges.

Delete the Object Lambda Access Point

  1. Sign in to the AWS Management Console and open the Amazon S3 console at https://console.aws.amazon.com/s3/.

  2. In the left navigation pane, choose Object Lambda Access Points.

  3. On the Object Lambda Access Points page, choose the radio button to the left of the S3 Object Lambda Access Point that you created in Step 6 (for example, tutorial-object-lambda-accesspoint).

  4. Choose Delete.

  5. Confirm that you want to delete your Object Lambda Access Point by entering its name in the text field that appears, and then choose Delete.

Delete the S3 access point

  1. Sign in to the AWS Management Console and open the Amazon S3 console at https://console.aws.amazon.com/s3/.

  2. In the left navigation pane, choose Access Points.

  3. Navigate to the access point that you created in Step 3 (for example, tutorial-access-point), and choose the radio button next to the name of the access point.

  4. Choose Delete.

  5. Confirm that you want to delete your access point by entering its name in the text field that appears, and then choose Delete.

Delete the execution role for your Lambda function

  1. Sign in to the AWS Management Console and open the AWS Lambda console at https://console.aws.amazon.com/lambda/.

  2. In the left navigation pane, choose Functions.

  3. Choose the function that you created in Step 4 (for example, tutorial-object-lambda-function).

  4. On your Lambda function's details page, choose the Configuration tab, and then choose Permissions in the left navigation pane.

  5. Under Execution role, choose the link of the Role name. The IAM console opens.

  6. On the IAM console's Summary page of your Lambda function's execution role, choose Delete role.

  7. In the Delete role dialog box, choose Yes, delete.

Delete the Lambda function

  1. In the AWS Lambda console at https://console.aws.amazon.com/lambda/, choose Functions in the left navigation pane.

  2. Select the check box to the left of the name of the function that you created in Step 4 (for example, tutorial-object-lambda-function).

  3. Choose Actions, and then choose Delete.

  4. In the Delete function dialog box, choose Delete.

Delete the CloudWatch log group

  1. Open the CloudWatch console at https://console.aws.amazon.com/cloudwatch/.

  2. In the left navigation pane, choose Log groups.

  3. Find the log group whose name ends with the Lambda function that you created in Step 4 (for example, tutorial-object-lambda-function).

  4. Select the check box to the left of the name of the log group.

  5. Choose Actions, and then choose Delete log group(s).

  6. In the Delete log group(s) dialog box, choose Delete.

Delete the original file in the S3 source bucket

  1. Sign in to the AWS Management Console and open the Amazon S3 console at https://console.aws.amazon.com/s3/.

  2. In the left navigation pane, choose Buckets.

  3. In the Bucket name list, choose the name of the bucket that you uploaded the original file to in Step 2 (for example, tutorial-bucket).

  4. Select the check box to the left of the name of the object that you want to delete (for example, tutorial.txt).

  5. Choose Delete.

  6. On the Delete objects page, in the Permanently delete objects? section, confirm that you want to delete this object by entering permanently delete in the text box.

  7. Choose Delete objects.

Delete the S3 source bucket

  1. Sign in to the AWS Management Console and open the Amazon S3 console at https://console.aws.amazon.com/s3/.

  2. In the left navigation pane, choose Buckets.

  3. In the Buckets list, choose the radio button next to the name of the bucket that you created in Step 1 (for example, tutorial-bucket).

  4. Choose Delete.

  5. On the Delete bucket page, confirm that you want to delete the bucket by entering the bucket name in the text field, and then choose Delete bucket.

Delete the IAM user

  1. Sign in to the AWS Management Console and open the IAM console at https://console.aws.amazon.com/iam/.

  2. In the left navigation pane, choose Users, and then select the check box next to the user name that you want to delete.

  3. At the top of the page, choose Delete.

  4. In the Delete user name? dialog box, enter the user name in the text input field to confirm the deletion of the user. Choose Delete.

Next steps

After completing this tutorial, you can customize the Lambda function for your use case to modify the data returned by standard S3 GET requests.

The following is a list of common use cases for S3 Object Lambda:

For more information about S3 Object Lambda, see Transforming objects with S3 Object Lambda.