...
For the object store at UAMS, each HPC user who requests personal space in the object store is given their own Namespace tied to their account on Grace. When referencing their account on Grace the HPC user must append "@hpc.uams.edu" to their Grace username. In other words, the name of HPC user's personal Namespace in the object store is their HPC username (the same as their home directory name on Grace), and the sole Object User within that namespace is identified as username@hpc.uams.edu.
...
Departments, labs, or other entities may arrange to have shared Namespaces in the object store. The department, lab, or other entity designates one or more persons to manage that Namespace. These Namespace Administrators would access the ECS management GUI using their UAMS credentials in the form of "username@uams.edu" (i.e. not their HPC credentials). Note that each UAMS user can only be the Namespace Administrator of one shared Namespace (not counting the user's personal Namespace tied to their HPC account on Grace). From the management GUI the Namespace Administrators can either add ACLs to Buckets or Objects to allow users to access data in the Namespace, or can create local Object Users (Object Users who are not tied to any particular domain) within the Namespace.
We are working with UAMS IT to get more user friendly addressing options. For the moment, we only allow for path-based addressing of the object store, and depend on the HTTPS ports outlined in the ECS Data Access Guide. Only the HTTPS protocols are allowed. For example, to access a Bucket named "foo" using the S3 protocol the URL would be https://uamsecs1.ad.uams.edu:9021/foo. If the bucket is not in the Object User's namespace, the RESTful call must also include x-emc-namespace in the HTTPS header.
...