## This is now possible with [Static websites on Azure Storage][1]

### Creating a Static Website

1. Navigate to your storage account
2. Select Static Website from the blade and toggle to "enabled"

  [![Add Static Website][2]][2]

3. Once you save, this will create a URL endpoint and also a bucket named `$web` to host your files

   [![Static Endpoint][3]][3]

4. Go to your `$web` storage container and upload any files you want

### Add CDN / Custom Domain

1. Navigate to your CDN Profile and either Create / Edit your Endpoint
2. Select 'Custom Origin' and use the 'Origin Hostname' that was created for your static site

   [![Custom Origin CDN][4]][4]

3. Give Azure up to 30 minutes to propagate all the settings

### Further Reading

* [Tutorial: Host a static website on Blob Storage][5]
* [Tutorial: Use Azure CDN to enable a custom domain with SSL for a static website][6]

  [1]: https://azure.microsoft.com/en-us/blog/static-websites-on-azure-storage-now-generally-available/
  [2]: https://i.stack.imgur.com/qdy7V.png
  [3]: https://i.stack.imgur.com/i1cMA.png
  [4]: https://i.stack.imgur.com/7j6S6.png
  [5]: https://learn.microsoft.com/en-us/azure/storage/blobs/storage-blob-static-website-host
  [6]: https://learn.microsoft.com/en-us/azure/storage/blobs/storage-blob-static-website-custom-domain

I have now successfully setup my static website in a CDN, 
Is there a way to specify that index.html is the default document ?
It is a 1 page site I just would like to browse to the root url without having to type /index.html .. 

Thank you

Azure CDN default document index.html

You can add any ACM certificate you have to a listener, after all this load balancer is a CNAME and would be resolved to your hostname(s) via a DNS record.

However for any ACM certificate you have to be able to verify that you control that domain. As the load balancers domain is owned by Amazon you cannot verify this domain. If you attempt to access the load balancers CNAME directly in the browser it will show as insecure (as the SSL will not be valid for that domain), you will however be able to verify HTTPS works.

The only solution to have a valid HTTPS endpoint will be to use an ACM certificate for a domain you own, and resolve it via that domain name rather than the load balancers CNAME.

I have an Application Load Balancer (ALB) that uses the [default DNS name][1] provided by AWS.  

i.e. name of `my-loadbalancer` in US East is given the DNS name:

`my-loadbalancer-1234567890.us-east-1.elb.amazonaws.com`

[![basic configuration][2]][2]

I have a listener over HTTP that works just fine:

`http://my-loadbalancer-1234567890.us-east-1.elb.amazonaws.com/`

However, when I go to add an **HTTPS Listener**, I need to provide a certificate that matches the current domain.  I can pick something from my ACM store, but they're all for custom domains

[![HTTPS Listener][3]][3]

I can [request a new certificate][4], but not sure how I'd be able to validate against `***.us-east-1.elb.amazonaws.com`

This is a backend service, so I don't need a user friendly domain.

Is there anyway to add HTTPS to a load balancer out of the box?

  [1]: https://docs.aws.amazon.com/elasticloadbalancing/latest/classic/using-domain-names-with-elb.html
  [2]: https://i.stack.imgur.com/b4SOU.png
  [3]: https://i.stack.imgur.com/iSaaP.png
  [4]: https://console.aws.amazon.com/acm/home?region=us-east-1#/wizard/