Skip to content

Commit 2b30a86

Browse files
author
iru
authored
doc: troubleshoot datasources alias
1 parent 1469036 commit 2b30a86

File tree

1 file changed

+12
-0
lines changed

1 file changed

+12
-0
lines changed

README.md

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -349,6 +349,18 @@ This error happens when the ECS `TaskRole` has no permissions to assume this rol
349349
A: Probably you or someone in the same environment you're using, already deployed a resource with the sysdig terraform module and a naming collision is happening.
350350
<br/>S: If you want to maintain several versions, make use of the [`name` input var of the examples](https://github.com/sysdiglabs/terraform-aws-secure-for-cloud/tree/master/examples/single-account#input_name)
351351

352+
### Q-AWS-Datasources: I cannot see my acccount alias in the `Data Sources > Cloud page`
353+
A: There are several causes to this.
354+
<br/>Check that your aws account has an alias set-up. It's not the same as the account name.
355+
```bash
356+
$ aws iam list-account-aliases
357+
```
358+
If all good, test `deploy_benchmark` flag is enabled on your account, hence the trust-relationship is enabled between Sysdig and your cloud infrastructure.
359+
In order to validate the trust-relationship expect no errows on following API.
360+
```shell
361+
$ curl -v https://<SYSDIG_SECURE_ENDPOINT>/api/cloud/v2/accounts/<AWS_ACCOUNT_ID>/validateRole \
362+
--header 'Authorization: Bearer <SYSDIG_SECURE_API_TOKEN>'
363+
```
352364
<br/><br/>
353365

354366
## Upgrading

0 commit comments

Comments
 (0)