> For the complete documentation index, see [llms.txt](https://docs.duplocloud.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.duplocloud.com/docs/automation-platform/overview/use-cases/hosts-vms/disable-source-destination-check.md).

# Disable Source Destination Check

Disable CloudFormation's SourceDestCheck in EC2 Host metadata

{% hint style="danger" %}
Source/destination checking is a security feature. Disabling it is only needed in specific use cases. In most cases, disabling it creates a security gap. We recommend consulting with the DuploCloud team before using this.
{% endhint %}

AWS EC2 ensures that each instance is either the source or the destination of any network traffic that it receives. This is called "[source/destination checking](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-eni.html#eni-basics)". In the DuploCloud Portal, this parameter is specified as `true`, by default, enabling source and destination checks.

There are times when you may want to override this default behavior, such as when an EC2 instance runs services [Network Address Translation (NAT)](https://docs.aws.amazon.com/vpc/latest/userguide/work-with-nat-instances.html#EIP_Disable_SrcDestCheck), routing, or firewalls. To override the default behavior and set the `SourceDestCheck` parameter to `false`, use this procedure.

## Disable `SourceDestCheck` in the DuploCloud Portal

Set `SourceDestCheck` to `false` for an EC2 Host:

1. In the DuploCloud Portal, navigate to **Cloud Services -> Hosts**.
2. In the **EC2** tab, select the Host for which you want to disable `SourceDestCheck`.
3. Click the **Metadata** tab.
4. Click **Add**. The **Add Metadata** pane displays.<br>

   <div align="left"><figure><img src="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2FKwewi0gGcCf5f1wcV7fr%2FSDC1.png?alt=media&amp;token=1a336882-e116-48f5-90f2-ee7b288408af" alt=""><figcaption><p><strong>Add Metadata</strong> pane for <strong>Key SourceDestCheck</strong></p></figcaption></figure></div>
5. In the **Key** field, enter **SourceDestCheck**.
6. In the **Value** field, enter **False**.
7. Click **Create**. The **Key**/**Value** pair is displayed in the **Metadata** tab.

<figure><img src="https://2471407984-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F68cb0s9ce5UIUKWPuYs8%2Fuploads%2FC60XTc9tovMxdrKBCod6%2Fscreenshot-nimbusweb.me-2024.02.18-14_47_44.png?alt=media&amp;token=53837a1e-2379-4a8e-8a25-01447508102a" alt=""><figcaption><p><strong>EC2 Host</strong> page <strong>Metadata</strong> tab displaying <strong>SourceDestCheck Value</strong> of <strong>False</strong></p></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.duplocloud.com/docs/automation-platform/overview/use-cases/hosts-vms/disable-source-destination-check.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
