You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm proposing the addition of a new AWS CloudFormation resource type, AWS::OpenSearchServerless::Index, to facilitate the creation of indexes within OpenSearch Serverless collections.
Background:
OpenSearch Serverless currently supports the creation of collections using the AWS::OpenSearchServerless::Collection resource. However, there is no native support for creating indexes within these collections.
Necessity:
The absence of a dedicated resource for creating indexes poses challenges, especially when creating resources like Bedrock KnowledgeBases (AWS::Bedrock::KnowledgeBase). A Bedrock KnowledgeBase requires a pre-existing index, forcing the use of custom CloudFormation resources, which adds complexity and limits the ability to manage resources efficiently within a single CloudFormation template.
My current implementation of Open Search Indexs for Bedrock roughly follows:
The custom resource to act as AWS::OpenSearchServerless::Index translates the Properties and preforms a PUT request against the collection endpoint to create the index
Resource Name
OpenSearchServerless - [AWS::OpenSearchServerless::Index]
Details
I'm proposing the addition of a new AWS CloudFormation resource type,
AWS::OpenSearchServerless::Index
, to facilitate the creation of indexes within OpenSearch Serverless collections.Background:
OpenSearch Serverless currently supports the creation of collections using the
AWS::OpenSearchServerless::Collection
resource. However, there is no native support for creating indexes within these collections.Necessity:
The absence of a dedicated resource for creating indexes poses challenges, especially when creating resources like Bedrock KnowledgeBases (AWS::Bedrock::KnowledgeBase). A Bedrock KnowledgeBase requires a pre-existing index, forcing the use of custom CloudFormation resources, which adds complexity and limits the ability to manage resources efficiently within a single CloudFormation template.
My current implementation of Open Search Indexs for Bedrock roughly follows:
The custom resource to act as
AWS::OpenSearchServerless::Index
translates the Properties and preforms a PUT request against the collection endpoint to create the indexThe text was updated successfully, but these errors were encountered: