Unable to bump to latest Observability DA in RAG stack due to auth policy scoping changes #225
Description
The stack definition of current standard (OCP) RAG stack does the following:
- Create Key Protect instance in KMS DA
- Create KMS key in the instance in OCP landing zone
- Creates a COS instance in Observability DA
- Re-uses that COS instance for OCP landing zone (here)
- Landing zone creates a COS bucket in the COS instance using the KMS key it create.
Since that was created, the Observability DA has been updated so the COS to KMS s2s auth policy is now scoped to the exact KMS key. So that means the auth policy that the Observability DA created before, no longer works for landing zone because landing zone creates its own key.
This now blocks us from updating the stack to consume the latest Observability DA. And because the landing zone is not using the TIM COS module to create buckets or auth policies, it will require some refactoring in landing zone to get this to work. To be consistent with all our other modules / DAs, the DA that creates the bucket should also create the required KMS auth policy. So that would mean refactoring the landing zone DA to create a COS to KMS auth policy scoped to the KMS key created by landing zone before creating the bucket