Deploy a new Strapi app
Deploy a new Strapi app on your own AWS account with Microtica in under 10 minutes — ready infrastructure built on GitOps and declarative deployments.
Strapi is an open-source headless CMS built with NodeJS. With Strapi you design and publish the content your apps consume via API. Its admin UI lets you design data models and create and manage content.
Running Strapi on Microtica keeps setup simple and maintenance low while the infrastructure runs on your own AWS account. It follows a GitOps and declarative-infrastructure approach for stable, reliable, and predictable deployments.
Serverless Strapi on AWS
With this approach, Strapi can coexist with your existing AWS infrastructure, and you can always extend the setup with more cloud resources.
Microtica uses Strapi v4 as the default version for the Strapi Serverless template.
Infrastructure ownership
The Strapi infrastructure will be provisioned on your own AWS account. You retain full control over your infrastructure and data while getting all the benefits of infrastructure automation.

Microtica provides a built-in template that provisions the infrastructure to run Strapi on your AWS account in a scalable, secure, and reliable way with zero-downtime deployments.
To deploy the infrastructure, select the Strapi Serverless template.

Follow the template steps to deploy the Strapi app on your AWS account.
1. Create a Git repository
First, connect a Git account (GitHub, Bitbucket, or GitLab). Microtica sets a default repository name for each template, but you can change it. If you already have a Git account connected, choose it from the list. Microtica creates a new repository on your account with the name you provide, and deploys every Git push automatically.
2. Configure the template
Next, configure the environment variables for this template. Variables let you customize the template to your needs.
For example, this is where you configure the scaling parameters for your Strapi app. You can scale vertically and horizontally. For vertical scaling, update the CPU and Memory configuration in this section. For horizontal scaling, update the number of desired replicas in the same section.
In this section you also choose the database client — sqlite is the default option.

You can update the configuration later as well.
3. Configure the environment
After configuring the template, select an environment where the template will reside. Environments are a great way to separate your development and production applications. To create a new environment, enter its name and description and click the Select button. You can also choose an existing environment if you created one previously.
Next, configure the target AWS account where your Strapi infrastructure will be provisioned. Here is a quick guide on how to connect your AWS account.
4. Deploy
Once your AWS account is connected and configured in the environment, click the Deploy button to trigger the deployment.
It takes up to 10 minutes to create a live Strapi environment.
Follow the pipeline logs inline and monitor your deployment in real time.
Once the template deployment finishes, find the access URL in Environment > Infrastructure > Strapi (Strapi is the AppName you provided in the template configuration step), under Resource outputs, in the AccessUrl parameter. Paste it into your browser to see your Strapi demo app.

Next steps
Strapi Serverless
Run a Strapi headless CMS on your own AWS account with Microtica's Strapi Serverless template — Fargate, RDS, EFS, and S3 provisioned for you.
Deploy an existing Strapi app
Deploy your existing Strapi app on your own AWS account with Microtica — connect your Git repo, review the database config, and ship in minutes.
