Issue:

All S3 operations (ListObjects, PutObject, GetObject with presigned URLs) return AccessDenied when

using Railway Object Storage credentials, even from within a Railway-deployed service.

What I've tried:

• Created two separate buckets — both have the same issue
• Reset credentials on the first bucket — no change
• Tested from inside the Railway container using a direct Node.js script with the minio-js SDK — still Access Denied
• Tried both endpoints: t3.storageapi.dev and storage.railway.app
• Tried multiple regions: ams and auto
• Tried with and without pathStyle: true
• Verified env vars resolve correctly inside the container (ACCESS_KEY_ID, SECRET_ACCESS_KEY, BUCKET, REGION all present)

Reproduction (run inside Railway container):

node -e "
const Minio = require('minio');
const c = new Minio.Client({
endPoint: 't3.storageapi.dev',
useSSL: true,
accessKey: process.env.MINIO_ACCESS_KEY,
secretKey: process.env.MINIO_SECRET_KEY,
region: process.env.MINIO_REGION
});
c.listObjects(process.env.MINIO_BUCKET, '', true)
.on('data', d => console.log('OK:', d.name))
.on('error', e => console.log('ERR:', e.code, e.message));
"

Result: ERR: AccessDenied Access Denied.

Environment:

• minio-js SDK version: 8.0.6

This is maybe unrelated but the issue appeared when I switched to Pro plan