Integration troubleshooting
If a connection isn’t behaving as expected, find your symptom below. Each scenario has a likely cause and a fix. For general connection management, see Manage your integrations.
Costs look doubled
Section titled “Costs look doubled”Usually the same account is connected twice — a linked account was also connected standalone, so its spend is counted under both. Remove the duplicate connection and the numbers reconcile. See remove a connection.
No data yet after connecting
Section titled “No data yet after connecting”Your first analytics land the same day you connect, but a full backfill takes time. If you see nothing at all, confirm the CUR is delivering with Daily granularity in Parquet format, and that the role ARN and ExternalId were entered correctly.
Connected but costs look partial or missing
Section titled “Connected but costs look partial or missing”Check that your CUR is complete and that its granularity is Daily — Hourly or Monthly CURs need conversion. Low CUR completeness also shows up as lower tag coverage.
Role or permission error
Section titled “Role or permission error”The trust policy or ExternalId doesn’t match what CloudQuell expects. Re-copy the exact trust policy and inline read-only policy CloudQuell shows you and apply them to the role, then retry. Full details are in Connect your AWS account.