ECS 3.5.0.1 Administration Guide

Bucket and namespace addressing

When an S3 compatible application makes an API request to perform an operation on an ECS bucket, ECS can identify the bucket in several ways.

For authenticated API requests, ECS infers the namespace by using the namespace that the authenticated user is a member of. To support anonymous, unauthenticated requests that require CORS support or anonymous access to objects, you must include the namespace in the address so that ECS can identify the namespace for the request.

When the user scope is NAMESPACE, the same user ID can exist in multiple namespaces (for example, namespace1/user1 and namespace2/user1). Therefore, you must include the namespace in the address. ECS cannot infer the namespace from the user ID.

Namespace addresses require wildcard DNS entries (for example, *.ecs1.yourco.com) and also wildcard SSL certificates to match if you want to use HTTPS. Non-namespace addresses and path style addresses do not require wildcards since there is only one hostname for all traffic. If you use non-namespace addresses with virtual host style buckets, you will still need wildcard DNS entries and wildcard SSL certificates.

You can specify the namespace in the x-emc-namespace header of an HTTP request. ECS also supports extraction of the location from the host header.