AMQP (RabbitMQ) Destination
Install
See the Install guide for the full setup, including Windows PowerShell.
curl -fsSL https://install.skippr.io/install.sh | shClick to copyPublishes records as JSON messages to an AMQP exchange.
Configuration
yaml
warehouse:
kind: amqp
connection_string: ${AMQP_CONNECTION_STRING}
exchange: events
routing_key: output| Field | Default | Description |
|---|---|---|
connection_string | (required) | AMQP connection URI |
exchange | (required) | Exchange name |
routing_key | "" | Routing key |
exchange_type | direct | Exchange type (direct, fanout, topic, headers) |
Authentication
Authentication is provided through the AMQP connection URI. For security best practices, we strongly advise against storing the connection string in skippr.yaml. Use environment variable interpolation instead: replace the connection_string value with your own ${ENV_VAR} reference.
The relevant part of skippr.yaml looks like this:
yaml
warehouse:
kind: amqp
connection_string: ${AMQP_CONNECTION_STRING}Set the env var before running skippr:
macOS / Linux
bash
export AMQP_CONNECTION_STRING="amqp://guest:guest@localhost:5672"Windows PowerShell
powershell
$env:AMQP_CONNECTION_STRING = "amqp://guest:guest@localhost:5672"Windows Command Prompt
cmd
set AMQP_CONNECTION_STRING=amqp://guest:guest@localhost:5672Permissions or Network Requirements
The AMQP user must be allowed to connect to the broker and publish to the selected exchange with the configured routing key.
Troubleshooting
| Symptom | Fix |
|---|---|
| authentication or connection failures | Verify the AMQP URI, broker hostname, port, and vhost permissions. |
| messages are not routed | Check the exchange name, exchange type, routing key, and downstream bindings. |
Next steps
- Pair this destination with a source from Source Connectors.
- See Quick Start for the recommended warehouse evaluation paths.
Install
See the Install guide for the full setup, including Windows PowerShell.
curl -fsSL https://install.skippr.io/install.sh | shClick to copy