Use AWS SDK for Java v2

[ChristopherHahnTR]

Is your feature request related to a problem? Please describe.

AWS SDK for Java 1.x has entered maintenance mode July 31, 2024 and will be end of support Dec 31, 2025.
We are using eureka in AWS for an application storing government data which requires FIPS endpoints. My understanding is the sdk-v2 supports these requirements and v1 does not.
Describe the solution you'd like
I believe the solution is to change the classes in com.netflix.eureka.aws to use the sdk-v2 classes, as described in this link (with migration process)
https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/home.html

Describe alternatives you've considered
The only way I see to make our server "fips compliant" per our architect team is to update aws sdk. But I'm trying to get more details on if the endpoints used by eureka really need to be 'fips compliant'.

I have this PR with potential changes:
#1597

Except for the config switch UseAwsSdkV2, I have tested these changes with spring-boot-eureka. That change also requires an update to spring-boot-eureka.

[spencergibb]

I see you made the PR against master. This is a major breaking change and I think it shouldn't be released in any version except a major, unless the work can be put in separate modules like jersey 3 https://github.com/Netflix/eureka/tree/2.x/eureka-core-jersey3

[ChristopherHahnTR]

You commented on my other post as well, thanks for the replies, I'm new to this.
I'm going to rework the PR to go against the 2.0 branch.

Is there a branch I should target to be properly considered?
It should be possible to use injection to make backwards compatible, for example my new classes only get used if AWS jdk 2 is on the class path.. but I wasn't sure that would be necessary. These are the only three classes that use the aws jdk to my knowledge.

[spencergibb]

It should be possible to use injection to make backwards compatible, for example my new classes only get used if AWS jdk 2 is on the class path..

Yes, then it doesn't need a new major.

[spencergibb]

You commented on my other post as well, thanks for the replies, I'm new to this.

Absolutely! I'm on the Spring Cloud team. I wrote the 2.x upgrade mostly for Spring Framework 6 and Spring Boot 3 support.

[ChristopherHahnTR]

In your opinion, is the breaking part of this change the upgrade of AWS JDK jars, or the changes I made to awsEndpointOverrided (or both).
This is my first contribution to a public project and I see that decisions like the endpoint overrides should be thought through more.
I didn't think that just updating the jars would be considered breaking. They can be used alongside version 1 jars.

I will rework my changes.