Supported Clouds and Requirements
DevOps Genie supports AWS, GCP, and Azure for cloud-account scanning and compliance visibility. You can connect one provider first and add more later.
Cloud account requirements
| Provider | What DevOps Genie needs | Where to start |
|---|---|---|
| AWS | Role ARN with your organization-specific External ID. | Connect AWS |
| GCP | Service account JSON with read-oriented project access. | Connect GCP |
| Azure | App registration credentials and Reader access to the subscription. | Connect Azure |
Agent requirements
The DevOps Genie Agent is optional. If you deploy it, you need:
- Kubernetes cluster access.
- Helm 3.
- Permission to install the chart and its required resources.
- DevOps Genie API key from the product.
- Image pull credentials from DevOps Genie.
- VCS access if you want pull-request based automation.
Supported product areas
| Area | AWS | GCP | Azure |
|---|---|---|---|
| Cloud scanning | Supported | Supported | Supported |
| Compliance posture | Supported | Supported | Supported |
| Security findings | Supported | Supported | Supported |
| Agent-powered automation | Supported when required integrations are configured | Supported when required integrations are configured | Supported when required integrations are configured |
Choosing a first cloud
Start with the cloud account that has the most urgent visibility need. A production account is often useful, but you can also begin with a sandbox account if your security team wants to validate the access pattern first.