Skip to content

Generate SigV4 auth for AWS Python clients - #971

Open
stobrien89 wants to merge 2 commits into
python-client-aws-configfrom
python-client-sigv4
Open

stobrien89 wants to merge 2 commits into
python-client-aws-configfrom
python-client-sigv4

Conversation

@stobrien89

@stobrien89 stobrien89 commented Nov 20, 2026 •

Copy link
Copy Markdown
Contributor

Issue #, if available:

Stacked on #967.

Description of changes:

AWS services with aws.auth#sigv4 now get SigV4 auth, matching Java:

  • Configs default auth_schemes to SigV4AuthScheme / AsyncSigV4AuthScheme for the signing name. The credential fields already come from AwsConfig.
  • When the config has no credentials resolver, _post_setup sets the default AWS credentials chain, using the config's profile, region and transport.

Fixes a planning bug: aws.auth#sigv4 was only counted as an auth scheme if its trait definition was in the AST. AWS model ASTs leave it out, so every operation fell back to noAuth and would have been generated unsigned.

Adds auth_schemes, write_client_methods and endpoint_test_config hooks to ClientIntegration.

The per-feature snapshots (endpoint-rules-client, api-key-auth-client, aws-config-client) are folded into one features-client. It's a single AWS service built from models/features.smithy, with endpoint rules and tests, SigV4, API key auth, @optionalAuth and @auth([]).

S3 signing properties come with S3 support.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@stobrien89
stobrien89 requested a review from a team as a code owner November 20, 2026 17:48
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.

1 participant