CloudFormation Template Rules
In order to deploy your application using Tibica Installer, it has to comply with the set of rules. These rules are check agains the CloudFormation template produced by your stack (whether you are using Serverless Framework or AWS CDK).
Rules
-
Tags
Your application must have the following tags:
Key Value tibica-application SERVICE_NAME
tibica-customer CUSTOMER_ID
tibica-parent STACK_NAME
SERVICE_NAME
is the name of your application starting withtibica-
(for example, tibica-cloud-git).CUSTOMER_ID
is the id of the customer on which your application is installed. You will get it as an environment variable in your application.STACK_NAME
is the name of your stack. It consists of yourSERVICE_NAME
andCUSTOMER_ID
split by a dash:{SERVICE_NAME}-{CUSTOMER_ID}
.Please note that we will not be able to manage applications that do not have these tags or have names that do not start with
tibica-
.You can read more about the values for the tags in the
Vendor Application Structure Readme.md
file. -
IAM Policies
We strictly prohibit the use of wildcards (
*
) in IAM policies, as well as the use of the AWS-managedAdministratorAccess
policy. -
Serverless Resources Only
We prohibit the deployment of non-serverless resources on our accounts. This includes but is not limited to EC2 instances, ECS clusters, EKS clusters, RDS databases, Elasticache clusters, Elastic Beanstalk applications, Redshift clusters, etc.
-
Info Endpoint for API Gateway
If you are deploying an API Gateway, it must have an endpoint that returns information about the application at
/info
route. This endpoint should be accessible without any authentication. Here’s an example of the response if you’re using AWS CDK for Python: