Troubleshooting

CloudFormation stack creation failed

Cause: IAM permissions issue or stack already exists.

✓ Fix: Check CloudFormation events in AWS console. Delete existing stack if name conflicts. Ensure your AWS user has CloudFormation and IAM create permissions.

Requires admin permissions

Scan returns no data

Cause: Selected AWS account has no Cost Explorer data, or IAM role does not have Cost Explorer read permissions.

✓ Fix: Verify the IAM role includes ce:GetCostAndUsage permission. Enable Cost Explorer in AWS console if not activated.

Token validation failed

Cause: Token missing Zone, Zone Analytics, or Account Analytics read permissions.

✓ Fix: Create a new API token in Cloudflare dashboard with Zone: Read, Zone Analytics: Read, Account Analytics: Read permissions.

Requires admin permissions

Signal unavailable from Cloudflare API

Cause: Zone analytics requires Business or Enterprise plan.

✓ Fix: Upgrade Cloudflare plan or check token has analytics access. InfraDesk stores null for unavailable signals — no fake data is generated.

OpenAI validation failed

Cause: Standard API key used instead of Admin API key, or key lacks organisation usage/cost access.

✓ Fix: Create an Admin API key at platform.openai.com/settings/organization/admin-keys with organisation usage and costs access.

Requires admin permissions

No usage data after sync

Cause: Organisation has no recent usage, or key lacks cost API access.

✓ Fix: Verify usage exists in OpenAI dashboard. Check Admin key has organisation-level cost access.

Datadog validation failed

Cause: Wrong site selected, invalid API key, or invalid Application key.

✓ Fix: Double-check selected site matches your Datadog account region (US1, EU, etc.). Verify both API key and Application key are correct.

Requires admin permissions

No monitors returned after sync

Cause: Application key lacks monitor read permissions, or no monitors exist.

✓ Fix: Verify Application key has Monitors: Read permission. Check Datadog monitors exist in the selected account.

Validation failed — API Access List restriction

Cause: Atlas API key is restricted to specific IP addresses. InfraDesk server IP is not in the allowlist.

✓ Fix: Go to Atlas → Access Manager → API Keys → Edit → Add InfraDesk server IP or 0.0.0.0/0 for testing. Note: 0.0.0.0/0 allows all IPs — use only for testing.

Requires admin permissions

No clusters returned

Cause: API key has Organisation Read Only but no projects exist, or key is project-scoped without cluster access.

✓ Fix: Verify API key role is Organisation Read Only or Project Data Access Read Only. Check projects exist in Atlas.