If you create a 'custom endpoint alias' as described here, how long will the existing, original, random URL endpoints keep working for?
For example with an existing Elastic Cloud deployment with Deployment ID
Stringwith32randomHexCharacters which currently has:
- Elasticsearch endpoint URL: https://Stringwith32randomHexCharacters.region.aws.found.io
- Kibana endpoint URL: https://Adifferent32randomHexCharacters.region.aws.found.io:9243
if you then click 'Create an alias' and type for example 'mydeployment' it lists your new URLs such as:
- Elasticsearch endpoint URL: https://mydeployment.es.region.aws.found.io
- Kibana endpoint URL: https://mydeployment.kb.region.aws.found.io:9243
but makes no reference to whether (and for how long) the existing URLs will continue to work. The name 'alias' suggests that the original should last for ever, but this isn't clear and the consequences are quite significant.
These old release notes say:
They don’t replace the existing URL, but work alongside it
which sounds promising - does that mean the existing URLs will continue to work indefinitely?
If so it would be helpful if the official documentation & also the https://cloud.elastic.co UI made this clear.
If the original URL does not last indefinitely, this is a big deal due to the volume of references to the existing URLs for example in internal ticketing systems / documentation, user bookmarks, etc.
Many thanks in advance.