Workflow

The high-level workflow of the Static Website Hosting feature is as follows:

• An Operator enables the Static Website Hosting feature on the Vault.
• An Operator configures the Static Website Virtual Host Suffix in the AccessPools, which are deployed to the Vaults which have the feature enabled.
• An Operator configures their DNS servers to perform proper routing of static website virtual host style addresses to the appropriate Accesser node or Load Balancer IP address.
• A User adds the Website Configuration Policy to any or all buckets that have the Static Website Hosting feature enabled.
• A User accesses the objects in the COS buckets with Static Website Hosting via READ requests (HEAD/GET) of the Objects by using virtual host-based addressing requests sent to the Static Website Virtual Host Suffix.
  • For example, if the Static Website Virtual Host Suffix is static-website.example.com, then to access the static website for the COS bucket named ‘bucketname’, use http://bucketname.static-website.example.com/