Skip to content

TASK: Define Amazon OpenSearch architecture for UAT and PROD #97

Open

Description

@ramioooz

Parent: STORY: Implement centralized logging with OpenSearch

Define how the SIT OpenSearch design maps to Amazon OpenSearch Service for hosted environments.

Acceptance criteria:

  • UAT and PROD use isolated OpenSearch domains or equivalent isolation boundaries.
  • Fluent Bit or a managed ingestion layer routes logs without application changes.
  • IAM, VPC networking, TLS, encryption, retention, backup, monitoring, and cost are considered.
  • Failure handling prevents logging outages from blocking banking transactions.
  • The structured logging field contract and representative operational searches remain consistent across environments.
  • Version compatibility and upgrade responsibilities are documented.
  • The decision is recorded in an architecture decision record.

Activity

  1. added theissue type on Aug 2, 2026
  2. self-assigned this
    on Aug 30, 2026
  3. ramioooz commented on Aug 31, 2026

    @ramioooz
    MemberAuthor

    Deferred by the current delivery decision: AWS/UAT/PROD deployment and managed OpenSearch implementation will remain planned work in Sprint 7 until the remaining local SIT and core-domain work is complete. The issue remains in Sprint 7 and Backlog; no implementation PR is required now.

  4. ramioooz commented on Aug 31, 2026

    @ramioooz
    MemberAuthor

    Decision recorded: Amazon OpenSearch UAT/PROD architecture is deferred with AWS deployment work. The local SIT OpenSearch stack remains in scope; revisit the managed AWS design after the local SIT/core-domain wave.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions