The role grants auditing/read permissions only (
SecurityAudit +
ViewOnlyAccess + a few extra read actions). TigerGate can never create,
modify, or delete resources in your account.Before you start
Deploying the template needs two values:| Value | What it is |
|---|---|
| TigerGate account ID | The 12-digit AWS account TigerGate scans from — the principal that assumes your role. Get it from TigerGate; it fills the template’s TigerGateAccountId parameter. |
| External ID | A shared secret you choose (any unique string). Put the same value in the template and in the AWS connection form (confused-deputy protection). |
1. Create the role with CloudFormation
Get the template
Use the
tigergate-cspm-scan-role.yaml template (shown in full at the bottom
of this page — copy it into a file).Deploy it in the account you want scanned
CAPABILITY_NAMED_IAM is required because the template creates a named role.2. Connect it in TigerGate
Paste the Role ARN + External ID
In the dashboard, go to Integrations → Cloud Providers → Add Provider →
Amazon Web Services. Paste the
RoleArn output into Role ARN and the
same value into External ID. Set a Default Region (required — used for
the initial STS/API calls; the scan still covers every region).Test
Click Test. TigerGate does a live
AssumeRole + GetCallerIdentity and
confirms the connection works — or tells you the exact AWS reason (bad
credentials, assume-role denied, wrong external ID) so you can fix it before
saving.Multiple accounts (AWS Organizations)
To roll the role out across every account in an Organization, deploy the same template as a CloudFormation StackSet targeting your OUs. Use the same TigerGate account ID; you can share one External ID or use one per account.Alternative: static access keys
If you can’t use a role, TigerGate also accepts an IAM user’s access key + secret key (with an optional session token for temporary STS credentials). Attach the same read-only policies (SecurityAudit + ViewOnlyAccess + the
extra read actions) to that user, then enter the keys in the same Add Provider
→ Amazon Web Services form (Access Key ID, Secret Access Key, Default Region).
A role is preferred — no long-lived secrets to store or rotate.
Troubleshooting
| Scan/Test error | Cause | Fix |
|---|---|---|
AccessDenied … sts:AssumeRole | Role trust doesn’t allow TigerGate, wrong External ID, or a user ARN was entered as the role | Redeploy the template with the correct TigerGate account ID + External ID; make sure the Role ARN (not a user ARN) is used |
SignatureDoesNotMatch / AWS Secret Access Key is invalid | Wrong/rotated secret key | Re-enter the access key + secret, or switch to the role |
InvalidClientTokenId | Access key ID is wrong or deactivated | Re-check the key |
| Scan runs but few findings | Missing read permissions | Ensure both managed policies + the additions policy are attached (the template does this) |
The template
tigergate-cspm-scan-role.yaml
tigergate-cspm-scan-role.yaml