Message Aid

Introduction

Agents

enterprise

For our customers that need a higher level of compliance Message Aid offers a means to run our agent in your own network. This allows you to connect to brokers that might be behind a firewall, as well as write the message bodies to your own configured Message Locker. The message payload would never leave your network. Only the message meta data would be stored in Message Aid's own databases.

Network Access

External

The Agent that is running inside your network will communicate back to Message Aid via AMQPS (the TLS protected version of AMQP). The agent will open the connection outbound, so you won't need to open any inbound ports on your network.

GeoAddressIPsPort
USagents.us.messageaid.com44.218.249.215, 3.92.156.375671

Internal

Inside of your network the Agent will need access to your message brokers. Each type of broker is listed below.

RabbitMQ

Secure PortInsecure PortReason
56715672This is the port used for sending and receiving message data from the RabbitMQ broker
44380This is the port used for inspecting RabbitMQ metadata

Installation

Installing an Agent in your cloud can be accomplished several ways based on your specific network needs.

Configuration

To configure the agent, you will need to provide a connection string back to Message Aid. This can easily be provided with a connection string:

MESSAGEAID__CONNECTION_STRING=amqps://$USERNAME:$PASSWORD@agents.us.messageaid.com/$QUEUE

You can find this on your agent's sidebar

VariablePurpose
UsernameThe username to connect with Message Aid's RabbitMQ Broker
PasswordThe password to connect with Message Aid's RabbitMQ Broker
QueueThis is the queue your agent will listen to for commands.

Debugging

Network Access: to Message Aid

Log into the container or host running the Agent and then run the following telnet command.

> telnet agents.us.messageaid.com 5671

Trying 3.92.156.37...
Connected to agents.us.messageaid.com.
Escape character is '^]'.

Network Access: to the Broker

Log into the container or host running the Agent and then run telnet to check the items

RabbitMQ

We need access to both the AMQPS port and the HTTPS port

> telnet $RABBITMQ_HOST 5671
> telnet $RABBITMQ_HOST 443

Azure Service Bus

We need access to both the AMQPS port and the HTTPS port

> telnet $AZURE_SERVICE_BUS_HOST 5671
> telnet $AZURE_SERVICE_BUS_HOST 443

S3

We need access to the HTTPS port

> telnet $S3_ENDPOINT 443
Previous
Frameworks