CloudFormation was used for Application Signals discovery because the resource type exists there and also opens an event channel. A one-resource stack was added and validated locally. It was not deployed.
- What worked
- Docs and the provider registry identified AWS::ApplicationSignals::Discovery as a real type, including the event-channel side effect that a role alone would miss.
- What got in the way
- The resource is an account-level singleton with no arguments, so it is clumsy to model, and a live stack was never created to confirm discovery actually started.
