reference deployment

Solace PubSub+ Message Router on AWS

Enterprise-grade messaging and streaming for hybrid clouds, IoT, mobile applications, and event-driven microservices

This Quick Start automatically deploys Solace PubSub+ on the AWS Cloud. Solace PubSub+ is a message broker that lets you establish event-driven interactions between applications and microservices regardless of location.

With PubSub+, you can meet all your data movement needs—publish/subscribe, queueing, request/reply, and streaming—with one platform that spans cloud and on-premises environments. You can choose from a number of open protocols, including Advanced Message Queuing Protocol (AMQP), Java Message Service (JMS), Message Queuing Telemetry Transport (MQTT), Representational State Transfer (REST), and WebSocket.

This Quick Start uses AWS CloudFormation templates to deploy Solace PubSub+ message brokers in high availability (HA) redundancy groups for fault tolerance. You can use the Quick Start to build a new virtual private cloud (VPC), or deploy Solace PubSub+ message brokers into your existing VPC.

Note   An earlier version of this Quick Start was published under the product name Solace Virtual Message Router (VMR). Solace has renamed their product suite, and VMR is now referred to as Solace PubSub+. See the Solace products page for more information.

This Quick Start was developed by Solace Corporation in collaboration with AWS. Solace is an AWS Partner.

AWS Service Catalog administrators can add this architecture to their own catalog.  

  •  What you'll build
  •  How to deploy
  •  Cost and licenses
  •  What you'll build
  • Use this Quick Start to automatically set up the following Solace PubSub+ environment on AWS:

    • A single virtual private cloud (VPC) that spans three Availability Zones, with one public and one private subnet in each Availability Zone. You can also choose to deploy the Quick Start in two Availability Zones. In this case, the backup and monitoring instances of the message broker will be placed in the same Availability Zone.*

    Note   For production systems, we recommend using three Availability Zones, where available. For test or proof-of-concept (PoC) environments, you can choose to omit the private subnets.

    • An internet gateway to provide internet access to each subnet. This gateway is used by bastion hosts to send and receive traffic.*
    • Load balancer support with health checks (using Classic Load Balancers).*
    • In each public subnet, managed NAT gateways to allow outbound internet access for the message broker instances.*
    • In each public subnet, Linux bastion hosts in an Auto Scaling group to allow inbound Secure Shell (SSH) access to the message broker instances.*
    • In each private subnet, a single message broker instance that is assigned an HA role. For auto-recovery, these instances are set up with Amazon CloudWatch alarms. Docker is installed on each message broker instance, and the message broker instance is installed and executed within a Docker container.
    • CloudWatch logging support, including the log file /tmp/install-solace.log, which logs the events during installation.

    *  The template that deploys the Quick Start into an existing VPC skips the tasks marked by asterisks and prompts you for your existing VPC configuration.

  •  How to deploy
  • To build your Solace PubSub+ message broker environment on AWS, follow the instructions in the deployment guide. The deployment process includes these steps:

    1. If you don't already have an AWS account, sign up at See the deployment guide for resource requirements for the deployment.
    2. Obtain a reference to the Solace PubSub+ Docker image. See the deployment guide for details.
    3. Launch the Quick Start. Each deployment takes about 20 minutes to complete. You can choose from two options:
    4. Test the deployment by using the Solace Command Line Interface (CLI).

    To customize your deployment, you can configure infrastructure settings, boot disk capacity, and instance types for the message router and monitor instances.

    Amazon may share user-deployment information with the AWS Partner that collaborated with AWS on the Quick Start.  

  •  Cost and licenses
  • You are responsible for the cost of the AWS services used while running this Quick Start reference deployment. There is no additional cost for using the Quick Start.

    The AWS CloudFormation template for this Quick Start includes configuration parameters that you can customize. Some of these settings, such as instance type, will affect the cost of deployment. For cost estimates, see the pricing pages for each AWS service you will be using. Prices are subject to change.

    Tip  After you deploy the Quick Start, create  AWS Cost and Usage Reports to track costs associated with the Quick Start. These reports deliver billing metrics to an S3 bucket in your account. They provide cost estimates based on usage throughout each month, and aggregate the data at the end of the month. For more information about the report, see the AWS documentation.

    You can use this Quick Start to deploy PubSub+ Standard or PubSub+ Enterprise. By using the Solace PubSub+ message broker, you agree to terms and conditions outlined in the License Agreement for Solace Software on the Solace website.