You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Maintenance: end of support for aws-encryption-sdk 3.x #8190
We just bumped the minimum to >=3.3.1 to address CVE-2026-6550, but we still carry the full 3.x range. The 3.x line is in maintenance mode upstream and we'd rather simplify our dependency surface.
We are planning in 3 months (targeting August 2026) to drop support for 3.x entirely.
No Powertools utility will be affected by this change. However, if you bring Powertools alongside aws-encryption-sdk pinned to v3, you'll hit dependency resolution conflicts. If you're still on 3.x, please start planning your migration to 4.x.
I decided to go ahead and drop aws-encryption-sdk 3.x now instead of waiting. A few reasons behind that call:
The 3.x version keeps picking up security issues, and it's in maintenance mode upstream. Carrying a version range that spans two majors (3.x and 4.x) has been more painful than it's worth becayse the constraint is already full of exclusions we had to add one by one as problems came up, and honestly that approach doesn't scale. Every new CVE means another patch to the range.
Security comes first for us, so I'd rather move everyone to 4.x cleanly than keep maintaining a messy range that straddles both. No Powertools utility is affected by this and the data masking provider uses the same API on 3.x and 4.x. The only impact is if you bring Powertools alongside aws-encryption-sdk pinned to 3.x, in which case you'll hit a resolution conflict and need to move to 4.x.
So I'm bumping the minimum to >=4.0.5,<5.0.0. If you're still on 3.x, please start planning the move and I'm happy to help if you run into anything.
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.
Activity
leandrodamascena commentedon Jul 12, 2026
Hey folks, quick update on this one.
I decided to go ahead and drop
aws-encryption-sdk3.x now instead of waiting. A few reasons behind that call:The 3.x version keeps picking up security issues, and it's in maintenance mode upstream. Carrying a version range that spans two majors (3.x and 4.x) has been more painful than it's worth becayse the constraint is already full of exclusions we had to add one by one as problems came up, and honestly that approach doesn't scale. Every new CVE means another patch to the range.
Security comes first for us, so I'd rather move everyone to 4.x cleanly than keep maintaining a messy range that straddles both. No Powertools utility is affected by this and the data masking provider uses the same API on 3.x and 4.x. The only impact is if you bring Powertools alongside
aws-encryption-sdkpinned to 3.x, in which case you'll hit a resolution conflict and need to move to 4.x.So I'm bumping the minimum to
>=4.0.5,<5.0.0. If you're still on 3.x, please start planning the move and I'm happy to help if you run into anything.powertools-for-aws-oss-automation commentedon Jul 13, 2026
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.
github-actions commentedon Jul 13, 2026
This is now released under 3.31.1 version!