Support AWS SDK 2.0

[mv78]

AWS currently in the process or releasing SDK 2.0. It would be good to start integrating it into the project as it progresses to GA.

[aemruli]

@mv78 just checked today. At least from the information I found they are in the preview. Hence we are waiting once AWS has released a final 2.0.
I have updated the project to use the latest AWS SDK 1.x

[ajainy]

Can we upgrade AWS SDK v1.11.321 (latest as of May, 2018) ..?
@aemruli

Or please share your last commit, i will do similar.

[aemruli]

@ajainy we have upgraded master to 1.11.336

[michl-b]

Are there any news on this?
Usage with JDK11 gives some warnings on a class used in the old V1 of aws-sdk-java

WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by com.amazonaws.util.XpathUtils (file:/Users/michael/.m2/repository/com/amazonaws/aws-java-sdk-core/1.11.415/aws-java-sdk-core-1.11.415.jar) to method com.sun.org.apache.xpath.internal.XPathContext.getDTMManager() WARNING: Please consider reporting this to the maintainers of com.amazonaws.util.XpathUtils WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release

[kmualem]

Hi guys

Any news about AWS SDK version 2?

[michaelwiles]

Yes, problem with AWS SDK version 1 is it doesn't play nice with JDK 9 as it duplicates packages across individual jars.

Although an upgrade like this would touch a lot of classes it wouldn't be too hard to do as it's a simple job to upgrade to the new SDK and the new SDK is a lot easier to work with (imo it has a more fluent api).

[artembilan]

See another reason to do this: #491
Also here: spring-projects/spring-integration-aws#155

Thanks

[tinexw]

I started working on this here https://github.com/tinexw/spring-cloud-aws/tree/gh-267

If anyone wants to join, please let me know!

I would also like to get some insight from the maintainers what the best way to go about this is. I just started fixing compile errors and committed everything in one big commit. Not sure if that is a good idea.

Also, I'm just assuming we don't need to care about backwards compatibility. But is that correct?

[spencergibb]

@tinexw not sure how this would work as updating major versions of a dependency would be a breaking change

[tinexw]

Yeah, that's why I was asking what the preferred approach in this case is. Release a new major version?

[OlgaMaciaszek]

We would be very happy to take this upgrade PR, but we can't put backwards-incompatible changes within the Hoxton release train, cause it's not going to be a major. We will be shortly deciding if our next release train will be major (we will probably branch it out in a few months). If yes, then these changes could be merged there.

[tinexw]

Ok, thanks for the update. There is quite a lot left. I will pick it up again once you know for sure if it’s going to be a major release.

[sp00m]

Yet another reason to upgrade: EKS supports 2.10.11+ only... Any ETA yet?

[tcheek-bw]

Is this still being worked on? The 2.0 SDK would be really nice to have.

[spencergibb]

@tinexw started working on it and now that master would be a major release we would be happy to accept it.

[tinexw]

Good to know :-) I will pick it back up. Would be great to get some support especially in regards to testing later on.

[sp00m]

Just as an FYI, this ticket blocked us going forward, so we decided to develop our own abstraction for our Spring WebFlux projects, so that we could connect to SQS from within EKS: https://github.com/qudini/qudini-reactive/tree/master/qudini-reactive-sqs. Very SQS (and WebFlux) focused obviously, and by no means intended to replace https://github.com/spring-cloud/spring-cloud-aws, but maybe it can help resolving this issue somehow :)

[maciejwalkowiak]

Thanks @sp00m! We are going to move to SDK v2 in 3.0 and revisit SQS integration so we are definitely going to look at your repository for an inspiration.

[internetstaff]

Perhaps Spring Cloud AWS 3.0 could just be an upgrade to SDK v2 in order to knock that out sooner rather than later?

We're starting to hit issues like SSO that simply aren't supported in SDK v1.

[spencergibb]

The repo that would handle this is https://github.com/awspring/spring-cloud-aws