# MinIO AWS Region Error When Connecting via NocoDB UI (v0.258.11) **URL:** \ **Category:** Self-Host\ **Created:** [July 7, 2025, 2:56pm UTC](https://community.nocodb.com/t/minio-aws-region-error-when-connecting-via-nocodb-ui-v0-258-11/1990 "2025-07-07T14:56:08Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![devika](https://avatars.discourse-cdn.com/v4/letter/d/a587f6/32.png) [@devika](https://community.nocodb.com/u/devika)\ **Post date:** [July 7, 2025, 2:56pm UTC](https://community.nocodb.com/t/minio-aws-region-error-when-connecting-via-nocodb-ui-v0-258-11/1990/1 "2025-07-07T14:56:08Z")
Hi Team, I am trying to configure MinIO as an S3-compatible storage backend for NocoDB (version 0.258.11). MinIO is accessible from the pod, and connections are working when tested directly. However, when I try to perform operations through the NocoDB UI, I receive an error related to the AWS region. **Details:** - MinIO endpoint is accessible from within the pod. - S3 connection tests (e.g., using `mc` `) are successful. - The error only appears when using the NocoDB UI. - My configuration in values.yaml is as follows: - `NC_S3_ENDPOINT: "https://minio.qainfra.vite"` - `NC_S3_BUCKET: "nocodb"` - `NC_S3_ACCESS_KEY` and `NC_S3_ACCESS_SECRET` are set correctly. - `NC_S3_FORCE_PATH_STYLE: "true"` - `NC_S3_SSL: "true"` **Questions / Request for Help:** 1. Is there a specific AWS region value required for MinIO integration with NocoDB? 2. Are there any additional environment variables or configuration options I should set for MinIO compatibility? 3. Has anyone faced a similar issue or have suggestions for troubleshooting this error? Any help or suggestions would be appreciated! ![image](https://canada1.discourse-cdn.com/flex011/uploads/nocodb/original/1X/7eb0a43aad19c8eb323a83e8057b563875d624bb.png) `Error uploading file S3Error: Access Denied.` ` at parseError (/usr/src/app/node_modules/minio/dist/main/internal/xml-parser.js:57:13)` ` at Object.parseResponseError (/usr/src/app/node_modules/minio/dist/main/internal/xml-parser.js:104:11)` ` at process.processTicksAndRejections (node:internal/process/task_queues:105:5)` ` at async Client.makeRequestStreamAsync (/usr/src/app/node_modules/minio/dist/main/internal/client.js:514:19)` ` at async Client.listIncompleteUploadsQuery (/usr/src/app/node_modules/minio/dist/main/internal/client.js:1077:17)` ` at async Client.findUploadId (/usr/src/app/node_modules/minio/dist/main/internal/client.js:1143:22)` ` at async Client.uploadStream (/usr/src/app/node_modules/minio/dist/main/internal/client.js:1430:30)` ` at async Minio.upload (/usr/src/app/docker/main.js:2120:221616)` ` at async Minio.fileCreateByStream (/usr/src/app/docker/main.js:2120:221148)` ` at async Minio.test (/usr/src/app/docker/main.js:2120:220528) {` ` code: 'AccessDenied',` ` bucketname: 'nocodb',` ` resource: '/nocodb',` ` requestid: '184FFE3A8FF8817F',` ` hostid: 'f4a0adf2-2e92-443b-8917-3bb35ad328e6',` ` amzRequestid: '184FFE3A8FF8817F',` ` amzId2: undefined,` ` amzBucketRegion: undefined` `}` `[Nest] 9 - 07/07/2025, 2:25:07 PM ERROR [MissingDBError] S3Error: Access Denied.` `[Nest] 9 - 07/07/2025, 2:25:07 PM ERROR [GlobalExceptionFilter] Access Denied.` `S3Error: Access Denied.` ` at parseError (/usr/src/app/node_modules/minio/dist/main/internal/xml-parser.js:57:13)` ` at Object.parseResponseError (/usr/src/app/node_modules/minio/dist/main/internal/xml-parser.js:104:11)` ` at process.processTicksAndRejections (node:internal/process/task_queues:105:5)` ` at async Client.makeRequestStreamAsync (/usr/src/app/node_modules/minio/dist/main/internal/client.js:514:19)` ` at async Client.listIncompleteUploadsQuery (/usr/src/app/node_modules/minio/dist/main/internal/client.js:1077:17)` ` at async Client.findUploadId (/usr/src/app/node_modules/minio/dist/main/internal/client.js:1143:22)` ` at async Client.uploadStream (/usr/src/app/node_modules/minio/dist/main/internal/client.js:1430:30)` ` at async Minio.upload (/usr/src/app/docker/main.js:2120:221616)` ` at async Minio.fileCreateByStream (/usr/src/app/docker/main.js:2120:221148)` ` at async Minio.test (/usr/src/app/docker/main.js:2120:220528)` ---
**Author:** ![Navi](https://avatars.discourse-cdn.com/v4/letter/n/3be4f8/32.png) [@Navi](https://community.nocodb.com/u/Navi)\ **Post date:** [July 7, 2025, 3:01pm UTC](https://community.nocodb.com/t/minio-aws-region-error-when-connecting-via-nocodb-ui-v0-258-11/1990/2 "2025-07-07T15:01:39Z")
It is very hard to match all the variations from 3rd party providers. If you help debug from [code](https://github.com/nocodb/nocodb) and help suggest solution it would be awesome. ---
**Author:** ![devika](https://avatars.discourse-cdn.com/v4/letter/d/a587f6/32.png) [@devika](https://community.nocodb.com/u/devika)\ **Post date:** [July 8, 2025, 11:04am UTC](https://community.nocodb.com/t/minio-aws-region-error-when-connecting-via-nocodb-ui-v0-258-11/1990/3 "2025-07-08T11:04:51Z")
Hi @Navi , This bug has been fixed in the recent release. I am able to connect to minio now.