CliQr is now part of Cisco Learn More About Cisco

AMQP (Required)

The CloudCenter platform includes Advanced Message Queuing Protocol (AMQP) based communication between the CCO and the Agent. The CloudCenter platform uses RabbitMQ as the open source message broker to implement AMQP.


If the application VMs run in isolated networks (like Amazon's VPC), be sure to setup proper NAT rule (only outgoing needed) to allow application VMs to connect to RabbitMQ.

Each CloudCenter deployment requires one AMQP for each CCO.


Guacamole is an optional component that you may choose to deploy if you do not want to expose the AMQP servers to end users. By default, the Guacamole server is installed on the same VM as AMQP.

  • The CloudCenter platform uses a Guacamole server to enable web based SSH/VNC/RDP to Virtual Machines (VMs) launched during the application lifecycle process. The Guacamole component is embedded, by default, in the AMQP server.

  • If you do not want the AMQP IP address to be routable by the end user, you may opt to setup a dedicated (standalone) Guacamole server for a cloud region.

Dedicated Servers

By default, the Guacamole component is installed on the same VM as AMQP. A dedicated Guacamole component is optional and you may choose to deploy it if you do not want to expose the AMQP servers to end users.

If the Guacamole Gateway is installed on a standalone server, Port 7788 needs to be opened on the AMQP instance to allow the Guacamole Gateway to connect to the Connection Broker. See Phase 2: Configure Network Rules for additional context.


If Guacamole is installed as a standalone server, Port 443 must be opened on Guacamole server, instead of on the AMQP server.

  • No labels