This is an automated email from the ASF dual-hosted git repository.
fanningpj pushed a commit to branch 1.2.x
in repository https://gitbox.apache.org/repos/asf/pekko-management.git
The following commit(s) were added to refs/heads/1.2.x by this push:
new edc9f31f docs: say that pekko-discovery-aws-api is deprecated (#670)
(#673)
edc9f31f is described below
commit edc9f31f623c58c677587db4295870fbf8bff1cc
Author: PJ Fanning <[email protected]>
AuthorDate: Wed Mar 4 11:51:53 2026 +0100
docs: say that pekko-discovery-aws-api is deprecated (#670) (#673)
* docs: say that pekko-discovery-aws-api is deprecated
* Update aws.md
* log deprecation warning
---
.../awsapi/ec2/Ec2TagBasedServiceDiscovery.scala | 4 +++
.../discovery/awsapi/ecs/EcsServiceDiscovery.scala | 7 +++++
docs/src/main/paradox/discovery/aws.md | 34 ++++++++++++++--------
docs/src/main/paradox/discovery/index.md | 4 +--
4 files changed, 34 insertions(+), 15 deletions(-)
diff --git
a/discovery-aws-api/src/main/scala/org/apache/pekko/discovery/awsapi/ec2/Ec2TagBasedServiceDiscovery.scala
b/discovery-aws-api/src/main/scala/org/apache/pekko/discovery/awsapi/ec2/Ec2TagBasedServiceDiscovery.scala
index 88682029..58a35dbb 100644
---
a/discovery-aws-api/src/main/scala/org/apache/pekko/discovery/awsapi/ec2/Ec2TagBasedServiceDiscovery.scala
+++
b/discovery-aws-api/src/main/scala/org/apache/pekko/discovery/awsapi/ec2/Ec2TagBasedServiceDiscovery.scala
@@ -56,6 +56,10 @@ final class Ec2TagBasedServiceDiscovery(system:
ExtendedActorSystem) extends Ser
private val log = Logging(system, classOf[Ec2TagBasedServiceDiscovery])
+ log.warning(
+ "`pekko-discovery-aws-api` is deprecated because it uses the AWS SDK v1,
which is no longer maintained. " +
+ "Consider switching to `pekko-discovery-aws-api-async`, which uses the AWS
SDK v2 and is actively maintained.")
+
private implicit val ec: ExecutionContext =
system.dispatchers.lookup("pekko.actor.default-blocking-io-dispatcher")
private val config =
system.settings.config.getConfig("pekko.discovery.aws-api-ec2-tag-based")
diff --git
a/discovery-aws-api/src/main/scala/org/apache/pekko/discovery/awsapi/ecs/EcsServiceDiscovery.scala
b/discovery-aws-api/src/main/scala/org/apache/pekko/discovery/awsapi/ecs/EcsServiceDiscovery.scala
index 1d21a94a..0cd4c9ba 100644
---
a/discovery-aws-api/src/main/scala/org/apache/pekko/discovery/awsapi/ecs/EcsServiceDiscovery.scala
+++
b/discovery-aws-api/src/main/scala/org/apache/pekko/discovery/awsapi/ecs/EcsServiceDiscovery.scala
@@ -20,6 +20,7 @@ import pekko.actor.ActorSystem
import pekko.discovery.{ Lookup, ServiceDiscovery }
import pekko.discovery.ServiceDiscovery.{ Resolved, ResolvedTarget }
import pekko.discovery.awsapi.ecs.EcsServiceDiscovery.resolveTasks
+import pekko.event.Logging
import pekko.pattern.after
import pekko.util.ccompat.JavaConverters._
@@ -37,6 +38,12 @@ import scala.util.Try
final class EcsServiceDiscovery(system: ActorSystem) extends ServiceDiscovery {
+ private val log = Logging(system, classOf[EcsServiceDiscovery])
+
+ log.warning(
+ "`pekko-discovery-aws-api` is deprecated because it uses the AWS SDK v1,
which is no longer maintained. " +
+ "Consider switching to `pekko-discovery-aws-api-async`, which uses the AWS
SDK v2 and is actively maintained.")
+
private[this] val config =
system.settings.config.getConfig("pekko.discovery.aws-api-ecs")
private[this] val cluster = config.getString("cluster")
diff --git a/docs/src/main/paradox/discovery/aws.md
b/docs/src/main/paradox/discovery/aws.md
index e83fe04f..8f7ce917 100644
--- a/docs/src/main/paradox/discovery/aws.md
+++ b/docs/src/main/paradox/discovery/aws.md
@@ -2,7 +2,7 @@
If you're using EC2 directly _or_ you're using ECS with host mode networking
_and_ you're deploying one container per cluster member, continue to
-@ref:[Discovery Method: AWS API - EC2 Tag-Based
Discovery](aws.md#discovery-method-aws-api-ec2-tag-based-discovery).
+@ref:[Discovery Method: AWS API - EC2 Tag-Based
Discovery](aws.md#discovery-method-aws-api-ec2-tag-based-discovery). This
support is **deprecated**.
If you're using ECS with
[awsvpcs](https://aws.amazon.com/blogs/compute/introducing-cloud-native-networking-for-ecs-containers/)
@@ -23,6 +23,12 @@ instead.
### Discovery Method: AWS API - EC2 Tag-Based Discovery
+@@@ warning
+ `pekko-discovery-aws-api` is deprecated because it uses AWS SDK v1 which has
reached
+ [end of
life](https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-aws-sdk-for-java-v1-x-on-december-31-2025/).
+ We do not currently have an implementation of EC2 Tag-Based Discovery in
`pekko-discovery-aws-api-async`, the recommended replacement.
+@@@
+
You can use tags to simply mark the instances that belong to the same cluster.
Use a tag that
has "service" as the key and set the value equal to the name of your service
(same value as
`pekko.management.cluster.bootstrap.contact-point-discovery.service-name`
defined in `application.conf`, if you're using this module for bootstrapping
your Pekko cluster).
@@ -41,6 +47,11 @@ ensure the "Tag New Instances" option is checked.
#### Dependencies and usage (EC2 Tag-Based Discovery)
+@@@ warning
+ `pekko-discovery-aws-api` is deprecated because it uses AWS SDK v1 which has
reached
+ [end of
life](https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-aws-sdk-for-java-v1-x-on-december-31-2025/).
+@@@
+
This is a separate JAR file:
@@dependency[sbt,Gradle,Maven] {
@@ -153,9 +164,14 @@ There are two "flavours" of the ECS Discovery module.
##### pekko-discovery-aws-api
-This uses the mainstream AWS SDK. The advantage here is that if you've already
-got the mainstream AWS SDK as a dependency you're not now also bringing in the
-preview SDK. The disadvantage is that the mainstream SDK does blocking IO.
+@@@ warning
+ `pekko-discovery-aws-api` is deprecated because it uses AWS SDK v1 which has
reached
+ [end of
life](https://aws.amazon.com/blogs/developer/announcing-end-of-support-for-aws-sdk-for-java-v1-x-on-december-31-2025/).
+@@@
+
+This uses the AWS SDK v1 which ha reached end of life. It is recommended that
you use
+the `pekko-discovery-aws-api-async` dependency instead.
+The main disadvantage of this old lib is that the SDK v1 uses blocking IO.
@@dependency[sbt,Gradle,Maven] {
symbol1=PekkoManagementVersion
@@ -180,14 +196,8 @@ pekko.discovery {
##### pekko-discovery-aws-api-async
-This uses the preview AWS SDK. The advantage here is that the SDK does
-non-blocking IO, which you probably want. You might need to think carefully
-before using this though if you've already got the mainstream AWS SDK as a
-dependency.
-
-Once the async AWS SDK is out of preview it is likely that the
-`pekko-discovery-aws-api` module will be discontinued in favour of
-`pekko-discovery-aws-api-async`.
+This uses AWS SDK v2. The advantage here is that the SDK does
+non-blocking IO, which you probably want.
@@dependency[sbt,Gradle,Maven] {
symbol1=PekkoManagementVersion
diff --git a/docs/src/main/paradox/discovery/index.md
b/docs/src/main/paradox/discovery/index.md
index d3504525..d1ce5da8 100644
--- a/docs/src/main/paradox/discovery/index.md
+++ b/docs/src/main/paradox/discovery/index.md
@@ -1,8 +1,6 @@
# Apache Pekko Discovery Methods
-As of version `1.0.0` of Pekko Management @extref:[Pekko
Discovery](pekko:discovery/index.html)
-has become a core Pekko module. Older versions of Service Discovery from Pekko
Management are not compatible with the
-Pekko Discovery module in Pekko.
+@extref:[Pekko Discovery](pekko:discovery/index.html) is a core Pekko module.
Pekko Management contains methods for:
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
