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

[Docs] Document workaround when using private link endpoints with us-east-1 #243

Open
robbavey opened this issue Feb 7, 2022 · 0 comments

Comments

@robbavey
Copy link
Contributor

robbavey commented Feb 7, 2022

As with the issue reported in the S3 input plugin in logstash-plugins/logstash-input-s3#234, when using private link endpoints with us-east-1, the plugin will fail to write to the specified bucket, producing the following error:

[2022-02-03T08:20:59,305][ERROR][logstash.outputs.s3      ][main] Failed to upload file (retried 3 times). {:exception=>Seahorse::Client::NetworkingError, :message=>"Failed to open TCP connection to mybucket.bucket.vpce-vpcid.s3.vpce.amazonaws.com:443 (initialize: name or service not known)"

This is due to a problem fixed in aws/aws-sdk-ruby#2483, but not backported to v2 of the AWS-SDK, where us-east-1 will be stripped from the url when using the IAD regional endpoint plugin (which is included by default).

This should be able to be circumvented by setting s3_us_east_1_regional_endpoint=regional in the aws config file.

@robbavey robbavey changed the title [Docs] [Docs] Document workaround when using private link endpoints with us-east-1 Feb 7, 2022
@robbavey robbavey added the docs label Feb 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant