cloudpoolCloud instances that cooperate to fulfill a single role in a service should be treated and managed as a group: end-user facing front-ends, database back-ends, etc. Increasing or decreasing the size of the group should be a simple task, no matter which cloud infrastructure(s) the group is deployed on. With elastisys cloud platform’s cloud pools, modifying the size of deployments is as easy as setting a desired size for the group.

Using the elastisys cloud platform’s cloud pools is simple: define a pool, and set a desired size. If a cloud instance in the group is no longer operational, a replacement is provisioned. If the desired size is increased, a new cloud instance is provisioned. If the desired size is decreased, the cloud instance that is closest to starting a new billable period of time stays around until it can be terminated without paying for another period of usage — why waste the capacity it provides if it is already paid for? This increases cost efficiency, and works for all supported clouds.

Health checks and cruise control ties in with cloud pools excellently, and makes it easy to mark instances as fully operational or not, evictable or not (some instances are not allowed to be shut down automatically, e.g., a master Database server — or a failed instance that warrants further investigation), and whether they are even to be regarded in service or not.

Cloud pools are released as open source to the cloud community. Head over to the API documentation on and clone the code from our github page over at the scale.cloudpool repository!

Elastisys cloud platform does cloud pools right. With it, managing large deployments of cloud instances becomes easier, more robust, and more cost-efficient. Your operations team can focus on other tasks, and your billing team appreciates how you get the most bang for your cloud deployment bucks. It just works.

Learn more about the other features of the elastisys cloud platform and about the professional services offered by elastisys.