DivvyCloud is able to scale from a single instance managing a few clouds to a fully resilient infrastructure capable of managing hundreds of clouds. We offer a number of deployment and installation options depending on your needs.
This page provides information on our preferred configurations and specifications to help get you started. Keep in mind that no setup is perfect for every customer’s environment and we can only make general suggestions without additional details.
Notes on Deployment
For complex or large cloud footprints it’s likely best to work with one of our team to make sure you get the best recommendations that are tailored to your requirements.
In addition, the content on this page and featured on the individual deployment subpages applies to self-hosted customers. For hosted customers we recommend that you contact your CSM or support with any questions or concerns.
Reach out to [email protected].
Before you get started we recommend reviewing the information included on the Product Architecture page for a general idea of the components used in the DivvyCloud platform.
Instructions for our current recommended deployment method is available on the AWS - EC2 or ECS Fargate - Terraform page.
Visit our Test Drive Deployments overview page for details about "trying out" DivvyCloud.
haproxy is configured both
--reverse-proxy will be set automatically. In DivvyCloud these flags operate as follows:
--https-modewill make cookie handling more secure when running via HTTPS.
--reverse-proxyproperly configures DivvyCloud when running behind a reverse proxy (such as apache or nginx).
For questions on this or other flags reach out to [email protected].
Updated 12 days ago