Terragrunt-based deployment of Dev OpenSearch collection for new streaming log format for harvest (registry-loader)

[ramesh-maddegoda]

Are you sure this is not a new requirement or bug?

No

Task Type

Sub-task

💡 Description

To support the ingestion of the new common streaming log format (one log per product) and ensure the registry loader is "Cloud Ready" for Nucleus, we need to provision an OpenSearch Serverless collection in MCP Dev with latest Registry Changes. This ensures we can safely test routing single-product log lines from CloudWatch into OpenSearch.

This task will utilize new Terragrunt setup.

Acceptance Criteria
[ ] A separate, dedicated OpenSearch Serverless collection with latest registry changes is successfully deployed via Terragrunt.
[ ] The environment successfully ingests the new common streaming log format (one product per CloudWatch line).
[ ] OpenSearch Dashboard tracking visualizations can be built cleanly on top of the new index mapping.

[tloubrieu-jpl]

For that purpose we need to configure a new deployment in the terragrunt confiogiration and apply it in the AWS dev account.