What
The two services default `AWS_REGION`/`AWS_S3_REGION` to different values:
- `services/inh-ingestion-svc/src/config/settings.py`: `s3_region: str = Field("nbg1", alias="AWS_REGION")` (Hetzner region code)
- `services/inh-public-api-svc/src/config/settings.py`: `aws_s3_region: str = Field(default="eu-central-1", description="S3 region")`
Both services read/write the same S3-compatible bucket (`inherent-documents`), so their region defaults should describe the same storage backend.
Why this matters
In real deployments both are presumably overridden by env vars, so this is likely latent rather than actively broken — but the defaults disagreeing is a drift risk: a fresh/local/dev environment that doesn't set `AWS_REGION`/`AWS_S3_REGION` explicitly will have the two services pointed at different regions for what should be the same bucket.
Ask
Confirm which region is actually correct for the shared bucket (Hetzner `nbg1` vs AWS `eu-central-1`) and align both services' defaults to match.
Found during a hardcoded-config-value sweep starting from `services/inh-public-api-svc/src/config/`.
What
The two services default `AWS_REGION`/`AWS_S3_REGION` to different values:
Both services read/write the same S3-compatible bucket (`inherent-documents`), so their region defaults should describe the same storage backend.
Why this matters
In real deployments both are presumably overridden by env vars, so this is likely latent rather than actively broken — but the defaults disagreeing is a drift risk: a fresh/local/dev environment that doesn't set `AWS_REGION`/`AWS_S3_REGION` explicitly will have the two services pointed at different regions for what should be the same bucket.
Ask
Confirm which region is actually correct for the shared bucket (Hetzner `nbg1` vs AWS `eu-central-1`) and align both services' defaults to match.
Found during a hardcoded-config-value sweep starting from `services/inh-public-api-svc/src/config/`.