a9s RabbitMQ for PCF (Beta)

IMPORTANT: The a9s RabbitMQ for Pivotal Cloud Foundry (PCF) tile is currently in beta and is intended for evaluation and test purposes only. Do not use this product in a PCF production environment.

This documentation describes the a9s RabbitMQ for PCF tile.

A9s rabbitmq tile


a9s RabbitMQ for PCF enables on-demand provisioning of VM-based, dedicated RabbitMQ servers and clusters. App developers can create instances of a RabbitMQ server or cluster using Apps Manager or the Cloud Foundry Command Line Interface tool (cf CLI) and bind these instances to an app. Depending on your service plan, a service instance may be associated with a single, dedicated VM or a set of VMs that includes a RabbitMQ replica set cluster.

Due to the on-demand provisioning on VMs, only existing service instances use infrastructure resources. These resources are released when service instances are destroyed. With on-demand provisioning, the number of service instances is not limited by design.

For clustered data service plans, databases are distributed across multiple infrastructure availability zones (AZs). This enables short failover times and resilience against failures of individual infrastructure hosts or entire AZs.

Current Features

a9s RabbitMQ for PCF includes the following key features:

Feature Description
OnĀ­-demand service instance provisioning a9s RabbitMQ for PCF deploys RabbitMQ instances automatically. Developers can provision a single-VM RabbitMQ server or a multi-VM RabbitMQ replica set using one command.
Service instance isolation Each RabbitMQ server runs on a dedicated VM to ensure bad-neighborhood protection and align with enterprise security requirements.

a9s RabbitMQ for PCF uses Cloud Foundry application security groups (ASGs) to prevent network connections from unauthorized apps.
High availability a9s RabbitMQ for PCF ensures high availability using RabbitMQ replication.

The Consul-based internal DNS system provided by a9s Consul DNS for PCF ensures that the bound app always connects to a working node.
Smoke tests A post-deployment, smoke-test errand runs basic tests against your installation to ensure that it is configured properly.
Service instance capacity upgrade By updating your service plan, you can upgrade the RAM, CPU, and storage capacity for your RabbitMQ instances.
Logging and monitoring Each RabbitMQ service instance provides log messages and RabbitMQ-specific metrics to one or more syslog/graphite endpoints. You can configure the syslog/graphite endpoint to receive logging and monitoring information.
Deployment updater An updater errand updates the stemcell and all provisioned a9s RabbitMQ for PCF service instances to their latest version.

Video Overview of a9s RabbitMQ for PCF

The following video provides an overview of how a9s RabbitMQ for PCF works.

Product Snapshot

The following table provides version and version-support information about a9s RabbitMQ for PCF:

Element Details
Version v0.10.1
Release date April 17, 2017
Software component version v3.6.6
Compatible Ops Manager version(s) v1.7.x, v1.8.x, v1.9.x, v1.10.x
Compatible Elastic Runtime version(s) v1.7.x, v1.8.x, v1.9.x, v1.10.x
IaaS support AWS, OpenStack, and vSphere
IPsec support No


To install and use a9s RabbitMQ for PCF, you must install the following products and tiles:

For more information, see Installing and Configuring a9s RabbitMQ for PCF.

Feedback and Support

The anynines team can help you get started and succeed with a9s RabbitMQ for PCF. Technical support, including a service-level agreement, is available with a commercial license.

If your company has specific RabbitMQ administration policies or configuration best practices, the anynines team is happy to incorporate them. Third-party RabbitMQ support organizations are also welcome to assist.

Contributions are welcome and will be investigated by the anynines team. Please send any bugs, feature requests, or questions to svc.support@anynines.com.


Contact our sales team to learn more about commercial licenses and support.

Create a pull request or raise an issue on the source for this page in GitHub