Discussion on "How to run a highly-available Typesense search in AWS"

Stefan Olaru · 2022-12-20T12:20:42.338Z

Retrieving relevant search results blazing-fast is a challenge. A solid search requires typo tolerance, result rankings, synonyms, filtering, faceting, geo search, and so on. Quite often the underlying database schema is not optimized for our search ...

I am able to create the full stack, but how to access the dahsboard

Hi Stefan,

May I ask why you decided to use a SNS Topic with a Lambda subscribed to it?

Con: It seems like an extra step because you could just invoked the lambda at the end of the UserData script instead of writing to the SNS Topic at the end of the UserData script, which causes the lambda to be invoked.

Pro: It does seem cleaner to separate the concerns of the lambda running successfully and the UserData script installing Typesense successfully.

Was this your thinking or am I missing something?

Ohhh... I suppose the startup would be tricky without the SNS Topic. The order of creation of things might become a tricky obstacle: The lambda has to be created to be triggered and yet the lambda needs to know some things about the autoscaling group.

Hey Calvin, the SNS topic is in there because the AutoScaling group will publish a message to it in case of EC2_INSTANCE_TERMINATE. E.g. in case of a scale-down

Stefan Olaru Ahh that makes sense. Thank you much!

You are a life saver, I tried running your one-click deployments and am getting a "No export named typesense-vpc-VPCID found. Rollback requested by user." error though and can't figure out why?

The names of the vpc stack's exported values are dependent on the name of the stack. I named my vpc stack, "typesense-vpc", in order for the exported values to have the names that the cluster stack expects.

Calvin Butler Stefan Olaru Thanks so much for replying (I missed this) I tried recreating the stacks with the VPC stack first and I called it "typesense-vpc". I am now getting an error when trying to create the instance event listener of "Resource handler returned message: "Error occurred while GetObject. S3 Error Code: NoSuchKey. S3 Error Message: The specified key does not exist." when deploying the cluster stack

aaron ueckermann sounds like the S3 bucket is missing the instance-listener.zip

I missed this in the article for some reason ☺️

Please copy as mentioned in repo readme #2: github.com/stefanolaru/aws-cloudformation-templat…

Great article, Stefan! I'll refer back to this in some time!

Thank you, Ovi! 🙏

Search Hashnode

How to run a highly-available Typesense search in AWS

Responses4