Skip to content

Commit

Permalink
Updates SDK to v2.293.0
Browse files Browse the repository at this point in the history
  • Loading branch information
awstools committed Aug 14, 2018
1 parent d3c7507 commit f7728f4
Show file tree
Hide file tree
Showing 24 changed files with 14,002 additions and 1,933 deletions.
17 changes: 17 additions & 0 deletions .changes/2.293.0.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
[
{
"type": "feature",
"category": "AutoScaling",
"description": "Add batch operations for creating/updating and deleting scheduled scaling actions."
},
{
"type": "feature",
"category": "CloudFront",
"description": "Lambda@Edge Now Provides You Access to the Request Body for HTTP POST/PUT Processing. With this feature, you can now offload more origin logic to the edge and improve end-user latency. Developers typically use Web/HTML forms or Web Beacons/Bugs as a mechanism to collect data from the end users and then process that data at their origins servers. For example, if you are collecting end user behavior data through a web beacon on your website, you can use this feature to access the user behavior data and directly log it to an Amazon Kinesis Firehose endpoint from the Lambda function, thereby simplifying your origin infrastructure."
},
{
"type": "feature",
"category": "ES",
"description": "Amazon Elasticsearch Service adds support for no downtime, in-place upgrade for Elasticsearch version 5.1 and above."
}
]
7 changes: 6 additions & 1 deletion CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,12 @@
# Changelog for AWS SDK for JavaScript
<!--LATEST=2.292.0-->
<!--LATEST=2.293.0-->
<!--ENTRYINSERT-->

## 2.293.0
* feature: AutoScaling: Add batch operations for creating/updating and deleting scheduled scaling actions.
* feature: CloudFront: Lambda@Edge Now Provides You Access to the Request Body for HTTP POST/PUT Processing. With this feature, you can now offload more origin logic to the edge and improve end-user latency. Developers typically use Web/HTML forms or Web Beacons/Bugs as a mechanism to collect data from the end users and then process that data at their origins servers. For example, if you are collecting end user behavior data through a web beacon on your website, you can use this feature to access the user behavior data and directly log it to an Amazon Kinesis Firehose endpoint from the Lambda function, thereby simplifying your origin infrastructure.
* feature: ES: Amazon Elasticsearch Service adds support for no downtime, in-place upgrade for Elasticsearch version 5.1 and above.

## 2.292.0
* feature: SageMaker: SageMaker updated the default endpoint URL to support Private Link via the CLI/SDK.

Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ version.
To use the SDK in the browser, simply add the following script tag to your
HTML pages:

<script src="https://sdk.amazonaws.com/js/aws-sdk-2.292.0.min.js"></script>
<script src="https://sdk.amazonaws.com/js/aws-sdk-2.293.0.min.js"></script>

You can also build a custom browser SDK with your specified set of AWS services.
This can allow you to reduce the SDK's size, specify different API versions of
Expand Down
Loading

0 comments on commit f7728f4

Please sign in to comment.