Amazon Web Services (AWS)

Connect AWS identities, IAM privileges, and cloud resources to Superviso.

The Amazon Web Services connector supports Identity & Access records and Assets & Data resources. It uses an IAM access key to read account information in the configured AWS region.

Required values

  • Access Key and Secret Access Key for the dedicated IAM principal
  • Region containing the resources you want Superviso to collect

Required access

Grant the managed IAMReadOnlyAccess policy. Resource collection also requires read access to the AWS services being collected, including the applicable EC2, RDS, Lambda, and S3 APIs.

Use a dedicated read-only principal, avoid reusing an administrator credential, and rotate the access key according to your organization's credential policy.

Before you start

Create the credentials listed above in the provider’s administration tools.

Configure in Superviso

  1. Open Settings → Connectors and choose Add connector.
  2. Select Amazon Web Services (AWS) from Provider.
  3. Associate the intended asset, or use the new-asset option when appropriate. Enable only the supported synchronization options you need.
  4. Enter Access Key, Secret Access Key, and Region for the intended account and resource scope.
  5. Recheck the required privileges, scope, and filters, then choose Create connector. Resolve any validation errors shown by the form.
  6. Open the saved connector, choose Sync connector when available, and confirm the synchronization scope.
  7. Open Logs, wait for execution to finish, and inspect the result and any errors. Open the relevant Identities, Privileges, or Resources page for the enabled integration to verify collected records.
Unsaved Amazon Web Services (AWS) connector setup with synchronization options and blank credential fields.
Select Amazon Web Services (AWS) and review its supported options before entering your own credentials. Select the image to view it full size.

Expected outcome

The connector is saved for Amazon Web Services (AWS) with the intended integration and collection scope. Synchronization logs show progress, results, and imported records.

If setup or synchronization fails

Check the exact account or organization identifier, required form values, credential validity, granted access, and selected filters. Inspect the failed log’s details before retrying. If only some records are missing, check their scope and provider permissions. For synchronization status and source-managed fields, see Connectors and synchronization logs.

Back to Providers

Screenshot

Scroll to inspect the image, or choose Fit image to see the whole screen.