# AWS VPC

## Step 1

In AWS go to **Network & Security** > **Security Groups** > **Create security group**.

![](https://418253935-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiJ406Lpi9EKoWDi7GFL7%2Fuploads%2FgNuDcJHS0yOtqwioQe1F%2FIP%20whitelisting%20guides%20-%20AWS%20VPC_1.PNG?alt=media\&token=acc670d5-1659-460d-a9a3-317059c39d4d)

## Step 2

**Name** the Security group, select the appropriate **VPC**, and fill out the **Inbound rules** section with the information provided below. Finally, click **Create security group**.

* **Type** - All traffic
* **Source** - **Custom** - GoodAccess Gateway IP**/32** (example: 11.22.33.44/32)

{% hint style="warning" %}
**Please note:** If you are using VPC peering, you can later update the rules for your VPC security groups to[ reference security groups in the peered VPC](https://docs.aws.amazon.com/vpc/latest/peering/vpc-peering-security-groups.html). In case you are using a Transit Gateway, note that spoke Amazon VPCs cannot reference security groups in other spokes connected to the same AWS Transit Gateway.
{% endhint %}

![](https://418253935-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiJ406Lpi9EKoWDi7GFL7%2Fuploads%2FTdrYzy1tTmpL990ljoYx%2FIP%20whitelisting%20guides%20-%20AWS%20VPC_2.PNG?alt=media\&token=12894bc9-c6b7-4c27-b711-0ad358edbb3d)

## Step 3

#### **Attach resources to the security group**

* Return to the EC2 dashboard, go to **Instances** > **Instances**
* Select the instance you would like to apply the Security Group to (**Actions** > **Networking** > **Change Security Groups**)
* Select the newly created security group and **Assign security group**