This tutorial will walk you through the steps required to get a Solace evaluation Virtual Message Router instance running in Amazon Web Services (AWS) and ready for messaging. Solace makes the Amazon Machine Image (AMI) package for AWS available publicly that you can use to run a VMR.
- You have access to AWS.
- EBS Volume of 30 GB or more
- Machine Instance with at least 4 GB of RAM and two vCPUs
- To get a Solace Version 7.2.2 VMR instance up and running and ready for messaging.
Starting the AMI Package in AWS
- Choose a Solace AMI package for AWS.
Go to the Downloads page of dev.solace.com. In the VMR Community Edition or VMR Evaluation Edition areas, select Cloud Images, then, under AMI for Amazon Web Services, select an AWS region appropriate for you. After you read and agree to the license agreement, you will be emailed a link that will take you to the AWS Instance Launch Wizard.
- In the Choose an Instance Type screen of the AWS Instance Launch Wizard, choose an instance to run, and then click Next: Configure Instance Details.
The amount of memory and CPUs configured can affect the number of client connections to the VMR that can be made. A minimum of 4 GB of RAM, and two CPUs is required for all VMR editions. For Evaluation editions, this enables a maximum of 1,000 client connections; if you increase the resources to at least 12 GB of RAM and four CPUs, a maximum of 10,000 client connections can be made.
For Community editions, a maximum of 100 client connections are permitted even if you provision more resources than the minimum system requirements.
- 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.
- In the Add Storage screen, select a sufficiently-sized volume, then click Next: Tag Instance.
The VMR requires 30 GiB. Both SSD volume types ("General Purpose" and "Provisioned IOPS") are supported.
- In the Tag Instance screen, add tags 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.
- In the Configure Security Group screen, create a new security group, and then click Review and Launch.
To enable connectivity to your VMR, create an appropriate security rule for each port that the VMR uses for a service (for information on the default ports the VMR uses, refer to VMR Configuration Defaults). Alternatively you may only expose the services required for your application. Note that AWS can provide a private and public IP address. These addresses must be considered in the security group configuration .
- In the Review Screen, review your instance. Ignore the warnings, and click Launch.
- 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.
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.)
To log into the Linux Host shell, enter the following command:
ssh -p 2222 -i <auth_key> sysadmin@<public_ip>
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.
For information on how to modify the router configurations with the Solace router CLI, refer to the sections provided in Router Configuration.