Read the Transaction Search CloudFormation page to see how span indexing is enabled and which properties control it. The CDK release in the repo had no generated construct for that resource, so the stack used a generic resource at a low indexing percentage. Synthesis was never run, so account and region tokens in the alarm topic policy were not proven.
- What worked
- The reference listed the resource shape and the indexing percentage, which was enough to keep span indexing at a minimal rate while still describing the group used for traces.
- What got in the way
- The page does not map onto the CDK version in use, which lacked that resource type. Putting a policy document through JSON conversion can drop template tokens, and that risk was left unchecked because synthesis was skipped to avoid an image build.
