forcing S3 is done only via SchemaMap?

[krkabol]

hello to RAIS team,
I know this software one day and I think I already love it, BUT: cannot find out the way how to interact with S3, can you please check what I'm missing? - it has to be some dummy tiny thing...

docker-compose.yml

   rais:
        image: uolibraries/rais:4-alpine
        container_name: rais
        links:
            -   minio
        environment:
            - RAIS_ADDRESS=:12415
            - RAIS_LOGLEVEL=DEBUG
            - RAIS_SCHEMEMAP=test=s3://test-iiif other=s3://xxx
            - RAIS_IIIFWEBPATH=/iiif
            - RAIS_IIIFBASEURL=http://localhost:8080
            - AWS_ACCESS_KEY_ID=test
            - AWS_SECRET_ACCESS_KEY=testSecret
            - AWS_REGION=us-west-2
            - AWS_SESSION_TOKEN
            - RAIS_S3_ENDPOINT=minio:9000
            - RAIS_S3_DISABLESSL=true
            - RAIS_S3_FORCEPATHSTYLE=true
        ports:
            - 8080:12415

Minio is running, keys are valid, bucket&object exists etc.

but a call http://localhost:8080/iiif/test/TEST_000022_8.jp2/full/max/0/default.jpg (that should be caught by SchemeMap IMO) doesn't work -> using TilePath :

docker logs rais
2025/11/06 12:47:33.197 - rais-server - INFO - No plugins will attempt to be loaded
2025/11/06 12:47:33.197 - rais-server - DEBUG - Serving images from "/var/local/images"
2025/11/06 12:47:33.197 - rais-server - INFO - Explicitly setting IIIF base URL to "http://localhost:8080"
2025/11/06 12:47:33.197 - rais-server - INFO - RAIS v4.2.1 starting...
2025/11/06 12:47:39.254 - rais-server - DEBUG - SchemeMap translated "test/TEST_000022_8.jp2" to URL "file:///var/local/images/test/TEST_000022_8.jp2"
2025/11/06 12:47:39.254 - rais-server - INFO - Request: [172.22.0.1:57290] /iiif/test/TEST_000022_8.jp2/full/max/0/default.jpg - 404

• I expect that should there be a problem with S3 connection, it would throw an error? - no error
• tested with full and alpine, 4.0, 4.1. latest...
• all ENVs are present in container
• malformed, e.g. RAIS_SCHEMEMAP=test=s3://test-iiif other=s3//xxx throws expected error, so it is proceeded

and as I understood, the nonempty SchemeMap is enough to configure RAIS to use a S3 source for the matched scheme..?

thank you in advance
Petr

[jechols]

After a bit of digging into our s3demo, I found that the S3 connectivity is fine... which was confusing for a bit, until I realized your issue is with how you request the URLs.

First, the scheme map is unnecessary in terms of making S3 work - you can just use the "s3" scheme and it's fine. But second: *the IIIF id must be a URI formatted as <scheme>://<resource>* when you aren't using the base file://default. This is technically a misuse of a URI (we should really allow:`, but it's an okay way to make it very clear we're using a non-default identifier.

To your problem: http://localhost:8080/iiif/test/TEST_000022_8.jp2/full/max/0/default.jpg, with RAIS listening on http://localhost:8080/iiif, is requesting the id test/TEST_000022_8.jp2. Since that's just a path with no scheme, and no ://, RAIS uses the default file://<tile dir>, which you see in the logs. To use test as a scheme in a RAIS id, you just need your ID to be test://TEST_000022_8.jp2 instead.

This is all a very long-winded way to say http://localhost:8080/iiif/test://TEST_000022_8.jp2/full/max/0/default.jpg should work where your other URL doesn't.

(Extra info is here to help me in the future, FYI, since I don't do a ton of RAIS support 😁)

[krkabol]

thank you so much @jechols for your help — it works perfectly now!
Since I have only little experience with IIIF, I didn’t realize the difference between the actual file name and the IIIF ID.
If the software itself runs as fast as the support I’ve just received, it’s truly a dream tool!

Best regards,
Petr

PS maybe I should rename the topic to be more relevant for other newbies? - something "Request for image from S3 ends up at the file store, ignoring SchemeMap?" - this is how I felt before your explanation..