amplify-category-api icon indicating copy to clipboard operation
amplify-category-api copied to clipboard

Integrate OpenSearch/ElasticSearch features directly into Amplify Gen 2 without external instances

Open oe-bayram opened this issue 1 year ago • 1 comments

Environment information

NPM Packages:
  @aws-amplify/backend: 1.0.0
  @aws-amplify/backend-cli: 1.0.1
  aws-amplify: 6.2.0
  aws-cdk: 2.140.0
  aws-cdk-lib: 2.140.0
  typescript: 5.4.5
AWS environment variables:
  AWS_NODEJS_CONNECTION_REUSE_ENABLED = 1
  AWS_SDK_LOAD_CONFIG = 1
  AWS_STS_REGIONAL_ENDPOINTS = regional
No CDK environment variables

Description

This feature request aims to enhance AWS Amplify by integrating specific search capabilities currently available in OpenSearch/ElasticSearch directly into the Amplify framework, without the need for setting up and managing external OpenSearch instances.

Integrating advanced search features such as sorting, wildcard, and full-text searches requires setting up external instances of OpenSearch or ElasticSearch. Directly integrating these capabilities into Amplify could significantly streamline development processes and reduce overheads associated with maintaining external services.

oe-bayram avatar May 09 '24 17:05 oe-bayram

Hey👋 thanks for raising this feature request! I'm going to transfer this over to our API repository for further evaluation.

ykethan avatar May 09 '24 17:05 ykethan

Hi - we should probably add some docs here. https://docs.amplify.aws/react/build-a-backend/data/custom-business-logic/search-and-aggregate-queries/#step-2-setting-up-the-opensearch-instance instead of creating a new domain, you could in theory also use the opensearch.Domain.from...(...) pattern but we'll need to validate it.

renebrandel avatar Jun 03 '24 14:06 renebrandel