Skip to content
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

Match FIPS implementation between sdk v1 and sdk v2 #1119

Conversation

kgeckhart
Copy link
Contributor

@kgeckhart kgeckhart commented Aug 22, 2023

This PR mirrors the aws sdk v1 FIPS implementation to sdk v2. FIPS is enabled per client when running with FIPS enabled. I originally tried keeping the FIPS setting at the root config and explicitly disabling it for clients which did not support it. But testing showed the root config value takes precedence over client specific values.

As a part of double checking FIPS support on the services, I noticed Amazon Managed Prometheus does not appear to have any FIPS support on https://aws.amazon.com/compliance/fips/. I removed support for enabling FIPS is sdk v1 and v2.

The base branch is #1115 ATM since both PRs touch the sdk v2 client configs. I'll rebase this one after the retry setting is merged.

Resolves: #966

@kgeckhart kgeckhart force-pushed the kgeckhart/aws-sdk-v2-disable-fips-when-unavailable branch from 82ad660 to acfee4f Compare August 22, 2023 17:30
@cristiangreco cristiangreco merged commit 3525d64 into prometheus-community:master Aug 23, 2023
3 checks passed
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.

[BUG] AWS SDK v2 client attempts to use non-existing FIPS endpoint(s)
2 participants