Reduce Nucleus Configuration Bucket Sprawl

[jordanpadams]

User Story

As a Nucleus operator, I want configuration storage consolidated so that we do not require a separate S3 bucket for every PDS node.

Problem

Nucleus currently provisions one configuration bucket per node. The configuration data does not appear to require node-level bucket isolation, and this pattern creates unnecessary bucket sprawl and operational overhead as additional nodes and deployments are added.

Desired Outcome

Evaluate and implement a simpler configuration storage model, preferably using a shared Nucleus configuration bucket with node-specific prefixes, unless there is a technical or security requirement that necessitates separate buckets.

For example:

nucleus-config/
  atm/
  geo/
  img/
  ppi/
  sbn/
  ...

Acceptance Criteria

• Document why separate configuration buckets are currently required, if applicable.
• Determine whether node configuration can safely use a shared bucket with node-specific prefixes.
• Update Nucleus/Terraform configuration to eliminate unnecessary per-node buckets.
• Preserve appropriate IAM isolation between nodes/configurations where needed.
• Verify existing Nucleus deployments continue to function with the revised model.