Elastic Search managed ignores X-Opaque-id header

Elastic Search managed ignores X-Opaque-id header Elastic Search docs mentions with the use of an X-Opaque-id in the requests we can track the queries. The X-Opaque-id header should be forwarded in the response. However this doesn't work with AWS managed Elastic Search

to aws elasticsearch:

curl -i --http1.1 -H 'X-Opaque-Id: 12345'  "http://aws_elastic_sarch_url/_cat/health"
HTTP/1.1 200 OK
Date: Wed, 03 Aug 2022 07:56:35 GMT
Content-Type: text/plain;charset=UTF-8
Content-Length: 100
Connection: keep-alive
Access-Control-Allow-Origin: *
1659513395 07:56:35 aws-elasticsearch green 7 4 true 7976 3978 0 0 0 0 - 100.0%

to raw elasticsearch:

curl -i --http1.1 -H 'X-Opaque-Id: 12345'  "http://raw_elastic_sarch_url/_cat/health"
HTTP/1.1 200 OK
X-Opaque-Id: 12345
content-type: text/plain; charset=UTF-8
content-length: 66
1659516213 08:43:33 docker-cluster green 1 1 0 0 0 0 0 0 - 100.0%

Any solutions for using X-opaque-id headers with AWS ElasticSearch?