Deploying Prebuilt Container Images
Flightcontrol allows you to deploy your own pre-built container image with an image registry, which allows you to use the platform for just Continuous Delivery, instead of an integrated Continuous Integration/Continuous Deployment pipeline.
To clarify our terminology, we use "registry" to refer to the host service that stores a collection of image repositories, which we refer to as a "repository." The intended use of this feature is to support private repositories.
Adding an Image Registry to Flightcontrol
Open the Image Registry tab by clicking "Image Registries" in the sidebar, and then click "Add an Image Registry."
We support two different registry types, both of which have different inputs:
- Docker: requires username & password
- Amazon Elastic Container Registry (ECR): registry URI - plus you need to provide IAM permissions for your Fargate service
Using an Image Registry
If you are using infrastructure-as-code to configure your app, you can copy the “Registry ID” and paste into your service config. See Using Code for details.
If you are using the dashboard, select the registry under the “Build System” box, and then add your repository URI and tag in the appropriate text fields.
You must have a connected AWS account because we store your registry credentials in AWS Secrets Manager. This costs $0.40 per registry per month per AWS account.