Choosing the Cloud Your Queues Run On

IronMQ is available on multiple cloud hosts, so your queue can run in the same infrastructure your app does. This saves time on latencies and allows you to spread your queues across multiple clouds, if desired, to maximize your queues' availability.

Each of the official IronMQ client libraries allows you to change a configuration setting to set the host the library connects to. Changing your cloud is as simple as selecting the host you want.

Cloud Host
AWS US-EAST mq-aws-us-east-1.iron.io
AWS EU-WEST mq-aws-eu-west-1.iron.io
Rackspace ORD mq-rackspace-ord.iron.io
Rackspace LON mq-rackspace-lon.iron.io
Rackspace DFW Pro Plans Only - Email Support

Alternative domains can be found here in case of dns failures.

NOTE: Beanstalkd is currently not supported on Rackspace. Please use one of our HTTP clients if you are on Rackspace.

Check your library's documentation for information on switching the host within the library.

Do we not support your cloud of choice? Let us know, and we'll try to add support for it.

Setting Host

It is useful to quickly change your host in cases where your region has gone down.

If want to set the Host, Post, and Protocol specifically, simply include those keys in that project's iron.json file:

iron.json
{
  "project_id": "PROJECT ID HERE",
  "token": "YOUR TOKEN HERE"
  "host":"mq-aws-us-east-1.iron.io"
}
iron.json
{
  "project_id": "PROJECT ID HERE",
  "token": "YOUR TOKEN HERE"
  "host":"mq-rackspace-lon.iron.io"
}
iron.json
{
  "project_id": "PROJECT ID HERE",
  "token": "YOUR TOKEN HERE"
  "host":"mq-aws-eu-west-1.iron.io"
}