You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 18, 2023. It is now read-only.
However, in AWS computing, the SDKs should be able to auto-configure it from the multiple credential providers, so it works seamlessly in EC2, Fargate or EKS with IAM Roles. Instead of specifying the prefixing related env variables with bottomless IAM access keys through env variables, I think we should rely on Rust SDK so the proper chain can be used automatically. Currently it fails with:
$ sqld --enable-bottomless-replication
..
LIBSQL_BOTTOMLESS_AWS_DEFAULT_REGION was not set
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Looking at bottomless project readme and source code, it looks like it always expects AWS Access Key and Secret Key from ENV variables.
sqld/bottomless/src/replicator.rs
Line 140 in 146df90
However, in AWS computing, the SDKs should be able to auto-configure it from the multiple credential providers, so it works seamlessly in EC2, Fargate or EKS with IAM Roles. Instead of specifying the prefixing related env variables with bottomless IAM access keys through env variables, I think we should rely on Rust SDK so the proper chain can be used automatically. Currently it fails with:
The text was updated successfully, but these errors were encountered: