High Availability (active/active) shared EC2 cloud loses templates on the replicas not connected to the operations center

Last Reviewed:2026-11-03()
2 minute readKnowledge base

Issue

When an Amazon EC2 cloud is defined as a shared cloud at the operations center and pushed to a controller running in High Availability (active/active) mode, the EC2 cloud intermittently loses all of its templates on the replicas that are not connected to the operations center.

The following symptoms appear:

  • CloudConfigurationSnippetHandler#consume: Applied/updated Clouds configuration […​] is logged every 60 seconds on each replica.

  • The EC2 cloud’s template count flips between the expected number and 0, as the replicas repeatedly overwrite each other’s cloud configuration.

  • A rolling restart of the controller temporarily resolves the symptom until the next operations center context update.

Environment

Resolution

A fix is pending inclusion in a future CloudBees CI release, this article will be updated once the fix is available.

An alternative solution is to not rely on the operations center shared cloud for the EC2 cloud configuration and instead define it directly on the affected controller using controller-level Configuration as Code (CasC).

Workaround

  1. Move the EC2 cloud configuration from the operations center shared cloud to controller-level Configuration as Code (CasC) on the affected controller.

  2. This is the recommended long-term solution as well, since defining the cloud directly on the controller avoids the operations center shared-cloud replication path entirely.

  3. If the EC2 shared cloud cannot be removed from the operations center because other controllers still rely on it:

    1. Install the Extension Filter Plugin on the affected controller.

    2. Block the com.cloudbees.opscenter.context.config.CloudConfigurationSnippetHandler extension to prevent all shared cloud configurations from syncing from the operations center.

    3. Define the clouds directly on the controller, for example through CasC, once the sync is blocked.

Tested product/plugin versions

  • CloudBees CI on modern cloud platforms 2.568.3.37913

References

This article is part of our Knowledge Base and is provided for guidance-based purposes only. The solutions or workarounds described here are not officially supported by CloudBees and may not be applicable in all environments. Use at your own discretion, and test changes in a safe environment before applying them to production systems.