'InvalidAccessKeyId' error with replication to local MinIO container

[technimakri]

Hello, I'm following the Getting Started and Running in a Docker container tutorial. I'm trying to replicate a database from a litestream container to a minIO container on the same Docker network. I can log in through the minIO portal correctly using the minioadmin credentials and see my bucket. But when running litestream replicate from the litestream container I run into the following error:

replicating to: name="s3" type="s3" bucket="mybkt.minIO" path="db.sqlite3" region="" endpoint="" sync-interval=1s
/data/db.sqlite3(s3): monitor error: cannot lookup bucket region: InvalidAccessKeyId: The AWS Access Key Id you provided does not exist in our records.
        status code: 403, request id: QNH752G9NN0DVJEW, host id: gip60lFy8Ay7icKzFhG567cRzVT7ReDzyeWujbkPfICZpuFo+p3I0o+2EizO2Y2+GiPp5vjLXSA=

I've tried using the config file, replica url and environment variable methods of replicating, directly in the running container terminal with no success. I've also tried creating a new admin user and password and new access key + secret key in the minIO portal, which returns the same error. Any help or tips would be greatly appreciated!

My docker compose file:

services:
  minIO:
    image: minio/minio:latest
    ports:
      - "9000:9000"
      - "9001:9001"
    volumes:
      - minIOStorage:/data
    command: server /data --console-address ":9001"

  litestream:
    image: litestream/litestream:latest
    ports:
      - "9090"
    volumes:
      - localDb:/data
      - /home/technimakri/configs/litestream.yml:/etc/litestream.yml
    command: replicate

volumes:
  localDb:
  minIOStorage:
    
   

My litestream.yml file:

access-key-id:     minioadmin
secret-access-key: minioadmin

dbs:
  - path: /data/db.sqlite3
    replicas:
      - url: s3://mybkt.minIO:9000/db.sqlite3

[technimakri]

I've now realised that my setup wasn't trying to connect to my locally running minIO container, but rather trying to connect to AWS s3 directly. The error returned was correct there.

My (limited) understanding is that litestream uses regex to detect a localhost s3 type replica URL, which I mistakenly tried to extend to a docker network URL.

Looking back through the docs, I think this setup could be corrected using the endpoint config file option? That's what I'll try next.

[technimakri]

The following litestream config file indeed worked:

access-key-id:     minioadmin
secret-access-key: minioadmin

dbs:
  - path: /data/db.sqlite3
    replicas:
      - type: s3
        bucket: mybkt
        path: db.sqlite3
        endpoint: http://minIO:9000