AWS
Amazon Web Services is a cloud platform. This connector brings in the EC2 instances in every region of an AWS account, the account’s IAM users and IAM Identity Center users, with their multi-factor authentication (MFA) status and type.
Beta. This connector was built from AWS’s API documentation and hasn’t been verified against a live account yet. It may return incomplete data or fail in ways we haven’t seen. If something looks wrong, contact [email protected].
At a glance
| Data provided | Devices, Users |
|---|---|
| Authentication | IAM access key (optionally used to assume a role) |
| Where to configure | Connectors → Add a Connector → AWS |
Before you start
- One connection covers one AWS account. Add a connection per account.
- Only the standard AWS partition is supported (not China or GovCloud).
- Use a dedicated IAM user with read-only permissions, never a personal or root key.
Setup
- In IAM, create a user with no console access and attach a policy allowing only these actions on
*:ec2:DescribeInstances,ec2:DescribeRegions,iam:ListUsers,iam:ListMFADevices,iam:GenerateCredentialReport,iam:GetCredentialReport,sts:GetCallerIdentity. To also bring in IAM Identity Center users, addsso:ListInstancesandidentitystore:ListUsers; without them those users are skipped. - Create an access key for that user.
- In Navigator, go to Connectors → Add a Connector → AWS, enter the access key ID and secret access key, and save.
To use a role instead (for example one in another account), create the role with the same permissions and a trust policy naming the IAM user, with an external ID condition if you like. Then also enter the Role ARN (and the External ID). The access key is then used only to call sts:AssumeRole, and the user needs sts:AssumeRole on that role.
Limit to these regions is optional: leave it blank to cover every region enabled for the account, or enter a comma-separated list such as us-east-1,eu-west-1.
What data this connector provides
- Devices: every EC2 instance that isn’t terminated, in each region, with name, private DNS name, instance type, operating system, architecture, private and public IP addresses and MAC addresses. Stopped instances are kept. Account, region, availability zone, state, VPC, launch time, whether IMDSv2 is required, and the instance profile are shown as AWS-specific fields.
- Users: every IAM user, plus the account’s root user, with whether MFA is enabled and which type:
virtual_totp(authenticator app),hardware_totp(hardware token),fido(security key) orother. Console access, last password use, creation time and active access-key count are shown as AWS-specific fields. - Identity Center users: name, email and display name. AWS doesn’t expose MFA for these users, so their MFA status is left unknown rather than shown as off.
Known limitations
- Hostname is the instance’s
Nametag, or the first part of its private DNS name when there is no tag. EC2 has no hostname field. - Serial number, CPU count and memory are not provided.
- MFA only matters for users who can sign in to the console. A user with no console password and no MFA is usually a programmatic account; check the Console access field.
- The root user’s MFA type isn’t visible to a non-root key, so it shows MFA enabled or not, with no type.
- IAM users can’t be disabled, so enabled is left unknown, and whether a user is an administrator isn’t determined.
- Passkeys may appear as
fidoorotherdepending on how AWS reports them. - Identity Center groups and group membership, vulnerabilities (Inspector) and installed software (SSM) are not provided.
Troubleshooting
- The sync fails with an access-denied error. The key lacks one of the permissions above.
- The sync notes that a region was skipped. That region isn’t enabled for the account or the key isn’t permitted there.
- The sync notes the credential report is unavailable. Add
iam:GenerateCredentialReportandiam:GetCredentialReport. Until then console access and key counts are unknown.