might be a dumb question, but when using S3 sdk to...
# help
j
might be a dumb question, but when using S3 sdk tooling to communicate with the S3 Gateway exposed by LakeFS - what region should I be setting in the configuration of said SDK?
i
Hi John, If your lakeFS instance is deployed within a specific AWS region, it makes sense to use that same region in your SDK configuration. This can help with potential latency optimizations. If your buckets(repositories) reside in a specific region, aligning your S3 SDK region setting to that location could also be beneficial. If you set an incorrect region in your S3 SDK, you might still be able to access your data through lakeFS, but you could experience increased network latency.
j
what if we're running lakeFS in Azure and the block store is an azure blockstore though?
but we're using the LakeFS S3 Gateway to handle file uploading?
because my assumption is that region probably plays a part in signature validation
o
hey @John Darrington - you got it right, it is used for signing as well. The region configured on the server has to match the one configured on the clients. Since many S3 clients default to us-east-1, so does the server, but this is configurable on both ends. If you're on azure this makes little difference.
👍 1
👍🏽 1
j
sounds good