Setting Up VMRs in AWS

This section will walk you through the steps required to get a single Solace Virtual Message Router (VMR) instance running in Amazon Web Services (AWS) and ready for messaging.

Assumptions

  • You have access to AWS.

System Requirements

For Evaluation and Enterprise VMR editions, the system resources that you provision for the VM automatically determines the number of client connections to the VMR that can be made. If you provision:

  • 30 GB of disk space, 4 GB of RAM, and two vCPUs—a maximum of 1,000 client connections are possible. This is the minimum required system resources.
  • 30 GB of disk space, 12 GB of RAM, and four vCPUs or greater—a maximum of 10,000 client connections are possible.

For Community VMR editions, a maximum of 100 client connections is permitted. Increasing the system requirements will not increase the number of available client connections.

Note:   

  • The minimum supported instance type for a Solace VMR message routing node is m4.large with a storage value type IO1 with 3000 IOPS. For a monitoring node, the minimum supported instance type is m4.large with a storage volume type IO1.
    Performance in AWS will vary depending on instance type and storage configuration. Solace has characterized that deterministic performance is achieved using an instance type of m4.10xlarge with a storage volume type IO1 with 10,000 IOPs. AWS provides different instance types between m4.large and m4.10xlarge which may be suitable for your requirements.
  • To deploy VMRs in high-availability (HA) redundancy groups, you must set up three separate VMR instances as discussed in this section, and then configure them appropriately as a group. For more information on how to configure existing VMRs as an HA group, see Managing VMR Redundancy.

Starting Solace VMR Instance in AWS

To start a Solace VMR instance in AWS, perform the following steps:

  1. Obtain a Solace Amazon Machine Image (AMI) package for the type of VMR edition you will use.

    For Evaluation and Community VMR editions, you must download the AMI through a Solace-provided link. For Enterprise edition VMRs, Solace makes the AMI for AWS directly available to your AWS account.

    • For an Evaluation and Community VMR edition, do the following:
      1. Go to dev.solace.com/downloads/, then in the VMR Community Edition or VMR Evaluation Edition areas, select Cloud Images.
      2. Under AMI for Amazon Web Services, select an AWS region appropriate for you, then after you accept the license agreement, you will be emailed a link that will take you to the AWS Instance Launch Wizard.
    • For an Enterprise VMR edition, do the following:
      1. Log in to your AWS account, and from the main AWS dashboard, select EC2, then click Launch Instance.

        EC2 selection

      2. In the Choose AMI screen, select My AMIs, then select Ownership, and enable Shared with Me.
      3. Find the Solace AMI (the image name has a format of soltr-<version>-vmr-enterprise-cloud), then click Select.

        Choose AMI

  2. In the Configure Instance Details screen, choose an appropriate Amazon Virtual Private Cloud (VPC) and subnet, and then click Next: Add Storage.

    For information about VPCs and subnets, refer to AWS documentation.

    Choose an Instance Type

  3. In the Configure Instance Details screen, configure the VPC, then click Next: Add Storage.
  4. Configure Instance Details

  5. In the Add Storage screen, select a sufficiently-sized volume, and then click Next: Tag Instance.

  6. In the Tag Instance screen, add tags as appropriate to keep your VMR instances organized, then click Next: Configure Security Group.

    The following example uses Name, Owner, and Version but you can choose any tags that make sense for your application.

    Tag Instance

  7. In the Configure Security Group screen, create an appropriate security rule for each port that the VMR uses for a service to enable connectivity to your VMR, and then click Review and Launch.

    For information on the default ports the VMR uses, refer to VMR Configuration Defaults. The example below includes rules for all service ports that the VMR may use. Alternatively you may only expose the services required for your application.

    Note:   

    • AWS can provide a private and public IP address. These addresses must be considered in the security group configuration.
    • If you will be using the VMR in an HA redundancy group with other VMRs, you must create security rules for ports 5404, 5405, and 8741.

    Configure Security Group

  8. In the Review Screen, review your instance. Ignore the warnings, and click Launch.
  9. The instance will start. In the dialog box that starts, choose an authentication key pair for the VMR instance, which can be used for this first login to the VMR, and then click Launch Instance.

    Authentication Key Pair

    The EC2 dashboard will show your VMR instance under Instances. Here you can find the external and internal IP address of the instance. (For more information, refer to IP Addressing in the Cloud.)

  10. To log into the Linux Host shell, enter the following command:

    ssh -p 2222 -i <auth_key> sysadmin@<public_ip>

Configuring Users

After initially booting a cloud instance of a VMR, only key-based login for the sysadmin account is allowed. For more information on login and user configuration, refer to Configuring Users in the Cloud.

Managing the VMR Configuration

Unlike a Solace messaging appliance, a VMR starts with a basic configuration that enables most common services. This basic configuration can be modified as required. For more information, refer to VMR Configuration Defaults.