Skip to content
Furl Docs

AWS

Connect Furl to AWS using an IAM access key to import EC2 instance inventory.

Description

Section titled “Description”

The AWS integration imports your EC2 instances into Furl so the context graph knows which devices are AWS-hosted. This is useful for correlating cloud workloads with vulnerability findings and for routing remediations differently depending on whether a device is a cloud instance or a managed endpoint.

Configuration Steps

Section titled “Configuration Steps”

  1. Create an IAM user (or use an existing one) with read-only EC2 access

    Attach a policy that grants at least ec2:DescribeInstances. The AWS-managed AmazonEC2ReadOnlyAccess policy is sufficient if you’d prefer not to author a custom policy.

  2. Generate an access key for that IAM user

    • In the AWS console, go to IAM → Users → <your user> → Security credentials.
    • Click Create access key.
    • Copy both the Access Key ID and Secret Access Key immediately — AWS shows the secret only once.

  3. Identify the AWS region you want Furl to read from (e.g., us-east-1, us-west-2).

Required Configuration

Section titled “Required Configuration”

Provide the following in Furl:

  • AWS Access Key ID — The IAM user’s access key ID.
  • AWS Secret Access Key — The IAM user’s secret access key.
  • AWS Region — The region whose EC2 inventory you want Furl to import.

Supported Capabilities

Section titled “Supported Capabilities”

Datasources

Section titled “Datasources”
  • EC2 Instances → Retrieve information about EC2 instances in the configured region.

Actions

Section titled “Actions”

Currently no actions are supported for this integration.

Best Practice: Dedicated IAM User

Section titled “Best Practice: Dedicated IAM User”

We strongly recommend creating a dedicated IAM user for this integration rather than reusing personal credentials. If a person leaves and their credentials are revoked, the integration breaks; a dedicated integration user avoids that.

Troubleshooting

Section titled “Troubleshooting”
  • If Furl returns an authentication error, verify the access key is active in IAM and hasn’t been deactivated or rotated.
  • If Furl can connect but returns no instances, check that the IAM policy grants ec2:DescribeInstances and that there are running instances in the region you configured.
  • Multi-region accounts: this integration imports a single region per connection. To cover multiple regions, configure the integration once per region.