Introducing the next generation of Amazon OpenSearch Serverless for building your agentic AI applications Amazon Web Services announced the next generation of Amazon OpenSearch Serverless, a fully managed search and vector engine for AI agent applications that scales from zero to thousands of requests per second and back to zero when idle. The new version creates resources in seconds, scales capacity up to 20 times faster than the previous generation, and offers up to 60% cost savings compared to provisioned clusters. The update includes native integrations with AI development platforms Vercel and Kiro, enabling developers to deploy production-ready search and vector backends without managing infrastructure. AWS News Blog https://aws.amazon.com/blogs/aws/ Introducing the next generation of Amazon OpenSearch Serverless for building your agentic AI applications | | Today, we’re announcing the next generation of Amazon OpenSearch Serverless https://aws.amazon.com/opensearch-service/features/serverless/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&sc channel=el , a fully managed search and vector engine designed for customers building AI agents. The next generation of OpenSearch Serverless scales from zero to thousands of requests per second and back to zero when idle, offering up to 60% cost savings compared to the cost of OpenSearch Service clusters provisioned for peak capacity. The next generation of OpenSearch Serverless creates resources in seconds and scales capacity up to 20 times faster than the previous generation. With instant resource creation and native integrations with AI development platforms like Vercel https://vercel.com/ and Kiro https://kiro.dev/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&sc channel=el , you can deploy production-ready search and vector backends for your AI agents in minutes without managing infrastructure. The next generation of OpenSearch Serverless in action To get started with the next generation of OpenSearch Serverless, choose Create collection in the Serverless menu in the Amazon OpenSearch Service console https://console.aws.amazon.com/aos/home?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&sc channel=el . Create NextGen collection with instant auto scaling and scale-to-zero for cost optimization. At launch, we support full-text search and vector search only for the collection type. If you want to use the existing OpenSearch Serverless infrastructure, choose Switch to Classic . Choose Express create , the fastest way to create collection. No configuration is required—the default settings and matching security policies are applied automatically. Some configuration options can be changed later. When you choose Create collection , OpenSearch Serverless will provision resources in seconds. You can also create a collection of OpenSearch Serverless with AWS Command Line Interface AWS CLI https://aws.amazon.com/cli/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&sc channel=el or AWS SDKs. Here is a sample CLI command to create a collection group. aws opensearchserverless create-collection-group \ --name channy-nextgen-group \ --standby-replicas ENABLED \ --generation NEXTGEN \ --description "My NextGen collection group" \ --capacity-limits '{ "maxIndexingCapacityInOCU": 10, "maxSearchCapacityInOCU": 10, "minIndexingCapacityInOCU": 0, "minSearchCapacityInOCU": 0 }' \ --region "us-east-1" Now, you can create a collection that inherits the generation from its parent collection group. Supported collection types: SEARCH and VECTORSEARCH . aws opensearchserverless create-collection \ --name channy-nextgen-collection \ --type SEARCH \ --collection-group-name channy-nextgen-group \ --standby-replicas ENABLED \ --description "My collection in NextGen group" \ --region "us-east-1" To learn more about managing the next generation of OpenSearch Serverless, visit the Amazon OpenSearch Serverless documentation https://docs.aws.amazon.com/opensearch-service/latest/developerguide/serverless.html?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&sc channel=el . Building your agents faster with OpenSearch Serverless To support building production-ready agent applications in Vercel, you can now create a new OpenSearch collection or connect your existing OpenSearch Serverless collection within the Vercel console. Create a search backend in seconds and add features on-demand as your application grows. To learn more, visit AWS for Vercel https://vercel.com/marketplace/aws . You can go from idea to working prototype in minutes using Claude Code, Cursor, and Kiro. OpenSearch Agent Skills https://github.com/opensearch-project/opensearch-agent-skills provide a repository of skills that bring OpenSearch intelligence directly into your agent. Each skill encapsulates domain knowledge, best practices, and multi-step execution logic for a specific workflow–so your agent not only gets results, but understands how they were achieved. You can also use the OpenSearch Launchpad https://github.com/opensearch-project/opensearch-launchpad/tree/main/kiro/opensearch-launchpad in Kiro Powers https://kiro.dev/powers/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&sc channel=el to accelerate search applications with guided, end-to-end architecture planning. Now available The next generation of Amazon OpenSearch Serverless is generally available today and is available in all AWS commercial Regions where Amazon OpenSearch Serverless is currently available. The next generation of OpenSearch Serverless charges for the compute you use in OpenSearch Compute Units OCUs for indexing, search, and GPU acceleration https://docs.aws.amazon.com/opensearch-service/latest/developerguide/gpu-acceleration-vector-index.html?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&sc channel=el . You are charged separately for storage in GB-month. For more information, see Amazon OpenSearch Service Pricing https://aws.amazon.com/opensearch-service/pricing/?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&sc channel=el . Give it a try and send feedback to the AWS re:Post for Amazon OpenSearch Service https://repost.aws/tags/TA6VFzFFY6QQa KlHRKR-WsA/amazon-opensearch-service?trk=d8ec3b19-0f37-4f8c-8c12-189f913e205c&sc channel=el or through your usual AWS Support contacts. — Channy https://twitter.com/channyun