Frequently Asked Questions - CloudAMQP

CloudAMQP offers managed RabbitMQ and LavinMQ servers in the cloud. RabbitMQ and LavinMQ are open source, high throughput message queuing servers. CloudAMQP supplies fully managed servers and clusters, ranging from virtual hosts on a shared cluster to dedicated high performance HA clusters.

CloudAMQP has several monitoring tools that help clients address performance issues automatically and promptly. Alarms can also notify clients when resource consumption crosses critical thresholds.

See our Getting Started Guide. Our popular blog posts RabbitMQ for Beginners and LavinMQ for beginners are also good places to start. Once you have created your account you can start queuing and processing by using any of the guides available here in the docs, depending on platform and language. These tutorials cover the basics of creating messaging applications using CloudAMQP.

Cloud-based messaging increases the speed of getting the application to the market. Developers can focus on the core part of their applications instead of managing and maintaining servers and queueing infrastructure.

Developers who want to focus on the core part of their applications, instead of managing and maintaining servers and queueing infrastructure, are using CloudAMQP.

We have customers in a range from large enterprise businesses and startups to individual hobby developers.

You can change a plan in the console under Edit, but the ability to move between shared plans (Little Lemur and Tough Tiger for RabbitMQ, Loyal Lemming and Elegant Ermine for LavinMQ) and a dedicated plan depends on the broker type.

LavinMQ: You can migrate directly from a shared plan to a single-node dedicated plan via the CloudAMQP console (Edit → change plan). Please note the following important caveats:

• Your cluster will receive a new hostname after the migration. Make sure to update your connection strings accordingly.
• Migration targets single-node dedicated plans only. You can expand to a multi-node cluster afterwards if needed.
• All broker definitions and data are preserved during the migration.

RabbitMQ: Moving from a shared to a dedicated plan is not supported directly via Edit. We recommend that you use queue federation as described in our guide for Cluster migration with RabbitMQ Queue Federation.

For more details, see Migrate between plans.

It depends. If you have a 2+ nodes cluster, there will be no downtime during the migration.

If you have a 1-node server, there will be downtime. How long it will take depends on the length of the queues you have, but it is usually a short downtime. Please note that messages, exchanges, and queues that are not durable and persistent will be lost during the migration.

Yes, but messages have to be published as “persistent” to durable queues for them to survive the upgrade (or any kind of restart). There will, however, be a minute or two of downtime while the instance is being upgraded.

You can delete an instance from the instances list page in the user interface. If you remove an instance, your queues, exchanges, bindings and all data associated with it will be deleted and we will not be able to restore them.

Please navigate to the UI at customer.cloudamqp.com/instance, click Edit next to the instance and select Delete. After the instance is removed, you have the option to pay any outstanding invoice. Once your balance is current, you have the option to delete your Team (account) at customer.cloudamqp.com/team/settings.

Please let us know if you have any questions along the way.

Queue alarms can be triggered to send notification emails to you and your co-workers when the number of messages in a queue reaches a certain threshold for a set amount of time.

Consumers alarms can be triggered to send notification emails to you and your co-workers when the number of consumers for a queue is less than or equal to a set number of consumers, for a set amount of time.

CPU alarms (only for dedicated instances): when the CPU alarm is enabled you will receive a notification email when you are using more than 80% of the available CPU for more than 15 minutes. You can change the level at which the alarm will trigger. It is recommended to enable CPU alarms, which is done through the Control Panel.

Memory alarms (only for dedicated instances): when the Memory alarm is enabled you will receive a notification email when you are using more than 90% of the available memory for more than 15 minutes. The level can be changed. It is recommended to enable Memory alarms, which is done through the Control Panel. Note: this alarm is calculated from how much memory the underlying virtual machine is using, not what RabbitMQ or LavinMQ is using.

Read more in the alarms documentation.

Virtual hosts (vhosts) make it possible to separate applications on one broker. You can isolate users, exchanges, queues, etc. to one specific vhost. You can separate environments, e.g. production to one vhost and staging to another vhost, within the same broker instead of setting up multiple brokers.

