Maintenance: All aws-powertools Libraries Depend on AWS X-Ray SDK (EoS Planned)

[yoshi-taka]

Why is this needed?

All aws-powertools libraries currently depend on the AWS X-Ray SDKs, which according to AWS documentation are scheduled for end-of-support on February 25, 2027.

Do you have any plans or a roadmap to address or replace this dependency (perhaps by migrating to the AWS Distro for OpenTelemetry (ADOT) or another supported tracing solution)?

https://docs.aws.amazon.com/xray/latest/devguide/xray-daemon-eos.html

Which area does this relate to?

Tracer

Solution

No response

Acknowledgment

• This request meets Powertools for AWS Lambda (Python) Tenets
• Should this be considered in other Powertools for AWS Lambda languages? i.e. Java, TypeScript, and .NET

[boring-cyborg]

Thanks for opening your first issue here! We'll come back to you as soon as we can.
In the meantime, check out the #python channel on our Powertools for AWS Lambda Discord: Invite link

[leandrodamascena]

Hey @yoshi-taka thanks a lot for opening this issue! We are aware of this deprecation, and it will specifically affect customers using our tracer utility.
As always, we are actively working to provide the best for our customers, and we already have an RFC in place to discuss the OTEL implementation in Powertools.
XRay EOL is planned for early 2027, which gives us time to ensure a smooth transition for customers from the XRay SDK to OTEL.

I encourage you to join the discussion that will help shape our future with OTEL support: aws-powertools/powertools-lambda#90.

I'm closing this issue, but feel free to reopen if needed.

[powertools-for-aws-oss-automation]

Warning

This issue is now closed. Please be mindful that future comments are hard for our team to see.
If you need more assistance, please either reopen the issue, or open a new issue referencing this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.