# שגיאה בבנייה מחדש באמצעות minio כאחסון אובייקטים

**URL:** <https://meta.discourse.org/t/error-in-rebuilding-using-minio-as-object-store/237776>\
**Category:** Product Support\
**Created:** [1 בספטמבר,‏ 2022,‏ 1:01am UTC](https://meta.discourse.org/t/error-in-rebuilding-using-minio-as-object-store/237776 "2022-09-01T01:01:48Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![teward](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/teward/32/148702_2.png) [@teward](https://meta.discourse.org/u/teward)\
**Post date:** [4 בספטמבר,‏ 2022,‏ 1:11am UTC](https://meta.discourse.org/t/error-in-rebuilding-using-minio-as-object-store/237776/10 "2022-09-04T01:11:27Z")

</div>

No, MinIO does not support PutObjectAcl. It supports bucket level permissions but not _object_ level ACLs in that form of the API.

MinIO does NOT support the full AWS API. See [https://docs.min.io/minio/baremetal/security/minio-identity-management/policy-based-access-control.html](https://docs.min.io/minio/baremetal/security/minio-identity-management/policy-based-access-control.html) for the fully supported API set.

MINIO\_DOMAIN needs added for DNS style buckets to happen, which is why the invalid PUT happens. Once we get further we see the failures in the XML against what is allowed in the schemas. Make sure you NEVER put any policy in place that has variables not supported in the supported set that MinIO actually supports.

Remember: S3-compatible does NOT mean it’s a 100% match for all supported AWS S3 API variables/endpoints/values.

---

_[View the full topic](https://meta.discourse.org/t/error-in-rebuilding-using-minio-as-object-store/237776)._