OrcLink
← Help Center

Warehouse

Amazon SQS queue

SendMessage: the same events and bodies as a webhook endpoint.

Built, not yet tested liveBuilt. Not yet tested against a live Amazon SQS queue account.

Live: shipped in OrcLink's production release before this one. Built, not yet tested live: built and tested with sample data, not yet run against a live account of the vendor. Coming soon: listed, not available to connect yet.

How to connect

  • Data out > Streams: name, the queue URL, and an access key allowed sqs:SendMessage only (stored encrypted). Pick the events.

What OrcLink reads

  • Nothing from the destination.

What OrcLink writes back

  • Each event you pick (the webhook events) as a message: the same body as a webhook delivery, with an event_type message attribute. A FIFO queue gets the workspace as message group and the event id as deduplication id.

Never stored

  • Your credentials in clear: stored encrypted (AES-256-GCM) and never shown again.

Known limits

  • The same events, bodies, HIPAA labels and opt-in as a webhook endpoint; a pause after 20 failed deliveries in a row.
  • Deliveries are sent by the job worker, while the scheduled job jobs runs (your OrcLink operator schedules it).
  • HIPAA mode: it runs only when the workspace has accepted OrcLink's BAA and an owner has recorded a BAA with Amazon Web Services.
  • It runs only while the person who set it up (or last started it) can still manage the workspace.
  • Plans: event streams need the Medium plan or above.