Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump AWS SDK to 2.13.1 #17

Merged
merged 1 commit into from Apr 28, 2020
Merged

Bump AWS SDK to 2.13.1 #17

merged 1 commit into from Apr 28, 2020

Conversation

stenlarsson
Copy link
Contributor

We got a mail from AWS a while back:

One or more applications in your AWS account has a dependency on asynchronous features of AWS SDK for Java V2. In versions below 2.10.56 of the AWS SDK for Java V2, the asynchronous clients (e.g. S3AsyncClient, SqsAsyncClient) resolve and cache the IP address of AWS Services once per channel pool, and the resolved IP is then used for all future connections to the host name until the client is closed. As a result, applications that use long-lived asynchronous SDK clients could use stale IP addresses to AWS services that can result in exceptions, and potentially not use the breadth of load balancing that the service provides, causing increased overall latency.

What Do I Need to Do?
Please upgrade your application dependency to AWS Java V2 SDK 2.10.56.

This bumps AWS SDK to the latest version which happens to be 2.13.1.

We got a mail from AWS a while back:

> One or more applications in your AWS account has a dependency on asynchronous features of AWS SDK for Java V2. In versions below 2.10.56 of the AWS SDK for Java V2, the asynchronous clients (e.g. S3AsyncClient, SqsAsyncClient) resolve and cache the IP address of AWS Services once per channel pool, and the resolved IP is then used for all future connections to the host name until the client is closed. As a result, applications that use long-lived asynchronous SDK clients could use stale IP addresses to AWS services that can result in exceptions, and potentially not use the breadth of load balancing that the service provides, causing increased overall latency.
>
> What Do I Need to Do?
> Please upgrade your application dependency to AWS Java V2 SDK 2.10.56 [1].
>
> [1] https://mvnrepository.com/artifact/software.amazon.awssdk/netty-nio-client/2.10.56

This bumps AWS SDK to the latest version which happens to be 2.13.1.
@stenlarsson stenlarsson self-assigned this Apr 23, 2020
@stenlarsson stenlarsson merged commit d1a5c85 into master Apr 28, 2020
@stenlarsson stenlarsson deleted the bump-aws-sdk branch April 28, 2020 13:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants