Change domain to datasets-server.huggingface.co
- [x] create the domain and point to the load balancer. See https://github.com/huggingface/infra/pull/205 and https://github.com/huggingface/infra/pull/209. Check at https://www.whatsmydns.net/#A/datasets-server.huggingface.co
- [x] use the domain in the ingress: see #328 
- [x] change the TLS certificate to accept both domains. The TLS certificates must be created manually at https://us-east-1.console.aws.amazon.com/acm/home?region=us-east-1#/certificates/list.
  - [x] created at https://us-east-1.console.aws.amazon.com/acm/home?region=us-east-1#/certificates/bfcad79a-111b-4852-adc2-5d78f4132eb6.
  - [x] use the certificate in the ingress: https://github.com/huggingface/datasets-server/pull/331
- [x] change in betteruptime.com (also created the "Datasets server" escalation policy, using the same model as the "Tensorboard" one)
- [x] point directly to the new domain from moon-landing: see https://github.com/huggingface/moon-landing/pull/3119
  - [x] to get the config, splits and rows: https://github.com/huggingface/moon-landing/blob/ef4d36bc7e7da25f3c873c324e0bcabffca8e4f9/server/.env.production.example#L40
  - [x] to get the assets: https://github.com/huggingface/moon-landing/blob/ef4d36bc7e7da25f3c873c324e0bcabffca8e4f9/server/.env.production.example#L41
  - [x] We still get queries to the old domain from the hub [kibana](https://kibana.elastic.huggingface.tech/app/discover#/?_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:now-15m,to:now))&_a=(columns:!(),filters:!(),index:'24d42510-a44e-11ec-bb45-ad141ad1c5f8',interval:auto,query:(language:kuery,query:'kubernetes.container.name%20:%20%22datasets-server-reverse-proxy%22%20and%20message%20:%20%22datasets-server.huggingface.tech%2Fvalid%22'),sort:!(!('@timestamp',desc)))) - the PR ephemeral environments are still using the old domain -> [nevermind](https://github.com/huggingface/datasets-server/issues/319#issuecomment-1147145154)
- [x] change in autonlp-ui: https://github.com/huggingface/autonlp-ui/blob/ac85c029a58fdd25c8f810cbba8a3d8ecbba6181/src/lib/config.ts#L58. See https://github.com/huggingface/autonlp-ui/pull/270
- [x] change it in the Hub webhook, asked on [Slack](https://huggingface.slack.com/archives/C023JAKTR2P/p1654175138985519)
- [x] remove the domain datasets-server.huggingface.tech from the current project (https://github.com/huggingface/datasets-server) - see https://github.com/huggingface/datasets-server/pull/351
- [x] remove the proxy: https://github.com/huggingface/conf/blob/bd698a91c615938b52477c25d72ba84d10af4c68/moonrise/nginx-moonrise.conf#L321-L328 - see https://github.com/huggingface/conf/pull/173

Should we apply these two tasks, or keep the domain + certificate for further use (admin)? (edit: from @XciD : yes, let's manage everything on the same domain)
- [x] revoke the certificate https://us-east-1.console.aws.amazon.com/acm/home?region=us-east-1#/certificates/321c89f0-1267-4519-b3cf-547738e3340e
- [x] remove the domain datasets-server.huggingface.tech from https://github.com/huggingface/infra -> see https://github.com/huggingface/infra/pull/228
- [x] replace the certificate https://us-east-1.console.aws.amazon.com/acm/home?region=us-east-1#/certificates/bfcad79a-111b-4852-adc2-5d78f4132eb6 with a new one without datasets-server.huggingface.tech in the alternate names
  - [x] certificate has been created: https://us-east-1.console.aws.amazon.com/acm/home?region=us-east-1#/certificates/777e3ae5-0c54-47ee-9b8c-d85eeb6ec4ae
  - [x] use the new certificate - https://github.com/huggingface/datasets-server/pull/360
  - [x] delete the old certificate https://us-east-1.console.aws.amazon.com/acm/home?region=us-east-1#/certificates/bfcad79a-111b-4852-adc2-5d78f4132eb6
Change domain to datasets-server.huggingface.co: - [x] create the domain and point to the load balancer. See https://github.com/huggingface/infra/pull/205 and https://github.com/huggingface/infra/pull/209. Check at https://www.whatsmydns.net/#A/datasets-server.huggingface.co
- [x] use the domain in the ingress: see #328 
- [x] change the TLS certificate to accept both domains. The TLS certificates must be created manually at https://us-east-1.console.aws.amazon.com/acm/home?region=us-east-1#/certificates/list.
  - [x] created at https://us-east-1.console.aws.amazon.com/acm/home?region=us-east-1#/certificates/bfcad79a-111b-4852-adc2-5d78f4132eb6.
  - [x] use the certificate in the ingress: https://github.com/huggingface/datasets-server/pull/331
- [x] change in betteruptime.com (also created the "Datasets server" escalation policy, using the same model as the "Tensorboard" one)
- [x] point directly to the new domain from moon-landing: see https://github.com/huggingface/moon-landing/pull/3119
  - [x] to get the config, splits and rows: https://github.com/huggingface/moon-landing/blob/ef4d36bc7e7da25f3c873c324e0bcabffca8e4f9/server/.env.production.example#L40
  - [x] to get the assets: https://github.com/huggingface/moon-landing/blob/ef4d36bc7e7da25f3c873c324e0bcabffca8e4f9/server/.env.production.example#L41
  - [x] We still get queries to the old domain from the hub [kibana](https://kibana.elastic.huggingface.tech/app/discover#/?_g=(filters:!(),refreshInterval:(pause:!t,value:0),time:(from:now-15m,to:now))&_a=(columns:!(),filters:!(),index:'24d42510-a44e-11ec-bb45-ad141ad1c5f8',interval:auto,query:(language:kuery,query:'kubernetes.container.name%20:%20%22datasets-server-reverse-proxy%22%20and%20message%20:%20%22datasets-server.huggingface.tech%2Fvalid%22'),sort:!(!('@timestamp',desc)))) - the PR ephemeral environments are still using the old domain -> [nevermind](https://github.com/huggingface/datasets-server/issues/319#issuecomment-1147145154)
- [x] change in autonlp-ui: https://github.com/huggingface/autonlp-ui/blob/ac85c029a58fdd25c8f810cbba8a3d8ecbba6181/src/lib/config.ts#L58. See https://github.com/huggingface/autonlp-ui/pull/270
- [x] change it in the Hub webhook, asked on [Slack](https://huggingface.slack.com/archives/C023JAKTR2P/p1654175138985519)
- [x] remove the domain datasets-server.huggingface.tech from the current project (https://github.com/huggingface/datasets-server) - see https://github.com/huggingface/datasets-server/pull/351
- [x] remove the proxy: https://github.com/huggingface/conf/blob/bd698a91c615938b52477c25d72ba84d10af4c68/moonrise/nginx-moonrise.conf#L321-L328 - see https://github.com/huggingface/conf/pull/173

Should we apply these two tasks, or keep the domain + certificate for further use (admin)? (edit: from @XciD : yes, let's manage everything on the same domain)
- [x] revoke the certificate https://us-east-1.console.aws.amazon.com/acm/home?region=us-east-1#/certificates/321c89f0-1267-4519-b3cf-547738e3340e
- [x] remove the domain datasets-server.huggingface.tech from https://github.com/huggingface/infra -> see https://github.com/huggingface/infra/pull/228
- [x] replace the certificate https://us-east-1.console.aws.amazon.com/acm/home?region=us-east-1#/certificates/bfcad79a-111b-4852-adc2-5d78f4132eb6 with a new one without datasets-server.huggingface.tech in the alternate names
  - [x] certificate has been created: https://us-east-1.console.aws.amazon.com/acm/home?region=us-east-1#/certificates/777e3ae5-0c54-47ee-9b8c-d85eeb6ec4ae
  - [x] use the new certificate - https://github.com/huggingface/datasets-server/pull/360
  - [x] delete the old certificate https://us-east-1.console.aws.amazon.com/acm/home?region=us-east-1#/certificates/bfcad79a-111b-4852-adc2-5d78f4132eb6