Is it possible to set the CORS policy for a bucket. I am trying to use the s3-cli, but the s3api functions seem to be disabled. Is this the case?
I am interested in using the OSN to host assets that are used on an online viewer, but am getting CORS policy errors. The header has an aws prefix (x-amz-meta-access-control-allow-origin) as shown by a curl response
Running the following command issues an accessDenied error
aws s3api get-bucket-cors --bucket intensity01 --profile Intensity01 --endpoint-url https://ncsa.osn.xsede.org
Is this possible, or am I on the wrong track
Hey Brandon,
So out of the box, OSN does not support CORS and we do not allow end users to set bucket policies. OSN is run on mostly volunteer effort and, as such, we really reduce the feature set that we support. As designed, OSN was originally intended to “just” support data sharing. We have seen quite a few users (and now organizations buying their own storage clusters that we support) who are interested in using OSN as the storage backend for a CI service, and while we try to accommodate them, I can’t make a promise.
Please submit an OSN help request by sending an email to help@osn.mghpcc.org and tell us about your use case, the software you will be using, and the bucket policies that need to be supported. The more information you can provide us the better. I’ll add this to the agenda for our next OSN sysadmin meeting, which will occur on Tuesday. I’ll follow up on the ticket after I discuss it with the team.
