Cloud discovery
Cloud discovery lets an agent inventory your AWS resources and turn them into monitors for you, so you don’t have to add each endpoint by hand.
What it discovers
Section titled “What it discovers”An agent with AWS access lists, from the AWS API:
- Load balancers — ALBs and NLBs, with their ports and tags.
- EC2 instances — with public/private IPs, VPC, and tags.
- RDS databases — with their endpoint, port, engine, and tags.
Discovery is AWS only today. (There is no Kubernetes discovery, despite older design notes — an agent discovers the three AWS resource kinds above.)
Requirements
Section titled “Requirements”- An enrolled agent that can reach the AWS API, configured with AWS credentials (an IAM role or keys) and the region(s) to scan.
- Cloud discovery is available on every plan — there’s no separate entitlement to turn on.
From resources to monitors
Section titled “From resources to monitors”You control what becomes a monitor with match rules. Each rule matches resources by a tag or attribute (equals, one-of, exists, or a regex) and maps a match to a monitor — its type, port, and name. A live preview shows exactly what would be created before you commit.
Then choose how resources become monitors:
- Manual — review the discovered resources and adopt the ones you want, one by one.
- Auto-adopt — turn on a per-agent toggle and matching resources become monitors automatically. Auto-adoption stops at your plan’s monitor limit, so it never creates more than you’re allowed.
When a later scan no longer sees a resource, CuliPulse marks it closed rather than deleting it, so you keep the history.
Local network scan
Section titled “Local network scan”Separately from AWS discovery, an agent can scan a local network range (a CIDR block) on ports you specify and report the open TCP services it finds — useful for taking stock of what’s running on an internal network. This is configured on the agent itself and is distinct from cloud discovery above.