Skip to content

Document requirements for self-managed mqs infra #561

@alexluong

Description

@alexluong

Following #560, we need to have super clear documentation on what we expect regarding self-managed mqs infra. We need to clarify the 2 main concerns from Outpost POV which are visibility timeout & retry policy, what to consider, and how to configure Outpost correctly to match with the settings.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Status

    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions