AWS AmazonS3 documentation change
Summary
Updated documentation about S3 Object Lambda deprecation alternatives, including minor wording changes and emphasis on security investments. Added explicit examples of sensitive data redaction as a use case for Lambda processing.
Security assessment
The change emphasizes AWS's continued security investments and adds 'sensitive data redaction' as an example use case, which relates to security features. However, there is no evidence of addressing a specific security vulnerability.
Diff
diff --git a/AmazonS3/latest/userguide/amazons3-ol-change.md b/AmazonS3/latest/userguide/amazons3-ol-change.md index 15dc4afe2..d541d5fcb 100644 --- a//AmazonS3/latest/userguide/amazons3-ol-change.md +++ b//AmazonS3/latest/userguide/amazons3-ol-change.md @@ -7 +7 @@ -After careful consideration, we have made the decision to only allow existing customers to utilize Amazon S3 Object Lambda starting on November 7th, 2025. Existing customers of S3 Object Lambda can continue to use the service as usual. AWS continues to invest in security and availability improvements for S3 Object Lambda, but we do not plan to introduce new capabilities. +After careful consideration, we have made the decision to only allow existing customers to utilize Amazon S3 Object Lambda starting on November 7th, 2025. Existing customers of S3 Object Lambda can continue to use the service as usual. AWS will continue to to invest in security and availability improvements for S3 Object Lambda, but we do not plan to introduce new capabilities. @@ -9 +9 @@ After careful consideration, we have made the decision to only allow existing cu -There are several alternative services and designs that allow you to modify and process data accessed from S3 to meet the needs of different client applications or users who are accessing the data. Those alternatives include the AWS Solution Dynamic Image Transformation for Amazon CloudFront, invoking AWS Lambda by other means (via CloudFront, API Gateway, or function URLs), or processing data in the client application. All of these alternatives continue to use Amazon S3 for the underlying storage, so no data migration is necessary. +There are several alternative services and designs that allow you to modify and process data accessed from S3 to meet the needs of various client applications or users who are accessing the data. Those alternatives include the AWS Solution Dynamic Image Transformation for Amazon CloudFront, invoking AWS Lambda by other means (via CloudFront, API Gateway, or function URLs), or processing data in the client application. All of these alternatives continue to use Amazon S3 for the underlying storage, so no data migration is necessary. @@ -15 +15 @@ In this post, we discuss how to choose the best option for your use case. -This AWS solution enables real-time image processing through the global content delivery network (CDN) of Amazon CloudFront using API Gateway and Lambda. It supports a variety of transformations such as format changes, dimensions, fit methods, rotations, and some Thumbor filters. If you are using S3 Object Lambda today for image transformation, this can be a good alternative. The [solution overview](https://docs.aws.amazon.com/solutions/latest/dynamic-image-transformation-for-amazon-cloudfront/solution-overview.html) has more details on capabilities and how to get started using it. Be sure to modify the Enable S3 Object Lambda template parameter to 'No' when deploying the solution to your account. +This AWS solution enables real-time image processing through the global content delivery network (CDN) of Amazon CloudFront using API Gateway and Lambda. It supports a variety of transformations such as format changes, dimensions, fit methods, rotations, and filters. If you are using S3 Object Lambda today for image transformation, this can be a good alternative. The [solution overview](https://docs.aws.amazon.com/solutions/latest/dynamic-image-transformation-for-amazon-cloudfront/solution-overview.html) has more details on capabilities and how to get started using it. Be sure to modify the Enable S3 Object Lambda template parameter to "No" when deploying the solution to your account. @@ -19 +19 @@ For more information, see [Dynamic Image Transformation for Amazon CloudFront](h -**AWS Lambda** +**Data processing in AWS Lambda** @@ -21 +21 @@ For more information, see [Dynamic Image Transformation for Amazon CloudFront](h -AWS Lambda is integrated with several other services that give you flexibility to continue using Lambda to modify and process data even without S3 Object Lambda. Your data processing logic can remain the same, but your Lambda function will need to be updated based on how you choose to invoke it. This option is best for use cases where the application that invokes S3 Object Lambda relies on receiving processed data. For example, if your S3 Object Lambda function performed sensitive data redaction or a data format change. This option also minimizes the changes required if you choose to migrate off S3 Object Lambda. +You can continue to use AWS Lambda for your data processing, but invoke it directly or through other AWS services. Your data processing logic can remain the same, but your Lambda function will need to be updated based on how you choose to invoke it. This option is best for use cases such as sensitive data redaction, format changes, or situations where the application that invokes S3 Object Lambda relies on receiving processed data. This option also minimizes the changes required if you choose to migrate off S3 Object Lambda. @@ -23 +23 @@ AWS Lambda is integrated with several other services that give you flexibility t -If you are using an S3 Object Lambda access point as the origin of a CloudFront distribution, you can create a new origin using either Lambda Function URLs or API Gateway. [This blog](https://aws.amazon.com/blogs/networking-and-content-delivery/using-amazon-cloudfront-with-aws-lambda-as-origin-to-accelerate-your-web-applications/) details how you can setup a Lambda Function URL to act as an origin in for your CloudFront distribution. +If you are using an S3 Object Lambda access point as the origin of a CloudFront distribution, you can create a new origin using either Lambda Function URLs or API Gateway. [This blog](https://aws.amazon.com/blogs/networking-and-content-delivery/using-amazon-cloudfront-with-aws-lambda-as-origin-to-accelerate-your-web-applications/) details how you can setup a Lambda Function URL to act as an origin for your CloudFront distribution.