vhosts can be added to all dedicated instances. The downside of using a single instance is that there’s no resource isolation between virtual hosts.

No, there are no queue or message limits on our dedicated RabbitMQ plans. Our dedicated plans (Sassy Squirrel and larger) are not artificially limited in any way, the maximum performance is determined by the underlying instance type.

For the limits of LavinMQ dedicated plans, see Plans & Pricing.

See CloudAMQP Service Level Agreement (SLA). LavinMQ instances are covered by the same SLA as RabbitMQ instances.

You will need to take action to migrate to a larger plan or find the reasons for the high memory/CPU usage. Our blog post How to handle and avoid high CPU or Memory usage describes how to handle and avoid high CPU or memory usage. Alarms can be activated to send notifications when you have high CPU or memory usage, information about that can be found in our alarms documentation. The alarms can be activated from the control panel of your instance.

Recommended reading: RabbitMQ Best Practices.

Yes, RabbitMQ plugins can be enabled and disabled from the CloudAMQP Control Panel for dedicated plans, which is Sassy Squirrel and larger, see Plugins. We do support custom plugin installation, send us an email or enter the chat and we will assist you.

All our RabbitMQ plans, shared and dedicated, have protocol support for AMQP 0-9-1, AMQP 1.0, AMQPS, HTTPS, STOMP, MQTT, and WebSockets. Dedicated plans also have support for Web-STOMP.

For LavinMQ, see Which protocols does LavinMQ support?

No, you cannot access the nodes via SSH. Let us know if you need to perform any actions on the server and we will help you.

Yes, by using port 443 and TLS. Download the same rabbitmqadmin version as the RabbitMQ version in your cluster. It can be downloaded from https://your_host.rmq.cloudamqp.com/cli/.

The example below shows how to list exchanges:

rabbitmqadmin --use-tls --tls-ca-cert-file=$CERTIFICATE_LOCATION --host=$CLUSTER_URL --port=443 --username=$USERNAME --password=$PASSWORD --vhost=$VHOST list exchanges

No, rabbitmqctl is only possible to run on the local machine. Use rabbitmqadmin instead, which is better and enabled remotely.

No, lavinmqctl is only possible to run on the local machine.

All multi-node clusters in AWS and Google Cloud have nodes in multiple availability zones and have automatic fail-over.

CloudAMQP does not support nodes in different regions. However, your nodes will be placed in different Availability Zones in AWS, but not in different regions. Let us know if that is a requirement. We can always help you set up a federation between two different nodes, but it’s not always recommended.

There are no limitations in the number of channels per connection on our dedicated plans. We limit all shared plans to 200 channels per connection.

When an instance is marked as impaired by AWS it means that something is wrong with the instance, e.g., the underlying physical hardware was faulty or a piece of faulty network equipment cut off the network.

We automatically restart instances onto new hardware when this happens. All data is safe as long as you have persistent messages and durable queues.

This is not something we or you can prevent, it’s all in the hands of AWS. It does happen but it’s rare. However, a 2-node setup will keep your other node up and running when the first node needs to be replaced.

More information can be found in AWS’s documentation: Status checks for your instances.

See our blog post Amazon VPC Peering with CloudAMQP and the VPC Peering documentation.

Dedicated VPC is available as an extra option for our dedicated plans for $99 per month. Create your cluster in a dedicated VPC, which asks you to select the VPC subnet. Make sure that it does not overlap with any VPC subnets you want to peer with.

As soon as you have created your instance you can go to your AWS console and create a VPC peering request. Necessary details about your CloudAMQP VPC can be found on the VPC tab in the CloudAMQP console.

When you have created the request it can be accepted from the VPC tab in the CloudAMQP console.

If you want to enable VPC features for a current cluster, you can do so by clicking Edit → Enable VPC features in your cluster list. Note that we are unable to disable this feature once enabled.

