[I] AWS SDK V1 for Java no longer released [pekko-management]

["pjfanning (via GitHub)" <gi...@apache.org>]

pjfanning opened a new issue, #669:
URL: https://github.com/apache/pekko-management/issues/669

   EOL was end of 2025, apparently.
   
   We need to look at migration to SDK V2.
   
   https://github.com/apache/pekko-management/blob/main/project/Dependencies.scala#L26


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org

Re: [I] AWS SDK V1 for Java no longer released [pekko-management]

["pjfanning (via GitHub)" <gi...@apache.org>]

pjfanning commented on issue #669:
URL: https://github.com/apache/pekko-management/issues/669#issuecomment-3991493914

   discovery-aws-api module still depends on the legacy com.amazonaws (SDK v1) for both EC2 and ECS discovery, while discovery-aws-api-async already uses SDK V2.
   
   @mdedetrich @raboof @He-Pin @nvollmar should we just deprecate discovery-aws-api module and encourage users to switch to the async lib?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@pekko.apache.org
For additional commands, e-mail: notifications-help@pekko.apache.org