Deploying PubSub+ Cloud with AWS

Support for VM-based deployments is now deprecated and version 10.0.1 was the last event broker release that supported deployments in VM-based regions. For more details, see the Deprecated Features list.

Solace recommends that you choose a Kubernetes deployment for PubSub+ Cloud rather than the other environments discussed on this page. See Other Deployment Environments.

You can deploy PubSub+ Cloud in a dedicated Virtual Private Cloud (VPC) in AWS in your own AWS account. The Mission Control Agent and software event brokers are deployed in a VPC that has been appropriately provisioned.

If you install PubSub+ Cloud in your own VPC, you have control over the infrastructure and can apply any required security polices to the infrastructure. In this model, you pay the IaaS costs directly, which allows you to take advantage of any corporate discounts you may have with AWS.

The details of this deployment are discussed in the following sections:

Customer-Controlled VPC: Detailed Architecture

When PubSub+ Cloud is installed in a customer-controlled VPC, all components are instantiated in, and form part of, the customer's Virtual Private Cloud (VPC). This deployment model ensures that the customer's message and event data stays within their private cloud, allowing the customer to control the boundaries of the PubSub+ Cloud capability. Customers can also provide a separate account for Solace to use to access the client’s PubSub+ Cloud components.

If the VPC is owned by the customer, it can be dedicated to the event brokers as shown below, or it can be shared with the applications that use the event broker services.

The setup of the VPC is as follows:

  • One private subnet contains an EC2 instance that runs the Mission Control Agent.
  • Three private subnets contain the EC2 instances that run the event broker services. The size of these three subnets depends on the number of event broker services the customer needs to create.

    HA event broker services are fronted by a network load balancer that routes traffic to and from the active node in the event broker service(either the primary or backup software broker).

  • One private subnet for the EC2 instance containing the Mission Control Agent Installer (not shown).
  • An internet gateway routes external traffic to and from the VPC.

Depending on how your client applications need to connect to your event broker services, the actual VPC configuration may be slightly different than what is shown in the diagram above. For details, see AWS VPC Setup and Connectivity Model for AWS.