Integrations / Amazon Web Services

Amazon Web Services

Amazon Web Services (AWS) is a comprehensive cloud computing platform providing infrastructure services including compute, storage, databases, networking, and security.

Custom

Indexes

Actions

What Telara does

Capability matrix

Indexes Yes Tracks spend No Discovers shadow AI No Runs actions Yes Real-time events No

Before you connect

Prerequisites

An AWS account you can administer.

IAM permission to create a user and attach policies. Do not reuse a human console login.

Vendor setup

Get the credential

Create a dedicated IAM user

In the AWS console, go to IAM → Users → Create user. Name it for Telara (for example telara-reader). Skip console access.

Attach read access

On the user, open Permissions → Add permissions → Attach policies directly. Grant only the AWS APIs this connector should call. For a first connect, a read-only policy on the services you care about is enough.

Create an access key

Open the user’s Security credentials tab → Create access key → Other. Copy the access key ID and secret. AWS will not show the secret again.

Paste in Telara

Settings → Integrations → AWS. Enter the account, access key ID, secret, and region Telara asks for.

In Telara

Connect in Telara

Custom

AWS SigV4 signing with Access Key ID and Secret Access Key. Optional session token for assumed-role credentials.

In Telara, open Settings → Integrations, choose this connector, and complete the fields Telara shows.

Fields Telara asks for

Access Key Id
Secret Access Key
Region
Session Token

Knowledge

What gets indexed

Resource	Coverage
Resource inventory	Partial — not every record the vendor holds is synced
Iam user	Partial — not every record the vendor holds is synced

Sync

Freshness & sync

Resource	Lag	Deletions
Resource inventory	Up to 1 day	Removed records disappear on the next full sync
Iam user	Up to 1 day	Removed records disappear on the next full sync

Data handling

Permissions & data handling

Telara has not published a permission list for this connector yet. Treat the vendor consent screen as the source of truth until this page lists scopes.

Excluded from semantic search: Resource inventory, Iam user.

After connect

Verify it worked

This connector does not declare a credential probe yet. A saved connection means Telara stored the credential, not that the vendor accepted it.

Honesty

Known limitations

Empty regions are usually missing IAM, not a Telara outage.

SSO / IAM Identity Center still needs a dedicated machine user. A human SSO session is not a connector credential.