Package a CloudFormation template in a deployable Microtica Component.

To use this step, you would need to have an existing CloudFormation template hosted on your Git account.

The parameters you define in the CloudFormation template will automatically become an input parameters of the component. You can set the parameter values from 

Learn how to package a CloudFormation template into a deployable Microtica Component using this comprehensive document. Gain insights into hosting the CloudFormation template on a Git account and explore a YAML code example for defining input parameters. 

Trigger Pipeline

CloudFormation Component

Terraform Build

Microtica

Microtica Docs

How Microtica works

Deploy your application

Migrate from Heroku to AWS

Migrate to Microtica

Getting started

Billing

Project

Environment

CloudFormation

Terraform

Assign Domain

Components

Import an existing app

Scaling

Applications

Pipeline Syntax

Steps

Stages

Artifacts

Variables

Pipelines

Manual deployments

Automated deployments

Deploy from multiple Git branches

Pipeline Notifications

Deployment Insights

Automated Rollbacks

Deployments

Core Concepts

Connect an AWS account

Connect a GCP account

Connect a Container Registry

Connect an Existing Kubernetes Cluster

Integrations

Deploy a New Strapi App

Deploy an Existing Strapi App

Configure a Custom Domain

Access the RDS database

Scaling your Strapi App

Migrate your Strapi app from Heroku to AWS

Strapi Serverless

Medusa Server

Appwrite

Add Custom Variables

SPA on CloudFront

EKS Administration

Amazon EKS

Import an existing Node.js application

Node.js

Import an existing n8n application

Database Administration

n8n Workflow Automation

Next.js

Templates

Metrics

Cloud Native Monitoring

Cost Reports

Cost Dashboard

Automated Saving Schedules

Cloud Cost Optimization

Monitoring & Optimization

Changelog

Parameter	Description	Required
title	The display name of the step.	No
type	The type of the Microtica built-in step. Should always be cfn-component for this type of step.	Yes
cfn_template	Path to the CloudFormation template.	Yes
schema	Path to the JSON schema file. Used to define custom input/output parameters and validation for the component. If not provided, CloudFormation parameters will be considered as component’s input parameters.	No