S3 Minio Error (400)

Hi!
I see that support for custom URL Allow to specify S3 Endpoint URL to allow usage of S3 compatible services · Issue #794 · n8n-io/n8n · GitHub has been added for S3 storage beyond AWS.
I am using MINIO.
I am having a problem with any access to S3.

Error:

Error: AWS error response [400]: 400 - "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<Error><Code>BadRequest</Code><Message>An error occurred when parsing the HTTP request PUT at &#39;/&#39;</Message><Resource>/</Resource><Region>custom_region</Region><RequestId></RequestId><HostId>0b2169a8-9a1d-490e-aa40-dfad67874880</HostId></Error>"
    at Object.awsApiRequest (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Aws/S3/GenericFunctions.js:39:15)
    at processTicksAndRejections (internal/process/task_queues.js:93:5)
    at async Object.awsApiRequestSOAP (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Aws/S3/GenericFunctions.js:54:22)
    at async Object.execute (/usr/local/lib/node_modules/n8n/node_modules/n8n-nodes-base/dist/nodes/Aws/S3/AwsS3.node.js:117:36)
    at async /usr/local/lib/node_modules/n8n/node_modules/n8n-core/dist/src/WorkflowExecute.js:416:47

Credentials:

If you want to connect to none AWS S3 then you should not use the “AWS S3” node. That node is only meant to be used in combination with AWS. What you want to use instead is the generic “S3” node. There you can then set the S3 Endpoint to https://play.min.io:9000 and leave Region empty. The Access Key Id and Secret Access Key can then be set accordingly. It should then work fine.

Thank you, it helped.

Glad to hear. Have fun!