AWS PrivateLink is set up through VPC Connect on dedicated instances with VPC features enabled. See Pricing for the cost and AWS PrivateLink Setup for configuration instructions.

RabbitMQ and LavinMQ provide two types of federation: exchange and queue federation. A federated exchange can route messages published to an upstream server to a local queue. A federated queue allows a local consumer to receive messages from an upstream queue.

Read more about the RabbitMQ federation plugin, and how to set up federated exchanges, in The RabbitMQ federation plugin.

CloudAMQP is fully integrated with the following platforms:

• Heroku
• Microsoft Azure Marketplace

CloudAMQP is available in the following clouds and regions:

• Amazon Web Services: {"name" => "AF South 1 (Cape Town)", "city" => "Cape Town"}, {"name" => "AP East 1 (Hong Kong) *", "city" => "Hong Kong"}, {"name" => "AP East 2 (Taipei) *", "city" => "Taipei"}, {"name" => "AP NorthEast 1 (Tokyo) *", "city" => "Tokyo"}, {"name" => "AP NorthEast 2 (Seoul) *", "city" => "Seoul"}, {"name" => "AP NorthEast 3 (Osaka)", "city" => "Osaka"}, {"name" => "AP South 1 (Mumbai) *", "city" => "Mumbai"}, {"name" => "AP South 2 (Hyderabad)", "city" => "Hyderabad"}, {"name" => "AP SouthEast 1 (Singapore) *", "city" => "Singapore"}, {"name" => "AP SouthEast 2 (Sydney) *", "city" => "Sydney"}, {"name" => "AP SouthEast 3 (Jakarta)", "city" => "Jakarta"}, {"name" => "AP SouthEast 4 (Melbourne)", "city" => "Melbourne"}, {"name" => "AP SouthEast 5 (Malaysia)", "city" => "Kuala Lumpur"}, {"name" => "AP SouthEast 6 (New Zealand) *", "city" => "Auckland"}, {"name" => "AP SouthEast 7 (Thailand)", "city" => "Bangkok"}, {"name" => "CA Central 1 (Canada) *", "city" => "Montréal"}, {"name" => "CA West 1 (Calgary)", "city" => "Calgary"}, {"name" => "EU Central 1 (Frankfurt) *", "city" => "Frankfurt"}, {"name" => "EU Central 2 (Zurich)", "city" => "Zurich"}, {"name" => "EU North 1 (Stockholm) *", "city" => "Stockholm"}, {"name" => "EU South 1 (Milan)", "city" => "Milan"}, {"name" => "EU South 2 (Spain)", "city" => "Aragón"}, {"name" => "EU West 1 (Ireland) *", "city" => "Dublin"}, {"name" => "EU West 2 (London) *", "city" => "London"}, {"name" => "EU West 3 (Paris) *", "city" => "Paris"}, {"name" => "IL Central 1 (Tel Aviv)", "city" => "Tel Aviv"}, {"name" => "ME Central 1 (UAE)", "city" => "Dubai"}, {"name" => "ME South 1 (Bahrain) *", "city" => "Bahrain"}, {"name" => "MX Central 1 (Mexico)", "city" => "Querétaro"}, {"name" => "SA East 1 (São Paulo) *", "city" => "São Paulo"}, {"name" => "US East 1 (Northern Virginia) *", "city" => "Northern Virginia"}, {"name" => "US East 2 (Ohio) *", "city" => "Columbus"}, {"name" => "US West 1 (Northern California) *", "city" => "Northern California"}, {"name" => "US West 2 (Oregon) *", "city" => "Oregon"}
• DigitalOcean: {"name" => "Amsterdam 3", "city" => "Amsterdam"}, {"name" => "Bangalore 1", "city" => "Bangalore"}, {"name" => "Frankfurt 1", "city" => "Frankfurt"}, {"name" => "London 1", "city" => "London"}, {"name" => "New York 3", "city" => "New York"}, {"name" => "San Francisco 3", "city" => "Northern California"}, {"name" => "Singapore 1", "city" => "Singapore"}, {"name" => "Sydney 1", "city" => "Sydney"}, {"name" => "Toronto 1", "city" => "Toronto"}
• Google Compute Engine: {"name" => "Asia East 1 (Taiwan) *", "city" => "Taiwan"}, {"name" => "Asia East 2 (Hong Kong)", "city" => "Hong Kong"}, {"name" => "Asia Northeast 1 (Tokyo)", "city" => "Tokyo"}, {"name" => "Asia Northeast 2 (Osaka)", "city" => "Osaka"}, {"name" => "Asia Northeast 3 (Seoul)", "city" => "Seoul"}, {"name" => "Asia South 1 (Mumbai)", "city" => "Mumbai"}, {"name" => "Asia South 2 (Delhi)", "city" => "Delhi"}, {"name" => "Asia Southeast 1 (Singapore)", "city" => "Singapore"}, {"name" => "Asia Southeast 2 (Jakarta)", "city" => "Jakarta"}, {"name" => "Australia Southeast 1 (Sydney)", "city" => "Sydney"}, {"name" => "Australia Southeast 2 (Melbourne)", "city" => "Melbourne"}, {"name" => "Europe Central 2 (Warsaw)", "city" => "Warsaw"}, {"name" => "Europe North 1 (Finland)", "city" => "Finland"}, {"name" => "Europe North 2 (Sweden)", "city" => "Stockholm"}, {"name" => "Europe Southwest 1 (Madrid)", "city" => "Madrid"}, {"name" => "Europe West 1 (Belgium) *", "city" => "Belgium"}, {"name" => "Europe West 10 (Berlin)", "city" => "Berlin"}, {"name" => "Europe West 12 (Turin)", "city" => "Turin"}, {"name" => "Europe West 2 (London)", "city" => "London"}, {"name" => "Europe West 3 (Frankfurt)", "city" => "Frankfurt"}, {"name" => "Europe West 4 (Netherlands)", "city" => "Netherlands"}, {"name" => "Europe West 6 (Zürich)", "city" => "Zurich"}, {"name" => "Europe West 8 (Milan)", "city" => "Milan"}, {"name" => "Europe West 9 (Paris)", "city" => "Paris"}, {"name" => "Me Central 1 (Doha)", "city" => "Doha"}, {"name" => "Me Central 2 (Dammam)", "city" => "Dammam"}, {"name" => "Me West 1 (Tel Aviv)", "city" => "Tel Aviv"}, {"name" => "North America Northeast 1 (Montréal, Canada)", "city" => "Montréal"}, {"name" => "North America Northeast 2 (Toronto, Canada)", "city" => "Toronto"}, {"name" => "South America East 1 (São Paulo)", "city" => "São Paulo"}, {"name" => "South America West 1 (Santiago)", "city" => "Santiago"}, {"name" => "US Central 1 (Iowa) *", "city" => "Iowa"}, {"name" => "US East 1 (South Carolina) *", "city" => "South Carolina"}, {"name" => "US East 4 (North Virginia)", "city" => "Northern Virginia"}, {"name" => "US East 5 (Columbus)", "city" => "Columbus"}, {"name" => "US South 1 (Dallas, Texas)", "city" => "Dallas"}, {"name" => "US West 1 (Oregon)", "city" => "Oregon"}, {"name" => "US West 2 (Los Angeles)", "city" => "Los Angeles"}, {"name" => "US West 3 (Salt Lake City)", "city" => "Salt Lake City"}, {"name" => "US West 4 (Las Vegas)", "city" => "Las Vegas"}
• Azure: {"name" => "Australia Central", "city" => "Canberra"}, {"name" => "Australia East", "city" => "Sydney"}, {"name" => "Australia Southeast", "city" => "Melbourne"}, {"name" => "Brazil South *", "city" => "São Paulo"}, {"name" => "Canada Central", "city" => "Toronto"}, {"name" => "Canada East", "city" => "Quebec City"}, {"name" => "Central India", "city" => "Pune"}, {"name" => "Central US", "city" => "Iowa"}, {"name" => "Chile Central", "city" => "Santiago"}, {"name" => "East Asia", "city" => "Hong Kong"}, {"name" => "East US *", "city" => "Northern Virginia"}, {"name" => "East US 2 *", "city" => "Northern Virginia"}, {"name" => "France Central", "city" => "Paris"}, {"name" => "Germany West Central", "city" => "Frankfurt"}, {"name" => "Indonesia Central", "city" => "Jakarta"}, {"name" => "Israel Central", "city" => "Tel Aviv"}, {"name" => "Italy North", "city" => "Milan"}, {"name" => "Japan East", "city" => "Tokyo"}, {"name" => "Japan West", "city" => "Osaka"}, {"name" => "Korea Central", "city" => "Seoul"}, {"name" => "Korea South", "city" => "Busan"}, {"name" => "Malaysia West", "city" => "Kuala Lumpur"}, {"name" => "Mexico Central", "city" => "Querétaro"}, {"name" => "New Zealand North", "city" => "Auckland"}, {"name" => "North Central US", "city" => "Chicago"}, {"name" => "North Europe", "city" => "Dublin"}, {"name" => "Norway East", "city" => "Oslo"}, {"name" => "Poland Central", "city" => "Warsaw"}, {"name" => "Qatar Central", "city" => "Doha"}, {"name" => "South Africa North", "city" => "Johannesburg"}, {"name" => "South Central US", "city" => "San Antonio"}, {"name" => "Southeast Asia", "city" => "Singapore"}, {"name" => "South India", "city" => "Chennai"}, {"name" => "Spain Central", "city" => "Madrid"}, {"name" => "Sweden Central *", "city" => "Gävle"}, {"name" => "Switzerland North", "city" => "Zurich"}, {"name" => "UAE North", "city" => "Dubai"}, {"name" => "UK South", "city" => "London"}, {"name" => "UK West", "city" => "Cardiff"}, {"name" => "West Central US", "city" => "Wyoming"}, {"name" => "West Europe *", "city" => "Amsterdam"}, {"name" => "West India", "city" => "Mumbai"}, {"name" => "West US *", "city" => "Northern California"}, {"name" => "West US 2", "city" => "Washington"}, {"name" => "West US 3", "city" => "Phoenix"}
• Scaleway: {"name" => "Paris *", "city" => "Paris"}, {"name" => "Amsterdam *", "city" => "Amsterdam"}, {"name" => "Warsaw *", "city" => "Warsaw"}

