Adrian Rumpold
02/28/2023, 9:01 AMgateways.s3.fallback_url
setting, but haven't been able to figure out exactly how to use it. Is there any documentation besides the configuration reference guide?
In particular, I'm unsure how to pass authentication credentials to the fallback backend: If I specify credentials that don't exist in lakeFS but are valid on the fallback S3 endpoint, I get an InvalidAccessKeyId
error returned by the aws s3
command. If I specify the lakeFS credentials and try to access a bucket that would be handled by the fallback case, I get an AccessDenied
error.
Do the credentials need to be identical for both the lakeFS S3 endpoint and the fallback?
Thanks for your help! ๐Itai Admi
02/28/2023, 9:37 AMlakefs superuser
Error: required flag(s) "user-name" not set
Usage:
lakefs superuser [flags]
Flags:
--access-key-id string create this access key ID for the user (for ease of integration)
-h, --help help for superuser
--secret-access-key string use this access key secret (potentially insecure, use carefully for ease of integration)
--user-name string an identifier for the user (e.g. "jane.doe")
Adrian Rumpold
02/28/2023, 9:55 AMOz Katz
02/28/2023, 11:06 AMAdrian Rumpold
02/28/2023, 11:13 AMFlyteFile
resources. However, Flyte also puts its own metadata into the same S3 endpoint, which we obviously don't want to end up in lakeFS.
So we could either add an S3 request router in front of lakeFS, or use the fallback feature in lakeFS.Oz Katz
02/28/2023, 11:36 AMAdrian Rumpold
02/28/2023, 12:44 PM