Amazon OpenSearch Service Gets Warnings for Risky Config Changes: Meet Validation Advisory!
Hi everyone, Shii-chan here! I found an update that makes running Amazon OpenSearch Service a little less stressful, and I'm so excited to share it!
AWS What's NewWhat was announced?
In AWS What's New, Amazon OpenSearch Service introduced validation advisory. When you change a domain configuration, each validation result is now classified into one of two types:
- Critical: blocks the change, just like before
- Warning: advisory guidance. You can acknowledge it and proceed
The story so far
Until now, validation results were limited to pass or block.
That meant there was no way to flag changes that would succeed but still carry risk. Since they succeeded, you could miss the risk and run into trouble later.
What changes
You can now find potential issues without blocking your deployments! The source gives these two examples of warnings:
- Dedicated coordinator nodes that may be too small for the data node configuration
- A shard count that exceeds the recommended limit for the cluster
If you operate domains, you can see "this will work, but it might be risky" changes ahead of time and decide for yourself whether to go ahead.
Dive Deep
Here is where you can work with warnings, according to the source:
- Acknowledge warnings when you first submit a change
- Review severity in dry-run results before applying a change
- Set acknowledgments directly in AWS CloudFormation templates
- See severity in API responses and Amazon EventBridge notifications
It supports domains running either OpenSearch or Elasticsearch versions, and it is available in all AWS Regions where Amazon OpenSearch Service is available.
Wrap-up
- Validation results are now Critical (blocks) or Warning (acknowledge and proceed)
- You can notice risky changes that would otherwise succeed silently
- Severity is available in dry-run, CloudFormation, the API, and EventBridge
- All OpenSearch and Elasticsearch versions and all supported Regions are covered
This is a great fit if you run OpenSearch Service domains and push configuration changes through IaC or automation!