Skip to main content

Amazon Web Services (AWS)

Cloudaware ingests configuration, inventory, and selected telemetry from AWS accounts and organizations using IAM roles (recommended) or dedicated IAM users with access keys.

info
  • Audience: Cloudaware administrators, cloud engineers, security teams, and FinOps users
  • Outcome: AWS accounts and organizations are connected to Cloudaware for inventory, configuration, telemetry, and optional billing and EKS data collection

Use this section to prepare AWS, grant least‑privilege access, connect accounts and organizations, validate ingestion, and configure billing and EKS discovery.

What the AWS Integration Provides​

  • Unified CMDB objects for AWS accounts, organizations, compute, networking, storage, databases, and many PaaS and serverless services.
  • Support for multi‑account topologies via AWS Organizations, with automatic discovery of member accounts when configured.
  • Optional deep visibility into EKS clusters, CloudTrail events, billing, monitoring, and backup features when additional permissions are granted.
  • Cross‑cloud reporting and policies that correlate AWS data with other providers.

Integration Workflow​

Work through the guides in this section in the following order:

  1. Prerequisites — What you need in Cloudaware and AWS before starting.
  2. Least-Privilege Policies — Recommended IAM roles, policies, and trust configuration for read‑only access.
  3. Setup — Step‑by‑step configuration using IAM roles (and optionally access keys) to connect accounts and organizations.
  4. Verification — How to confirm that data is flowing and accounts are healthy.
  5. Troubleshooting — Common issues, diagnostics, and resolution steps.

See also:

  • Service Coverage — Summary of AWS services and object families discovered by Cloudaware.
  • Resource Coverage — Details about AWS resources discovered by Cloudaware.

Follow-up Integrations​

  • AWS Billing — Cost and usage data ingestion for AWS Cost Management. Configure the AWS cloud integration first, then add AWS Billing if you need cost analytics and reporting.
  • EKS Cluster Access — Kubernetes access configuration for discovering EKS objects.
  • EC2/RDS Instance Scheduler — Optional automation for scheduled EC2 and RDS start/stop actions.

Supported Environments​

  • Commercial AWS
  • AWS GovCloud is available when selected during account onboarding.
warning

Some services may not be available in every region or partition.

For CMDB schema details and example queries, see the AWS section in Provider Quick Reference.