Amplify-cli: Removing Elastic Search with @searchable tag
When building my API, I set up some models to be searchable by using the @searchable tag. However, even though I am not using the functionality, the Elastic Search costs are really hurting me.
If I remove the searchable tag and do an amplify push, should that take care of everything, or do I need to also do something inside AWS to stop being charged?
walter-scott
All 4 comments
You can double check in AWS Console if there is a ElasticSearch Service, if not, all is fine.
davidbiller
on 30 Oct 2019
If you just remove @searchable tag from your schema, the elasticsearch cluster would be removed.
kaustavghosh06
on 30 Oct 2019
@kaustavghosh06 IMO the amplify team should add a warning to the docs because adding a simple @searchable attribute results in the costs increasing dramatically so extra precaution should be taken with this. Just received a surprise billing and having an (unused) @searchable attribute was the reason.
hugozap
on 4 Oct 2020
+1 https://github.com/aws-amplify/amplify-cli/issues/3860
@kaustavghosh06 IMO the amplify team should add a warning to the docs because adding a simple @searchable attribute results in the costs increasing dramatically so extra precaution should be taken with this. Just received a surprise billing and having an (unused) @searchable attribute was the reason.
JuanmanDev
on 14 Nov 2020
Related issues
davo301
路
3Comments
rehos
路
3Comments
YikSanChan
路
3Comments
amlcodes
路
3Comments
ReidWeb
路
3Comments
Most helpful comment
@kaustavghosh06 IMO the amplify team should add a warning to the docs because adding a simple @searchable attribute results in the costs increasing dramatically so extra precaution should be taken with this. Just received a surprise billing and having an (unused) @searchable attribute was the reason.