Support AWS credential profiles in bottomless S3 replication ##
Maintainers usually reply within 11 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- aws
- Domain
- cloud
Research direction
Start by locating the bottomless S3 replication credential-handling entry point and reviewing how the listed LIBSQL_BOTTOMLESS_AWS_* variables are consumed. Compare that behavior with the AWS SDK credential provider chain and determine the intended profile environment variable. Done means credentials can be loaded from the standard AWS credentials file, a selected profile is supported, and the existing environment-variable behavior remains available.
Written by the indexing model from the issue text.
Description
Currently, libsql's bottomless S3 replication feature only accepts AWS credentials through environment variables:
- LIBSQL_BOTTOMLESS_AWS_ACCESS_KEY_ID
- LIBSQL_BOTTOMLESS_AWS_SECRET_ACCESS_KEY
- LIBSQL_BOTTOMLESS_AWS_SESSION_TOKEN (optional)
- LIBSQL_BOTTOMLESS_AWS_DEFAULT_REGION
The implementation does not read from the standard AWS credentials file (~/.aws/credentials) and doesn't support specifying a particular AWS profile.
Problem
This limitation creates several issues:
- It doesn't align with AWS best practices of using credential files and profiles
- It requires users to explicitly set environment variables even when credentials are already configured
- It makes it difficult to use in environments with multiple AWS accounts/roles
- It doesn't leverage the AWS SDK's built-in credential chain capabilities
Proposed Solution
Enhance the AWS credential handling in bottomless S3 replication to:
- Follow the standard AWS SDK credential provider chain
- Add support for reading from ~/.aws/credentials
- Add an optional environment variable to specify which profile to use
- Fall back to environment variables if no profile is specified or found
- Dominant language
- C
- Stars
- 17.3k
- Forks
- 562
- Avg merge
- 10d 15h
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tursodatabase/libsql
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
tursodatabase/libsql#2320 ·
Maintainers usually reply within 11 days
-
`cloudflare` feature: hrana streams are never closedPossibly taken @pcbeingused333 claimed this 4 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
tursodatabase/libsql#2312 ·
Maintainers usually reply within 11 days
-
bottomless: finished S3 upload tasks are never reaped, so sqld memory grows by ~10 KB per WAL batchPossibly taken @pavanmanishd claimed this 25 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
tursodatabase/libsql#2298 · 1 comment ·
Maintainers usually reply within 11 days
-
Rust local Row::get_value truncates embedded NUL TEXT and panics on malformed UTF-8 (0.9.30)Possibly taken @Sanjays2402 claimed this 35 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
tursodatabase/libsql#2285 ·
Maintainers usually reply within 11 days
-
libsql-ffi: broken builds under Nix on macOSPossibly taken @frectonz claimed this 85 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
tursodatabase/libsql#2275 ·
Maintainers usually reply within 11 days
All issues in tursodatabase/libsql
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
JulianKemmerer/PipelineC#395 ·
-
upstream-blocked
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
libretro/parallel-n64#858 ·