No, you don't.

The AGPL Section 13 only requires you to publish the sourcecode of an AGPL-licensed program if you "modify the program". When you host an AGPL-licensed software as-is, then you have no further obligations.

And even if you were modifying min.io, that provision only applies to "users interacting with it remotely through a computer network". But your users are not interacting with min.io. They are interacting with your CMMS which then interacts with min.io. So you do not need to give your sourcecode to your users.

And even if you were modifying min.io and if your users were interacting with min.io directly, you still would only need to open-source your modifications to min.io, not your own application. Two applications communicating with each other via webservices well-satisfied the "at arms length" definition of when two interacting programs do not count as a combined work according to the GPL.

No, you don't.

The AGPL Section 13 only requires you to publish the sourcecode of an AGPL-licensed program if you "modify the program". When you host an AGPL-licensed software as-is, then you have no further obligations.

And even if you were modifying min.io, that provision only applies to "users interacting with it remotely through a computer network". But your users are not interacting with min.io. They are interacting with your CMMS which then interacts with min.io. So you do not need to give your sourcecode to your users.

And even if you were modifying min.io and if your users were interacting with min.io directly, you still would only need to open-source your modifications to min.io, not your own application. Two applications communicating with each other via webservices well-satisfied the "communicating at arms length" definition of when two interacting programs do not count as a combined work according to the GPL.