-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
feat(libstore): add AWS SSO support for S3 authentication #14645
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
This enables seamless AWS SSO authentication for S3 binary caches without requiring users to manually export credentials. This adds SSO support by calling aws_credentials_provider_new_sso() from the C library directly. It builds a custom credential chain: Env → SSO → Profile → IMDS The SSO provider requires a TLS context for HTTPS connections to SSO endpoints, which is created once and shared across all providers.
Add validation for TLS context and client bootstrap initialization, with appropriate error messages when these fail. The TLS context failure is now a warning that gracefully disables SSO, while bootstrap failure throws since it's required for all providers.
The default (empty) profile case was using CreateCredentialsProviderChainDefault which didn't properly support role_arn/source_profile based role assumption via STS because TLS context wasn't being passed to the Profile provider. This change unifies the credential chain for all profiles (default and named), ensuring: - Consistent behavior between default and named profiles - Proper TLS context is passed for STS operations - SSO support works for both cases
| machine.fail(f"nix path-info {pkg}") | ||
| def setup_s3(populate_bucket=[], public=False, versioned=False): | ||
| def setup_s3(populate_bucket=[], public=False, versioned=False, profiles=None): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
BTW. It would make sense to start adding types here at some point. mypy is enabled in NixOS tests.
| if (!rawProvider) { | ||
| return nullptr; | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems unnecessary, considering the createWrapperProvider als does the nullptr check.
| apiHandle.InitializeLogging(logLevel, stderr); | ||
|
|
||
| // Create a shared TLS context for SSO (required for HTTPS connections) | ||
| auto allocator = Aws::Crt::ApiAllocator(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't this be a member of the class? I'm not sure about the lifetime requirements of the sdk for the allocator.
| auto bootstrap = Aws::Crt::ApiHandle::GetOrCreateStaticDefaultClientBootstrap(); | ||
| if (!bootstrap) { | ||
| throw AwsAuthError("failed to create AWS client bootstrap"); | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The bootstrap could also probably be a member and not rely on the singleton bootstrap.
| // including SSO support and proper TLS context for STS-based role assumption. | ||
| Aws::Crt::Auth::CredentialsProviderChainConfig chainConfig; | ||
| auto allocator = Aws::Crt::ApiAllocator(); | ||
| const char * profileName = profile.empty() ? "(default)" : profile.c_str(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The default is special-cases by the SDK?
Motivation
Context
Fixes: #14476
Add 👍 to pull requests you find important.
The Nix maintainer team uses a GitHub project board to schedule and track reviews.