Messaging Documentation
API Docs
  • Introduction
  • Getting started
    • Transitioning from v2 to v4
  • Message structure
    • Entity messages
      • Message group
      • Action
      • Example messages
    • Configuration messages
      • Message group
      • Action
      • Example messages
    • Financial messages
      • Message group
      • Action
      • Example messages
    • Batch Messages
      • Message group
      • Action
      • Example messages
  • Sample projects
  • Message metrics
  • FAQ
  • SQS - Queues
    • Overview
    • Setting up an SQS message integration
    • SQS queue names
  • SNS - PUB/SUB
    • Overview
    • Setting up an SNS message integration
    • SNS topic names
    • Message attributes
  • 🆕EventBridge
    • Overview
    • Setting up an EventBridge integration
Powered by GitBook
On this page
  • Considerations
  • Setting up a new messaging integration

Was this helpful?

Getting started

PreviousIntroductionNextTransitioning from v2 to v4

Last updated 2 years ago

Was this helpful?

Considerations

A few things to consider and get organized if you are ready to start receiving messages from Rightsline:

  • A Rightsline SQS queue or EventBridge event bus will be populated with every audit event that occurs, so this is best suited for customers who need integrations to a wide variety of data points.

  • SNS messages are much more targeted as the topics are based on a specific char types in Rightsline (e.g. Catalog Item, Deal, etc.) and can further be filtered in the subscription by specific actions (created, updated, deleted), individual user performing the action, template or status of the entity, as well as other .

  • We have updated our security policies in accordance with AWS best practices and require all customers that need to subscribe to SQS or SNS messages to have their own AWS account. You will need to provide us with that account ID in order to set up the correct permissions for all of the resources involved.

Setting up a new messaging integration

First, determine what type of message destination works best for your use case:

  • If you are interested in every type of event across multiple char types, or do not have an AWS account, jump to .

  • If you are only interested in select events or events from a few char types and have an AWS account, jump to .

  • If you have an AWS account and would like to route your messages to multiple AWS services in your account, jump to .

message attributes
Setting up SQS message integration
Setting up SNS message integration
Connect your event bus to Rightsline event bus