> ## Documentation Index
> Fetch the complete documentation index at: https://docs.levelblue.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Tenable Sensor Deployment for AWS
**To deploy the Tenable sensor for AWS**
1. Log into AWS, and launch a new EC2 instance.
* Enter a **Name and tags** for the instance.
* Search for and select the **Application and OS Images** for the instance.
2. Select **Tenable Core + Tenable Security Center (OL8)**.
3. Select **Subscribe Now**.
4. Set the following configuration:
* Select the **Instance Type**.
* Select the **Key Pair** name. This is needed to connect to the instance.
* Enter the **VPC** and **Subnet** for the **Network Settings**.
* Enable the **Auto-assign Public IP**.
* Enable **SSH** to access the Tenable sensor.
5. Once done, click **Launch Instance**.
6. Continue creating the VM until you get a successful confirmation message.
7. Take note of the **Public** and **Private IP** addresses of the deployed VM.
8. Connect to the Tenable sensor via SSH.
9. Log into [cloud.tenable.com](http://cloud.tenable.com) to get the Linking Key.
10. Click the burger menu, and then select **Settings**.
11. Select **Sensors**.
12. Click **Add Nessus Scanner** to view the Linking Key.
13. Copy the **Linking Key**.
14. In the Tenable sensor CLI, use the Linking Key to link the Tenable sensor.
```text theme={null}
sudo /opt/nessus/sbin/nessuscli managed link --key=”Linking Key” –cloud
```
Once done, you should see a "**Successfully linked**" message.
15. Return to the Tenable cloud page, and verify that the Tenable sensor is linked correctly and is in **Online** status.
**VERIFICATION / TROUBLESHOOTING**
* If the sensor does not link properly:
* Re-check the outbound TCP 443 access to [sensor.cloud.tenable.com](http://sensor.cloud.tenable.com) and [plugins.nessus.org](http://plugins.nessus.org).
* Make sure the Linking Key is correct and not expired.
* If the scans do not find hosts:
* Confirm that the scanner can reach the target network (routing, security groups/NSGs, and target host firewalls).
* For credential scans, confirm that the credentials work and the required auth ports are reachable.