Victor Ekpo

@carlhopf had been searching for hours and your solution fixed everything, yes they should add this to the package for sure!

Maybe you could do a deployment with multiple containers that all render to one source, then you load the data from your application?

Thank you @Xtansia, I did notice that the cluster name does come back when I use a regular Apache HTTP client with a request interceptor, it returns the ClusterResponse accordingly....

@Xtansia yes, it returns correctly when not using AwsSdk2Transport, the error is specific to using that transport.

@Xtansia Let me know if you need the full stack trace, when I tested locally I saw that AwsSdk2Transport tries to decode the response and it fails, here is part...

Sure With the AWS Sdk2 Transport ``` @Bean public OpenSearchClient openSearchJavaClient() throws Exception { LOGGER.info("Initializing Java client for AWS OpenSearch"); if (StringUtils.isBlank(url)) { LOGGER.info("Configuring AWS OpenSearch Java Client by resolving...

Sorry for the late reply on this, for some reason im not seeing my notifications. @Xtansia , we are on the latest version of Opensearch for the cluster, which is...

any update on this? I also have a Mock Integration I would like to test locally and it seems this is a current limitation in the SAM CLI local command