Configuring S3 API endpoint domain names

To support S3 virtual hosted-style requests, you must configure the list of endpoint domain names that S3 clients will be connecting to.

Before you begin

You must be signed in to the Grid Manager using a supported browser.
You must have specific access permissions. For details, see information about controlling system access with administration user accounts and groups.
You must have confirmed that a grid upgrade is not in progress.
Warning: Do not make any changes to the domain name configuration when a grid upgrade is in progress.

About this task

You configure API endpoint domain names after you create the fully-qualified domain names on the DNS server, depending on the grid nodes that S3 clients will be connecting to:

If S3 clients are connecting to one or more API Gateway Nodes, you must include the domain name of each API Gateway Node.
If S3 clients are connecting to one or more Storage Nodes, you must include the domain name of each Storage Node.
If S3 clients are connecting through an external load balancer, you must include the domain name of the load balancer.

Steps

Select Configuration > Domain Names.
The Endpoint Domain Names page appears.
Using the (+) icon to add additional fields, enter the list of S3 API endpoint domain names in the Endpoint fields.
If this list is empty, support for S3 virtual hosted-style requests is disabled.
Click Save.
Obtain a custom server certificate with the wildcard Subject Alternative Name (SAN) for the endpoint domain name, the endpoint domain name, and any other domain names that must be supported.
This step is required to validate the SSL certificate and to verify the hostname when API client applications connect to the endpoint.

Example
If the endpoint is s3.company.com, obtain a custom server certificate that includes the s3.company.com endpoint and the endpoint's wildcard SAN: *.s3.company.com.
Select Configuration > Server Certificates. Then, install the custom certificate in the Object Storage API Service Endpoints Server Certificate section.
Confirm that the DNS server also supports the endpoint and the wildcard SAN.
Now, when the endpoint bucket.s3.company.com is used, the DNS server resolves to the correct endpoint and the certificate authenticates the endpoint as expected.