Integration
Containerised and deployed to AWS.
Deployment is part of the platform rather than a pipeline you assemble. GetFlowing builds the container image, pushes it to a private registry and runs the rollout on AWS, with health checks in front of production traffic.
Integration
AWS integration
How it works
Applications are containerised and deployed to AWS. Each one gets a generated URL, and a custom domain when you are ready for it. Logs, health monitoring and rollback are available from the same control plane that shipped the release, and cloud resources stay under your control.
The path
From merged change to running application.
Six stages between a merge and live traffic. Each one has a visible status, which is what makes a release something you can explain afterwards.
Build
The container image is built from the merged change and checked before it is stored in a private registry.
Approve
A production deployment pauses for a human, with an explanation of what is about to happen.
Provision
Cloud services on AWS are provisioned or updated for the environment being released to.
Check
Health checks run against the new release before it is allowed to take production traffic.
Serve
Traffic moves to the healthy release, reachable on its generated URL or your own domain.
Operate
Traffic, latency, errors, uptime and logs are monitored, with rollback available if something is wrong.
Specification
What the AWS integration covers.
The aim is a release you can explain: what was built, what was deployed, whether it is healthy and how to undo it.
- Where it runs
- Applications are containerised and deployed to AWS. Cloud resources stay under your control.
- Image supply chain
- Images are held in a private registry, and the artefact that passed the build is the one that runs.
- Release gate
- Health checks run against the new release, and production traffic only moves once it passes.
- Addressing
- Every deployed application gets a generated URL. Custom domains are included from the Pro plan upwards.
- Monitoring
- Traffic, latency, errors, uptime and resource usage, next to the release that changed them.
- Undo
- Logs, deployment history and rollback, in the same place that shipped the release.
- Network isolation
- Each application is network isolated from every other and from the platform internals, with access restricted to what the application actually needs to run.
- Environments
- One on Starter, two on Pro, four on Business and six on Scale, so staging arrives when your release process needs it.
Private beta
Bring software delivery into one system.
Build something new or take control of what already exists. Get the planning, engineering, deployment, and operational capability of an experienced software team.