feat: aws analytics feature

Type of change

  • Bug Fix
  • Feature
  • Pipeline
  • Test
  • Documentation

Does this introduce a change in the core logic?

  • No
  • Yes

Does this introduce a change in the cloud provider implementation, if so which cloud?

  • AWS
  • Anthos
  • Azure
  • GCP
  • IBM

Does this follow conventional commits spec?

  • No
  • Yes

Have you set the target Milestone?

  • No
  • Yes

Have you set the no-detached-pipeline label?

  • No
  • Yes

Description

This PR introduces the AWS Analytics capability to the Seismic DMS Service. It adds new endpoints, job scheduling logic, and report management for both subproject-level and tenant-level analytics.

Key Changes

  • Added full Analytics section to OpenAPI (job scheduling + listing + connection-string generation)
  • Implemented AWS-side logic for:
    • DynamoDB reads/writes
    • Storage access and connection-string generation
    • Statistics job scheduling
  • Updated configuration and credential handling for AWS deployments
  • Improved internal utilities (logger, storage, credentials, ssmhelper, etc.)
  • Updated scripts such as detect_unused_packages.sh to handle escaped package names correctly

Endpoints Added

  • PUT /analytics/job — create/update job schedule
  • GET /analytics/job — list job schedules
  • GET /analytics/job/{subprojectid} — list subproject reports
  • DELETE /analytics/job/{subprojectid} — delete subproject schedule
  • GET /analytics/job/{subprojectid}/connection-string — generate report download string
  • Tenant-level equivalents:
    • /analytics/tenant/job
    • /analytics/tenant/job/connection-string

Why this change

This introduces scheduled analytics statistics generation and report downloads across AWS deployments - a key feature for OSDU Seismic analytics workflows.

Edited by Hasan Gokce

Merge request reports

Loading