* Available regions for shared instances are marked with an asterisk.

Your CloudAMQP instance is created in the same cloud and region as your Heroku account. If your application is located in AWS us-east-1, then your CloudAMQP instance is created in the same one.

Web-STOMP is a plugin to RabbitMQ which exposes a WebSockets server (with fallback) so that web browsers can communicate with your RabbitMQ server/cluster directly. Full information about Web-STOMP can be found on our STOMP over WebSockets page or at RabbitMQ.

The Web-STOMP plugin can be enabled on all dedicated plans (launched after June 2014).

The Web-STOMP plugin can be enabled on all dedicated plans (launched since June 2014).

Yes. See the New Relic V3 metrics integration.

The length of the log in CloudAMQP is size-based, meaning that it can vary in size, but we can ensure that the log will be stored at least six weeks back in time.

Logs can also be sent to external log aggregators (like Loggly and Papertrail) where they can be stored for a specified amount of time, see Logs & Metrics Integrations.

We do support TLS (SSL). In most clients it is easy to use TLS, just replace amqp:// with amqps:// in the URL. To force TLS for all clients, use the firewall to close the AMQP port (keep AMQPS).

All servers are configured with server certificates signed by a CA found in your default trust store.

RabbitMQ servers come with TLS version 1.2 and 1.3 enabled. Older versions can be enabled by request.

More details are found in the RabbitMQ TLS documentation and the LavinMQ TLS documentation.

Note: TLS will only secure messages during the transport. What we recommend for highly sensitive information (HIPAA, PCI etc) is that you encrypt your message bodies on your side and that you have a shared key between your publishers and your consumers.

We normally recommend using TLS with a server-side cert for encryption and then username/password authentication. It is possible to use client certificates, but it’s not that easy to maintain a CA in terms of proper certificate generation, etc. We normally advise against it as the security benefits are questionable.

If you want to use client certificates we can help you install the public part of the CA on the server and enable peer verification, but you have to manage the certificate generation yourself.

All servers are using certificates issued by Let’s Encrypt. Most operating systems and browsers come with the Let’s Encrypt root certificates built-in, read more at letsencrypt.org/certificates.

The root certificate CloudAMQP servers are using is ISRG Root X1. If you need, you can download it directly from letsencrypt.org/certs/isrgrootx1.pem or crt.sh.

Your server certificate is renewed seamlessly approximately every two months.

AMQP messages are just byte arrays, you can send anything, encrypted or not.

Yes, for dedicated instances in AWS, Azure and Google Cloud.

A firewall lets you restrict access to your cluster so that only your servers will have access. You can also set up different ports for different ranges, so, for example, your servers can access port 5672 (AMQP), but the management interface is still open to all.

