From f5e764209b06979945705211fd4aceb7d4334049 Mon Sep 17 00:00:00 2001 From: Joel Coutinho Date: Thu, 21 Sep 2023 12:09:24 +0530 Subject: [PATCH] minor change --- content/how-we-cut-our-aws-costs/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/how-we-cut-our-aws-costs/index.md b/content/how-we-cut-our-aws-costs/index.md index 6e67a78a..24b19464 100644 --- a/content/how-we-cut-our-aws-costs/index.md +++ b/content/how-we-cut-our-aws-costs/index.md @@ -44,7 +44,7 @@ In retrospect, another avenue for improvement that we identified was the usage o So what prompted us to change our deployment process? ## Why we had to change our deployment process -The past year has been quite a ride for SuperTokens. We rolled a host of new features and saw a big uptick in users. But, as our user numbers climbed, so did our infrastructure costs. With our AWS credits running out soon, we knew we had to do something to cut our expenses. +The past year has been quite a ride for SuperTokens. We released a host of new features and saw a big uptick in users. But, as our user numbers climbed, so did our infrastructure costs. With our AWS credits running out soon, we knew we had to do something to cut our expenses. With the release of our new multi-tenancy feature we saw the opportunity to consolidate core instances to optimize the utilization of our EC2 instances to cut down our costs while also providing the expected performance.