Strapi Serverless

Strapi is an open-source headless CMS built with NodeJS. Using Strapi you can easily design and publish the content consumed by your apps via API. Strapi provides a great admin UI portal where you can design your data models, and create and manage content.

The benefits of using the Strapi Serverless Template on Microtica for your projects are the simplicity of setup and low maintenance while having the infrastructure on your own AWS account. We are following the GitOps and declarative infrastructure approach for stable, more reliable, and predictable deployments.

With this template, Strapi can coexist with your existing AWS infrastructure and you always have the flexibility to extend this setup with additional cloud resources.

Since Microtica deploys on your cloud account, you would expect nothing less than complete transparency of what resources are going to be provisioned.

Using the Strapi Serverless template, you will create a few components in the environment:

• VPC — VPC, subnets and networking
• ContainerRunner — Container infrastructure based on Fargate and application load balancer. This component will run the Strapi project
• StrapiServerless — Persistent storage, relational databased and S3 storage
• StrapiApp (optional) — component for your existing Strapi project. If not provided, a standalone Strapi development environment is created

The Strapi Serverless template uses an Amazon EFS file system to store the persistent Strapi files:

• image uploads — media files storage
• api folder — only for the standalone setup where you don’t have your source code connected via Git (default). In this guide, we will explain how you can deploy your existing Strapi project
• data folder — store the sqlite data file, if database client is sqlite (default) The data stored in these folders will persist on subsequent deployments, application restarts or even if you kill the container completely.

The template provisions an RDS MySql database only if the database client is mysql.

The database is encrypted using a custom KMS key. The database password is automatically generated and stored securely in an AWS Secret Manager secret.

By default, the template provisions an AWS Fargate cluster with one container. For production environments we recommend at least two containers running all the time. This will also ensure a zero-downtime deployment.

The Fargate services are exposed via Application Load Balancer. When using a custom domain, which is recommended for production, the domain certificate will be attached and SSL termination will happen on this load balancer.

Since we use persistent file storage, all containers share the same file system.

The Strapi application logs are stored in CloudWatch Logs. You can monitor the logs from the Fargate console under tasks. The default log retention is 90 days.

These environment variables will be provided in the Strapi application runtime.

The following environment variables are provided only when DATABASE_CLIENT is set to mysql or postgres.

The estimated cost of the AWS cloud depends on the configuration of the Strapi infrastructure. Below is the cost estimation breakdown based on different configurations assuming the resources are running all the time:

• sqlite with one app container (0.25 vCPU and 0.5GB memory) the costs is around $30/month
• MySql with one app container (0.25 vCPU and 0.5GB memory) the cost would be around $45/month
• each additional container with the default config is $14/month

Additional costs apply for using the AWS EFS for storing media files (~$0.09 GB/month).

You can reduce the cost of your non-production Strapi environments with our Cloud Waste Manager.