Configure a firewall for your cluster directly from our UI. You can specify an IP range and decide which ports should be opened for that range. All other ports to your instance will be closed. See Firewall settings.

One message is counted as consumed when a message is published from your service to the broker (RabbitMQ or LavinMQ) or when one message is consumed from the broker.

If it feels like you are publishing/consuming fewer messages than specified in your CloudAMQP console and you are using Celery, please check if you have disabled Celery events. Celery recommended settings can be found in our Getting started with Celery guide. Have a look at CELERY_SEND_EVENTS, --without-gossip, --without-mingle and --without-heartbeat.

If you are not using Celery, send us an email and we will have a look at your instance.

The reset is performed the first day every month.

You will get warnings via email when you have used 70 and 100 percent of your allowed usage. With max connections you will be unable to establish new connections, existing connections are not affected.

It is only possible to manage users, virtual hosts and permissions on dedicated plans. For RabbitMQ, a dedicated plan is Sassy Squirrel or any plan larger than Sassy Squirrel.

You are allowed a maximum of 49 free instances. If you need more instances, please upgrade to one of our paid plans. Customers with at least one paid instance are allowed a maximum of 650 free instances.

Little Lemur (RabbitMQ) and Loyal Lemming (LavinMQ) instances that are abandoned/not used during the latest two months will be deleted. This will only happen if you haven’t published or subscribed one single message during that time.

You will receive a warning email before the instance is deleted, from where you have the option to wake up the instance.

Each plan includes a certain amount of free data transfer which can be calculated as 30% of the team spend each month. Teams that use more than these limits may be subject to additional charges. In the event of overages during a billing cycle, customers will have 30 days to resolve the issue. If no adjustments are made, additional traffic charges will be applied to subsequent invoices. See the Terms of Service.

Billing occurs at the end of each month, and you are only charged for the time an instance has been available to you. As soon as you delete the instance you won’t be charged for it anymore, i.e. if you had a Big Bunny (for $99/month) running for 15 days, then you will only be charged $49.50.

You also have the option to prepay an amount that suits your needs. If you’d like to avoid lots of small transactions, then prepayment is for you. A prepayment can be made for one to several months in advance. A prepayment is valid for 1 year, then it expires.

A customer subscribing to our plan Big Bunny equalling $99/month can choose to make a prepayment of 12 × $99 (and then skip being charged on a monthly basis for one whole year). The prepayment covers all plans the customer has on their account. So let’s say that the customer in the example would add another Big Bunny plan to their account on month five, then the prepayment will cover both plans for three more months. After that, the customer’s prepayment will have been fully spent.

You can pay with VISA, Mastercard, American Express, Maestro, JCB, Diners Club or Invoice/transfer. Contact us at billing@cloudamqp.com if you require invoicing. Payment options can be found under Billing information in the Control Panel. Please note that we don’t accept checks.

