Skip to main content

AWS Verification

Use this checklist to confirm that your AWS integration is healthy and that Cloudaware is ingesting the expected data.

Check Account and Organization Status in Cloudaware​

In Cloudaware, go to Admin (Admin Console):

  1. Select Amazon Web Services → CONFIGURED.
  2. On the Accounts tab:
    • Confirm that each onboarded AWS account shows a green status indicator.
    • Investigate any accounts with red status or validation errors.
  3. If you use AWS Organizations:
    • Open the Organizations tab. Confirm that the organization entry is healthy.
    • Switch to the Accounts tab to confirm that member accounts have a green status indicator.

If errors mention “assume role” or credential issues, see Troubleshooting.

Validate Sample Resources in CMDB​

In Cloudaware CMDB Navigator:

  • Navigate to AMAZON WEB SERVICES → COMPUTE → AWS EC2 Instances.
    • Confirm that a representative set of instances from each onboarded account and region is present.
    • Verify key fields such as account, region, availability zone, instance state, and tags.
  • Navigate to STORAGE, NETWORKING, DATABASE, and any other categories relevant to your environment.
    • Spot‑check that new or recently changed resources in the AWS console appear in Cloudaware after the next discovery run.
  • If you enabled EKS, CloudTrail, or other advanced features, confirm that their corresponding objects appear under the appropriate CMDB categories.

Confirm Freshness of Data​

For selected objects (for example, an EC2 instance or S3 bucket):

  • Check the Created By timestamp in Cloudaware (for initial setup).

    tip

    Allow initial collection latency for as little as 5 minutes or as long as 24 hours, depending on scope, connector scheduling, and platform load.

  • Check the Last Modified By timestamp to compare with the time of your most recent changes in the AWS console. Prefer resources where a known recent change occurred (e.g., tag update, resize, configuration change) to view updates in the CMDB within the expected processing window.

    note

    Last Modified By in Cloudaware can’t be treated as a freshness SLA for static or rarely changing resources.

If timestamps are stale across many objects, there may be an integration or scheduling issue.

Validate Reporting Behavior​

Once inventory looks correct:

  • Open the CMDB list view for the relevant resource type and confirm that the default list views organize resources as expected, including populated columns for name, resource ID, and any available telemetry or cost data.
  • Open cost, security, or operational dashboards that include AWS data and verify that counts, amounts, and resource totals are reasonable.

When to Contact Support​

Contact Cloudaware Support at support@cloudaware.com with screenshots and example resource IDs if:

  • An account or organization remains red after you have confirmed credentials and IAM/role configuration.
  • Specific services (for example, EKS, billing, or CloudTrail‑backed features) remain empty despite correct permissions.
  • Data appears significantly delayed or inconsistent across regions or accounts.