---
title: Connecting Amazon EC2 Discovery
description: "To attach an Amazon account to Detect, you will need: Go to the AWS Identity and Access Management (IAM) Console: 🔗 IAM Console Download the .csv file containing the Access Key ID and Secret Access K"
---

[Skip to content](https://support.preludesecurity.com/docs/amazon-ec2#main-content)

English

Show submenu for translations

[Contact support](https://support.preludesecurity.com/kb-tickets/new?hsLang=en)

![Prelude\_Wordmark\_Black\_Transparent.png\]](https://support.preludesecurity.com/hs-fs/hubfs/Prelude_Wordmark_Black_Transparent.png?height=50&name=Prelude_Wordmark_Black_Transparent.png)

Open main navigation

Close main navigation

- English
  
  Show submenu for translations
- [Contact support](https://support.preludesecurity.com/kb-tickets/new)
- [Visit the website](https://www.preludesecurity.com/)

[Visit the website](https://www.preludesecurity.com/)

 Find what you're looking for

- There are no suggestions because the search field is empty.

1. [Knowledge Base](https://support.preludesecurity.com/?hsLang=en)
2. [Monitor](https://support.preludesecurity.com/monitor?hsLang=en)
3. [Device Discovery Integrations](https://support.preludesecurity.com/monitor?hsLang=en#device-discovery-integrations)

# Connecting Amazon EC2 Discovery

To attach an Amazon account to Detect, you will need:

- The Prelude Dashboard / UI ([US1](https://platform.us1.preludesecurity.com/dashboard) | [EU1](https://platform.eu1.preludesecurity.com/dashboard)) or [Prelude CLI](https://support.preludesecurity.com/docs/prelude-cli?hsLang=en)
- Amazon Console access and permissions to grant IAM roles/permissions

#### IAM Role setup

### **1. Sign in to AWS IAM Management Console**

Go to the **AWS Identity and Access Management (IAM) Console**:  
🔗[IAM Console](https://console.aws.amazon.com/iam/)

---

### **2. Create or Use an IAM User**

#### **If You Have an IAM User:**

- In the left menu, click **Users**.
- Select your IAM user.

#### **If You Need to Create a New IAM User:**

- Click **Add users**.
- Enter a username.
- Select **Access key - Programmatic access**.

---

### **3. Attach Permissions**

- Click **Attach policies directly**.
- Perms needed: 
    - Ec2 integration needs only **AmazonEC2ReadOnlyAccess**

- Click **Next** and **Create user**.

---

### **4. Generate and Download the Access Key**

- Go to the **Security credentials** tab of your user.
- Click **Create access key**.
- Select **Application running outside AWS** or another option that fits your use case.
- Click **Create access key**.

**Download the .csv file** containing the **Access Key ID** and **Secret Access Key**. ⚠️ This is the only time you can see the secret key!

Within the Prelude SCM Console, navigate to [integrations](https://platform.us1.preludesecurity.com/account/integrations)

- Click on +Connect for Amazon EC2 Device Discovery
- Enter: 
    - Custom name for the connection (optional)
    - Amazon Account ID
    - Access Key
    - Secret Key
- Click Connect  
  ![](https://support.preludesecurity.com/hs-fs/hubfs/screenshot_2566-png.png?width=1174&height=888&name=screenshot_2566-png.png)

- [Monitor](https://support.preludesecurity.com/monitor?hsLang=en#main-content)

    - [Introduction to Control Monitor](https://support.preludesecurity.com/monitor?hsLang=en#introduction-to-control-monitor)
    - [Configuration](https://support.preludesecurity.com/monitor?hsLang=en#configuration)
    - [Client Hardware Security Integrations](https://support.preludesecurity.com/monitor?hsLang=en#client-hardware-security-integrations)
    - [Device Discovery Integrations](https://support.preludesecurity.com/monitor?hsLang=en#device-discovery-integrations)
    - [EDR Integrations](https://support.preludesecurity.com/monitor?hsLang=en#edr-integrations)
    - [Email Integrations](https://support.preludesecurity.com/monitor?hsLang=en#email-integrations)
    - [Identity Management Integrations](https://support.preludesecurity.com/monitor?hsLang=en#identity-management-integrations)
    - [Endpoint Management Integrations](https://support.preludesecurity.com/monitor?hsLang=en#endpoint-management-integrations)
    - [Vulnerability Management Integrations](https://support.preludesecurity.com/monitor?hsLang=en#vulnerability-management-integrations)
    - [Reporting](https://support.preludesecurity.com/monitor?hsLang=en#reporting)
    - [Troubleshooting](https://support.preludesecurity.com/monitor?hsLang=en#troubleshooting)
- [Detect](https://support.preludesecurity.com/detect?hsLang=en#main-content)

    - [Basics](https://support.preludesecurity.com/detect?hsLang=en#basics)
    - [Integrations](https://support.preludesecurity.com/detect?hsLang=en#integrations)
    - [Probe deployment](https://support.preludesecurity.com/detect?hsLang=en#probe-deployment)
    - [Security tests](https://support.preludesecurity.com/detect?hsLang=en#security-tests)
    - [Alert suppression](https://support.preludesecurity.com/detect?hsLang=en#alert-suppression)
    - [Assurance](https://support.preludesecurity.com/detect?hsLang=en#assurance)
- [Integrations](https://support.preludesecurity.com/integrations?hsLang=en#main-content)

    - [SASE](https://support.preludesecurity.com/integrations?hsLang=en#sase)
- [Account](https://support.preludesecurity.com/account?hsLang=en#main-content)

    - [SSO](https://support.preludesecurity.com/account?hsLang=en#sso)
- [CLI](https://support.preludesecurity.com/cli?hsLang=en)
- [Release Notes](https://support.preludesecurity.com/release-notes?hsLang=en)

[![Origin Technology Logo](https://support.preludesecurity.com/hs-fs/hubfs/origin_logo_inverse_000000.png?width=5000&height=5000&name=origin_logo_inverse_000000.png "Origin Technology Logo")](http://originhq.com)

Prelude Security Knowledge Base

Copyright © 2026, Origin Technology