-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
S3 with :use_fips_endpoint fails #2718
Comments
Whats the actual bucket name you're using? The issue here I believe is that in the FIPS regions, the bucket needs to be the endpoint host prefix, but the uri in your stack trace doesn't have the bucket name. With a DNS compatible bucket, I see the correct behavior, eg:
However, our bucket_dns plugin will check for dns compatible bucket names, and only move the bucket name to the endpoint prefix when it is: https://github.com/aws/aws-sdk-ruby/blob/version-3/gems/aws-sdk-s3/lib/aws-sdk-s3/plugins/bucket_dns.rb#L44, eg:
|
|
Later I figured out
I think the key for my issue is Maybe an error should be thrown when using fips endpoints with a dotted bucket? Or maybe a few notes about using fips endpoints in documentation can help. Thank you again. |
I wanted to add a note about Of course even better is to set this option automatically for fips endpoint. Also an option to force domain style URLs would be very useful. For people that decide or need to go that route, for example with a custom CA validation. |
|
Describe the bug
When creating S3 client with
:use_fips_endpoint
I can't access bucket still.This is related to #2645
Expected Behavior
Things to work.
Current Behavior
Reproduction Steps
Possible Solution
Probably discovery as described here can help: hashicorp/terraform-provider-aws#14217
Additional Information/Context
No response
Gem name ('aws-sdk', 'aws-sdk-resources' or service gems like 'aws-sdk-s3') and its version
aws-sdk-s3
Environment details (Version of Ruby, OS environment)
Red Hat Enterprise Linux 7, Ruby 2.6.7
The text was updated successfully, but these errors were encountered: