Is there a way to keep costs low with AWS Amplify DataStore @searchable directive?

Question

I'm using AWS Amplify DataStore to create an offline first notes app. To be able to search my notes I just add the @searchabledirective to the Schema and my DB documents are streamed to an AWS elastic service.

But, my initial test of this ended up costing me a lot of money. My dev project went from $2/month to $30/month just by adding the ES node. There doesn't seem to be a way to downscale the service from the AWS console.

Does anyone know of a way to not pay $30/month for 12kb of data in ES?

Answer 1

As per the documentation the @searchable directive sets up an ElasticSearch instance and streams data there. Moreover, t2.micro instances are not compatible - probably why you can't downscale.

There are a number of issues on the AWS Amplify Github repo similar to your question - see this and this.

I am in a similar boat and debating setting up a small server running MeiliSearch or migrating to Algolia.

FWIW, the AppSync documentation search is powered by Algolia :-).