refactor: drop aws crates for s3

We were just using them for S3 support. This PR switches us over to the s3 crate which works the same way, with some minor differences.

The main implication of this change is that we're no longer doing all the AWS stuff, like checking aws profile in home directory, or automatic discovery of metadata.

This change is covered by our brand new s3 test suite, but I also did the old school `just test-full` with minio.
This commit is contained in:
Johanna Larsson
2026-09-27 09:00:44 +00:00
committed by Tangled
parent 3054f04354
commit 66ea8287a0
8 changed files with 475 additions and 840 deletions
+1
View File
@@ -241,6 +241,7 @@
[storage]
# Storage backend: `filesystem` or `s3`.
# If you set `s3` you must also provide `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`.
#
# Can also be specified via environment variable `BLOB_STORAGE_BACKEND`.
#