AWS’s JavaScript SDK v3.1143.0 adds support for Amazon Bedrock Agentic Retrieve to use the Bedrock Mantle (OpenAI Responses) endpoint, alongside changes to OpenSearch, security tooling and other AWS services. For developers, the release is a useful bundle of new integration options, not just another version number looking for a home.
AWS AI Watch analysis
What happened
AWS published version 3.1143.0 on 29 September. Its release notes say Bedrock Agentic Retrieve can now use the Bedrock Mantle endpoint, with an optional project ID. The notes also cover advisory pre-validation for OpenSearch domain changes, new integrations for SecurityAgent and expanded SFTP server configuration.
Read the AWS SDK release notes.
Our top picks
- Bedrock Agentic Retrieve and the Responses endpoint
The SDK now supports this endpoint through a new MantleFoundationModel configuration, with an optional project ID. - OpenSearch pre-validation warnings
Non-critical checks can be acknowledged so changes can proceed instead of being blocked; severity also appears in progress and dry-run results. - SecurityAgent integrations
The SDK adds Azure DevOps and Bitbucket Data Center as integration providers. - More SFTP port choices
AWS Transfer Family supports up to three custom ports on public SFTP servers, with a choice of client-talk-first or server-talk-first communication. - Public endpoints for serverless Valkey
ElastiCache Serverless can be created with a public endpoint and no VPC configuration; AWS says these caches require IAM authentication.
Why it matters
The Bedrock change gives developers another route for connecting Agentic Retrieve to an endpoint that supports the OpenAI Responses API. Meanwhile, the OpenSearch warnings and expanded integration options show the SDK making room for more flexible workflows, including cases where a non-critical check should inform a decision rather than stop it outright.
Some of the release’s most consequential choices need careful handling. Publicly accessible cache endpoints and configurable SFTP ports offer flexibility, but operators will need to understand the access controls they are choosing. The notes describe the available settings, not their use in any particular deployment.
Our read
This is a worthwhile SDK release for AWS developers, especially teams working with Bedrock integrations or OpenSearch changes. The practical gain is choice: more endpoints and integrations, plus warnings that can be acknowledged when checks are non-critical. As ever, a new configuration option is not a deployment plan; check the service documentation and your own access requirements before switching things on.
What to watch
- Whether AWS adds further Bedrock Mantle and Responses API options to its SDKs.
- How OpenSearch reports advisory checks in real deployment workflows.
- What access controls AWS recommends for public ElastiCache endpoints.
- Whether the new SecurityAgent providers gain additional documented capabilities.
Discussion spark: When a cloud service offers a more flexible configuration, should the provider make the safer option the default, or leave that judgement to operators?
Sources and evidence
- v3.1143.0 (29 September 2026, 19:01 UTC)
not affiliated with or endorsed by Amazon Web Services (AWS)