No discounts are available at this time.

No. There is no shipping cost since the service is shipped electronically.

No. The service is non-returnable.

You can choose to pay through credit card (due on charge date) or via wire transfers (NET15). If you would like us to enable manual invoicing via wire transfer, send us an email once you have added all information and we will enable it for you. Please note that we don’t accept checks.

Email sales@cloudamqp.com to receive an official quote. Include what plan you want, if the quote should include VPC or not, and the subscription period.

The service will be provided off-premise in a data center and region chosen on behalf of the customer. The data centers and regions currently provided can be found on the CloudAMQP Plans & Pricing page.

Our billing is pro-rated, which means that our customers only pay for the time the service has been available to them and that the payment is done the month after delivery. Thus, you won’t receive your first invoice when the account has been created, you will receive it at the beginning of the upcoming month.

No. Our customers often change their plan while they are using our service, therefore it’s not convenient to pay for a year upfront. However, we do allow prepayments with credit. If you are a paying customer contact our customer support to activate prepayment. For more information, see Prepayments on CloudAMQP.

No. We don’t need any documents with signatures from you.

No. To safeguard customer data, active subscriptions aren’t deleted. For example, resellers that provide us with a PO for two months of the Happy Hippo plan are responsible for deleting the plan after the subscription expires. Otherwise, you will be charged for the extra time your data remains on the system.

It’s best to extend the current PO. If you need to have two separate POs for the subscriptions, you need to open a new account in order to make the subscriptions be billed separately.

1. Go to customer.cloudamqp.com/login and enter your email address. Fill out all the information in the billing section, such as billing address, email, etc. Please note that it’s important that we have your billing information registered and not the end-user information since you are our direct customer and not the end-user.
2. The PO number can be specified in the billing section under “billing notes”. Or send it to us, and we will add it for you.
3. You are free to create and delete instances once the billing information is set up. It’s up to you and the end-customer to decide who of you will create the subscription specified in the PO.
4. Invite the end-customer to the account via customer.cloudamqp.com/team so that they can start using the service.
5. Change the role of the person that created your account to “Billing Manager”. By doing so, you can access all invoices of the account and update the billing information, but you will not be able to edit the customer’s subscription. For more information, see Manage instance access with Access Control List (ACL).

First of all, make sure that your tasks do not take a longer time to perform on the client-side than the timeout setting. The error could also indicate a network glitch or that the server or clients are overloaded and don’t get to send heartbeats in time.

All CloudAMQP servers implement sensible TCP keepalive so AMQP heartbeats are not necessary. Therefore, we recommend turning heartbeats off and rely on the underlying TCP keepalive. It’s about the same thing but on the TCP/kernel level instead of on the protocol level. See Heartbeat.

If you are getting a ReferenceError in the RabbitMQ Management UI, usually after upgrading RabbitMQ, go ahead and clear the cache of your web browser and the error should be gone.

Yes. See CloudAMQP and General Data Protection Regulation (GDPR).

No separate agreement is required. Our Data Processing Agreement (DPA) for GDPR is an exhibit to our Terms of Service. Thus, our business relationship is automatically covered by a DPA when signing up for an account.

You have the right to see what personal information 84codes AB holds about you. You are entitled to be given a description of the information, what we use it for, who we might pass it onto, and any information we might have about the source of the information.

A subject access request should be made via email to compliance@cloudamqp.com.

As the data controller, you decide where you want to host your data by choosing the data center and region. The data will not leave that region unless you choose to move it. In CloudAMQP’s role as data controller, we may collect and store contact information, such as email address, and physical address, when customers sign up for our services or seek support help.

Your personal customer data (email and billing information) is stored in the US.

We are proud to be compliant with SOC 2 by AICPA. We have been audited against the Security (common criteria) and Availability Trust Services Criteria.

Our SOC 2 Type 2 report can be obtained from our Trust Center. See Security and Compliance.