> For the complete documentation index, see [llms.txt](https://docs.ionos.com/cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ionos.com/cloud/home/network-services/flow-logs/how-tos/delete-flow-logs.md).
# Delete a Flow Log
IONOS CLOUD Flow Logs: delete a flow log from a network interface in the DCD
{% hint style="info" %}
**Prerequisites:**
* Only contract administrators, owners, and users with the **Create Flow logs** permission can delete a flow log. Ensure that you have the necessary permission and sufficient memory available.
{% endhint %}
To delete a flow log, follow these steps:
1\. In the **DCD**, go to **Menu** > **Virtual Data Centers**.
2\. Open the required data center.
3\. Select the relevant VM for which you want to delete the flow logs. Open the properties of the Network Interface Controller (NIC) and select the **Network** tab.
4\. Select the **Flow Log** drop-down list.
5\. Select the  to delete the flow log. Confirm your selection by selecting **OK**.
6\. Select **Provision changes**. After provisioning, the network interface's flow logs are deleted successfully and no longer captured.
{% hint style="success" %}
**Result:** The flow log is deleted successfully.
{% endhint %}
{% hint style="info" %}
**Note:** Deleting a flow log does not delete the existing log streams from your bucket. Existing flow log data must be deleted using the respective service console. In addition, deleting a flow log that publishes to space.vars.ionos\_cloud\_object\_storage does not remove the bucket policies and log file Access Control Lists (ACLs).
{% endhint %}
---
# 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.ionos.com/cloud/home/network-services/flow-logs/how-tos/delete-flow-logs.md?ask=&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.