Posted On: Nov 23, 2021

Now you can examine whether or not a configuration change would require a blue/inexperienced deployment from the Amazon OpenSearch Service (successor to Amazon Elasticsearch Service) console or utilizing the Amazon OpenSearch Service APIs. With this new possibility, you’ll be able to plan and make configuration adjustments that require a blue/inexperienced deployment when your cluster just isn’t at its peak visitors.

Beforehand, you needed to rely on documentation to determine whether or not a change would require a blue/inexperienced deployment, and even then in sure situations, it was not utterly deterministic. Now, while you make a configuration change utilizing the Amazon OpenSearch Service console, you should utilize the ‘Run Evaluation’ choice to examine whether or not the change would require a blue/inexperienced deployment earlier than you really make the change. Relying on whether or not the configuration change requires a blue/inexperienced deployment, you’ll be able to plan to make the change at a time when the cluster just isn’t experiencing its peak visitors, serving to you keep away from any disruptions or latency throughout a blue/inexperienced deployment in your customers. You can too examine whether or not a change would require a blue/inexperienced deployment by means of the configuration APIs through the use of the brand new ‘DryRun’ parameter when calling UpdateDomainConfig API.

The brand new blue/inexperienced examine is on the market throughout 23 areas globally. Please check with the AWS Area Desk for extra details about Amazon OpenSearch Service availability.

For extra details about this function, please see the documentation. To be taught extra about Amazon OpenSearch Service, please go to the product web page.