Hybrid cloud computing network management

1. A computer-implemented method executed by one or more processors comprising:

configuring, by the one or more processors, a first node to participate in a node cluster, wherein the first node is hosted by a first cloud service provider, and wherein participating in the node cluster includes performing one or more processing actions specific to the node cluster on data received by the node;

configuring, by the one or more processors, a second node to participate in the node cluster, wherein the second node is hosted by a second cloud service provider different than the first cloud service provider;

receiving, by the one or more processors, a status indication from the first node over a network that is a public network;

in response to receiving the status indication, determining, by the one or more processors, a synchronization mechanism for the first node based on a network configuration of the first node, wherein the determined synchronization mechanism is configured to allow the first node to acquire synchronization data from other nodes in the node cluster;

in response to determining the synchronization mechanism, transmitting, by the one or more processors, the determined synchronization mechanism to the first node over the network;

configuring, by the one or more processors, a third node to participate in the node cluster, wherein the third node is a physical computing device hosted in a private network;

receiving, by the one or more processors, a status indication from the third node over the public network;

in response to receiving the status indication, determining a particular synchronization mechanism for the third node based on its location on the private network, wherein the particular synchronization mechanism includes initiation of synchronization by the third node; and

in response to determining the particular synchronization mechanism, transmitting the particular synchronization mechanism to the first node over the network.

2. The method of claim 1 , wherein the first node is a virtual machine instance, and configuring the first node includes calling an application programming interface (API) provided by the first cloud service provider to create the virtual machine instance.

3. The method of claim 1 , wherein the particular synchronization mechanism is configured to allow the third node to obtain synchronization information from other nodes in the cluster without accepting inbound connections from the public network.

4. The method of claim 1 , wherein the one or more processing actions specific to the node cluster include performing threat analysis and selectively performing corrective action in response to receiving network traffic from a network client.

5. The method of claim 4 , wherein the network client is a client of the first cloud service provider, and wherein the first node is configured to perform threat analysis and selectively perform corrective action on network traffic received from the network client.

6. The method of claim 4 , wherein the network client is a client of the second cloud service provider, and wherein the second node is configured to perform threat analysis and selectively perform corrective action on network traffic received from the network client.

7. The method of claim 1 , wherein the initiation of synchronization by the third node passes through a firewall configured to permit the initiation of synchronization by the third node and to block initiation of synchronization by the one or more processors.

8. A non-transitory, computer-readable medium storing instructions operable when executed to cause at least one processor to perform operations comprising:

configuring, by the one or more processors, a first node to participate in a node cluster, wherein the first node is hosted by a first cloud service provider, and wherein participating in the node cluster includes performing one or more processing actions specific to the node cluster on data received by the node;

configuring, by the one or more processors, a second node to participate in the node cluster, wherein the second node is hosted by a second cloud service provider different than the first cloud service provider;

receiving, by the one or more processors, a status indication from the first node over a network that is a public network;

in response to receiving the status indication, determining, by the one or more processors, a synchronization mechanism for the first node based on a network configuration of the first node, wherein the determined synchronization mechanism is configured to allow the first node to acquire synchronization data from other nodes in the node cluster;

in response to determining the synchronization mechanism, transmitting, by the one or more processors, the determined synchronization mechanism to the first node over the network;

configuring, by the one or more processors, a third node to participate in the node cluster, wherein the third node is a physical computing device hosted in a private network;

receiving, by the one or more processors, a status indication from the third node over the public network;

receiving, by the one or more processors, a status indication from the third node over the public network;

in response to receiving the status indication, determining a particular synchronization mechanism for the third node based on its location on the private network, wherein the particular synchronization mechanism includes initiation of synchronization by the third node; and

in response to determining the particular synchronization mechanism, transmitting the particular synchronization mechanism to the first node over the network.

9. The non-transitory, computer-readable medium of claim 8 , wherein the first node is a virtual machine instance, and configuring the first node includes calling an application programming interface (API) provided by the first cloud service provider to create the virtual machine instance.

10. The non-transitory, computer-readable medium of claim 8 , wherein the particular synchronization mechanism is configured to allow the third node to obtain synchronization information from other nodes in the cluster without accepting inbound connections from the public network.

11. The non-transitory, computer-readable medium of claim 8 , wherein the one or more processing actions specific to the node cluster include performing threat analysis and selectively performing corrective action in response to receiving network traffic from a network client.

12. The non-transitory, computer-readable medium of claim 11 , wherein the network client is a client of the first cloud service provider, and wherein the first node is configured to perform threat analysis and selectively perform corrective action on network traffic received from the network client.

13. The non-transitory, computer-readable medium of claim 11 , wherein the network client is a client of the second cloud service provider, and wherein the second node is configured to perform threat analysis and selectively perform corrective action on network traffic received from the network client.

14. The non-transitory, computer-readable medium of claim 8 , wherein the initiation of synchronization by the third node passes through a firewall configured to permit the initiation of synchronization by the third node and to block initiation of synchronization by the one or more processors.

15. A system comprising:

non-transitory memory for storing data; and

one or more processors operable to perform operations comprising:

configuring, by the one or more processors, a first node to participate in a node cluster, wherein the first node is hosted by a first cloud service provider, and wherein participating in the node cluster includes performing one or more processing actions specific to the node cluster on data received by the node;

configuring, by the one or more processors, a second node to participate in the node cluster, wherein the second node is hosted by a second cloud service provider different than the first cloud service provider;

receiving, by the one or more processors, a status indication from the first node over a network that is a public network;

in response to receiving the status indication, determining, by the one or more processors, a synchronization mechanism for the first node based on a network configuration of the first node, wherein the determined synchronization mechanism is configured to allow the first node to acquire synchronization data from other nodes in the node cluster;

in response to determining the synchronization mechanism, transmitting, by the one or more processors, the determined synchronization mechanism to the first node over the network;

configuring, by the one or more processors, a third node to participate in the node cluster, wherein the third node is a physical computing device hosted in a private network;

receiving, by the one or more processors, a status indication from the third node over the public network;

in response to receiving the status indication, determining a particular synchronization mechanism for the third node based on its location on the private network, wherein the particular synchronization mechanism includes initiation of synchronization by the third node; and

in response to determining the particular synchronization mechanism, transmitting the particular synchronization mechanism to the first node over the network.

16. The system of claim 15 , wherein the first node is a virtual machine instance, and configuring the first node includes calling an application programming interface (API) provided by the first cloud service provider to create the virtual machine instance.

17. The system of claim 15 , wherein the initiation of synchronization by the third node passes through a firewall configured to permit the initiation of synchronization by the third node and to block initiation of synchronization by the one or more processors.