Support DigiCert G5 family as TLS issuance hierarchy will change from G2/G3

Open Beginner friendly
#3,423 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
ruby
Domain
security

Research direction

Start with gems/aws-sdk-core/ca-bundle.crt and review the DigiCert G5 root and intermediate certificate information linked in the issue. Update the bundled certificates to support the new DigiCert TLS issuance hierarchy, then verify the bundle contains the required G5 certificates and does not remove existing coverage.

Written by the indexing model from the issue text.

Description

feature-request needs-triage
Describe the feature

Bundled certs in https://github.com/aws/aws-sdk-ruby/blob/version-3/gems/aws-sdk-core/ca-bundle.crt are very old. Based on https://knowledge.digicert.com/general-information/digicert-g5-root-and-intermediate-ca-certificate-update, from Oct. 15, 2026, DigiCert will change the default public TLS issuance hierarchy from the DigiCert Global G2 and G3 root hierarchies to the dedicated DigiCert G5 TLS root hierarchies.
Consequently, after October 15, there is a risk of connection failures to any non-AWS endpoints accessed via the AWS SDK that present a certificate chained to DigiCert G5.

Use Case

After October 15, there is a risk of connection failures to any non-AWS endpoints accessed via the AWS SDK that present a certificate chained to DigiCert G5.

Proposed Solution

No response

Other Information

No response

Acknowledgements
  • I may be able to implement this feature request
  • This feature might incur a breaking change
SDK version used

latest

Environment details (OS name and version, etc.)

any OS

Dominant language
Ruby
Stars
3.7k
Forks
1.2k
Avg merge
1d 7h
Merged PRs (30d)
5

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from aws/aws-sdk-ruby

All issues in aws/aws-sdk-ruby

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.