# VPC Search

By default, Hava builds your diagrams at a VPC level. A single diagram is generated for each VPC within your cloud provider account.

However, you might want to combine multiple VPC into one diagram view. For instance, a common use case is creating a single diagram view of all the VPC connected via a VPC peering connection.

### **Basic Examples**

| Search                         | Result                                                                                         |
| ------------------------------ | ---------------------------------------------------------------------------------------------- |
| `vpc:vpc-1234`                 | This would return everything in `vpc-1234` and be the same as the default VPC created by Hava. |
| `vpc:vpc-1234 or vpc:vpc-5678` | This would return both `vpc-1234` and `vpc-5678` using the or operator.                        |

### Locating VPC ID

If you don’t already know the VPC id, this can be found in several locations within Hava in the attribute panel.

**The most common way to find it is:**

1. Open up the VPC you want.
2. Click anywhere within the VPC container.
3. In the attribute panel under the VPC name, you will find the ID.

![
](https://codahosted.io/docs/cYayXS-HlE/blobs/bl-iCj_CsDI6F/a1048fad9a9a681e15ee8eb94b6e3164325bc2ccece98468504a9e12cf9753dd5e3ca3d015e1d08b91f5a0ceafca31910e627acff9124b16a821d1f0ba1f5041464e8201e64131ab4d13d5451111d59b13f30c18ff4b26f25649d989513120b4d70fc48d)

### Incorrect Syntax Errors

Hava requires the correct syntax if forgotten or edited, this will cause a syntax error. For example, when searching for a VPC it must include `vpc:` followed by the VPC id with no (space) in between

#### Space between vpc: and the VPC id

* Correct use: <mark style="color:green;">`vpc:vpc-1234`</mark>
* Incorrect use: <mark style="color:red;">`vpc: vpc-1234`</mark>

![](https://3601125483-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Loco-kTiJ7Tu_lfPZqb%2Fuploads%2FCsWt1CWWTiJfyZXvAFwP%2Fimage.png?alt=media\&token=8718c85b-fc1a-4789-9843-61873b707009)

**No vpc: before the VPC id**

* Correct use: <mark style="color:green;">`vpc:vpc-1234`</mark>
* Incorrect use: <mark style="color:red;">`vpc-vpc-1234`</mark>

![](https://3601125483-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Loco-kTiJ7Tu_lfPZqb%2Fuploads%2Fm5Hots1BnlB9dySSDbMe%2Fimage.png?alt=media\&token=c554a4bd-008a-4c14-8b3f-951f30099f4a)

**No Boolean operator between query**&#x20;

* Correct use: <mark style="color:green;">`vpc:vpc-123 or vpc:vpc-abcd`</mark>
* Incorrect use: <mark style="color:red;">`vpc:vpc-1234 or vpc-abcd`</mark>&#x20;

![](https://3601125483-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Loco-kTiJ7Tu_lfPZqb%2Fuploads%2FUgHhaKlyMq2PAhan3qu3%2Fimage.png?alt=media\&token=59128199-675c-4090-a9b2-fcd1476937ea)

### Use Cases

* VPC Peering Connections
