Cloudformation
You can deploy any Cloudformation manifests/templates with Qovery and manage the lifecycle of your own cloud resources. For example, you can deploy your own databases, lambdas, brokers etc...
Running and deploying your Cloudformation manifest/template is achieved via the Qovery Lifecycle Jobs, have a look at this section to know how it works.
To simplify the configuration, Qovery provides a Cloudformation configuration template for your Lifecycle job, allowing you to package your manifest and run it with the Cloudformation CLI directly on your cluster.
Follow these steps to create and deploy your Cloudformation manifest/template:
- Add a new service
Enter the environment where you want to deploy your Cloudformation manifest and select the "Add Service" button
- Use the Cloudformation template
Select the "Cloudformation" option in the service creation list and follow the steps.
- Manifest location
Provide the location of your manifest within your git repository
- Customize your configuration
Qovery provides you with a pre-configuration for your lifecycle job capable to run and deploy your Cloudformation:
- Dockerfile: you will find a Dockerfile capable to package your manifest/template and run the right Cloudformation command depending on the event triggered (Example: the "start" command executes "Cloudformation apply .."). Customize this file to match your needs (backend config, additional configuration etc..)
- Triggers: you will find the default triggers and commands based on the default Dockerfile.
- Resources: you will find a default CPU/Memory values capable to run the Cloudformation CLI on a Kubernetes job
- Environment variables: you will be able to provide the input of your Cloudformation manifest/template as file, which will be stored as an environment variable as file. You can also add additional environment variables necessary to run the Cloudformation commands (like AWS_SECRET_ACCESS_KEY etc..)
- Create & Deploy
Once it is all set, you can Create and Deploy your Cloudformation job. This will trigger the execution and deployment of the Cloudformation manifest/template.
- Access the Cloudformation output
If your Cloudformation manifest/template generates an output (see Lifecycle job output for more information), the output will be fetched and injected as environment variable to any service of the same environment. It will allow those services to access the newly created resource.
