In order to request a change to search.max_open_scroll_context in Amazon Opensearch, you will need to contact AWS premium support team. Setting the scroll value to higher value is not recommended in general as Scroll API also keeps a track of deleted or updated documents hence increasing the heap memory and disk usage. Hence, the limit of 500 is a safety net defined by the ElasticSearch to avoid any negative impacts on heap memory and disk usage.
That being said, because of managed nature of Amazon Opensearch service this setting can only be changed by opensearch internal team. If you would still like to go ahead and increase this setting, reach out to AWS support team via a support ticket with a specific value you would like it to be increased to.
Note: Please note that this setting will set back to default value (500) when the blue/green deployment is triggered due to a configuration change like version upgrade, changing instance type etc.
Impact to AWS Elasticsearch on the licensing change of Elasticsearch(elastic.co)Accepted Answerasked 2 years ago
Unable to change 'max_buckets' cluster settingasked 2 years ago
How to change parameter partial_revokesAccepted Answerasked 10 months ago
Bug report: cannot move AWS::Elasticsearch::Domain resource to a new VPCasked 7 months ago
Change cluster parameter groupAccepted Answerasked 3 years ago
Logging with CloudWatch vs. ElasticSearch/KibanaAccepted Answerasked 5 years ago
ElasticSearch version change gets stuck in Amazon OpenSearch Serviceasked 4 months ago
AWS Elasticsearch Option to store fields without indexing it.Accepted Answerasked 3 years ago
Change ElasticSearch search.max_open_scroll_contextAccepted Answerasked 8 months ago
pagination question on appsync to elasticsearchAccepted Answerasked 3 years ago