Skip to content

aws/transport/http: set TLS curve preferences - #3454

Open
sverma98015-commits wants to merge 1 commit into
aws:mainfrom
sverma98015-commits:fix-fips-curves
Open

aws/transport/http: set TLS curve preferences#3454
sverma98015-commits wants to merge 1 commit into
aws:mainfrom
sverma98015-commits:fix-fips-curves

Conversation

@sverma98015-commits

Copy link
Copy Markdown

Summary

This change updates the default HTTP transport configuration to explicitly set TLS curve preferences.

Changes

  • Added TLS curve preferences to tls.Config in defaultHTTPTransport:

    • CurveP256
    • CurveP384
    • CurveP521
  • Ensures consistent elliptic curve selection for TLS connections.

  • Added unit test to validate:

    • TLS minimum version is TLS 1.2
    • TLS configuration is properly initialized

Motivation

Improves TLS configuration clarity and ensures predictable elliptic curve usage in secure connections.

Testing

  • Ran go test ./aws/transport/http
  • All tests passing locally

Notes

No changes to generated code or service models.

@sverma98015-commits
sverma98015-commits requested a review from a team June 24, 2026 05:12
@lucix-aws

Copy link
Copy Markdown
Collaborator

Is there motivation for this beyond clarity? How were these values chosen? What potential impact does this have across the 400+ AWS services supported by this SDK today?

I am concerned about changing this without more context, even with that I would have pretty significant backwards-compatibility concerns.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants