Documentation
Cloud and controllers (AWS, Azure, Mist AI, Aruba Central, Meraki)
Connecting REAP to Cloud and controllers (AWS (opens in a new tab), Azure (opens in a new tab), Mist AI (opens in a new tab), Aruba Central (opens in a new tab), Meraki (opens in a new tab)): prerequisites, permissions, setup, what is read and written, troubleshooting.
Overview
Cloud network context and controller-managed estates as first-class sources.
Prerequisites
- Read-only cloud roles/keys (AWS (opens in a new tab) IAM role, Azure (opens in a new tab) app registration); controller API keys with read scope
- GCP (opens in a new tab) network discovery: not available today; GCP as a hosting location by arrangement
Permissions requested
| Scope | Permission | Why |
|---|---|---|
| AWS (opens in a new tab) | Read-only on VPC, TGW, route tables, security groups minimum policy | Cloud network context |
| Azure (opens in a new tab) | Reader on VNets, route tables, NSGs minimum role | Cloud network context |
| Mist AI (opens in a new tab) · Aruba Central (opens in a new tab) · Meraki (opens in a new tab) | Read-only organization/site API key | Inventory, events, client context |
Setup
- Create the role/key with the minimum policy.
- In REAP: Integrations → Cloud/Controller → credentials, scope.
- Verify that hybrid paths (site ↔ cloud) appear in topology.
What REAP reads
- Cloud routing/security constructs; controller inventory, events and health
What REAP writes
- Nothing
Troubleshooting
| Symptom | Likely cause | Check |
|---|---|---|
| Paths missing | Scope limited to some accounts/orgs | Extend scope |
Changelog
- September 2026 · page created (draft).
Engineering to confirm
- Minimum IAM/RBAC policies per cloud; controller API scopes
Last reviewed: October 7, 2026 (draft) · Owner: solutions engineering · Corrections: security@reapnet.ai