Hi everyone, I’m deploying an AWS OpenSearch domain, alongside my old AWS ElasticSearch, and there’s one very important difference in how the domain name works: for ES, a unique suffix is appended to the domain, but for OS, it’s not 😮
Is this a bug, or is this how it’s supposed to be?
If it’s expected, then how can we elegantly handle uniqueness across dozens of deployments? 🤔
This is how the OpenSearch domain is configured. For some reason, the
config key is required (unlike in all other resources):
Are you asking why there's a random suffix? Or why there isn't one?
06/25/2022, 4:24 PM
Why there isn’t one. ElasticSearch has one, which is great (we got used to this commodity of not having to worry about uniqueness of resources). But OpenSearch resource doesn’t generate one, which is an issue.
06/25/2022, 4:34 PM
Got it, you can create one using the random provider and append it to the name as a workaround, but could you cut an issue for this so we can add the randomness back in the provider?