> 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-1/security-configuration-settings/gcp-firewall-rules.md).

# GCP Firewall Rules

Configure firewall rules in DuploCloud for GCP environments

Firewall rules in Google Cloud Platform (GCP) control inbound and outbound network traffic to your virtual machines and other cloud resources. These rules define whether traffic is allowed or denied based on source IP ranges, protocols, ports, and targets.

DuploCloud enables you to manage GCP firewall rules directly from the Portal. Firewall rules are stateful, meaning return traffic is automatically allowed for approved inbound connections.

There are two types of firewall rules in DuploCloud:

* [Infrastructure Firewall Rules](https://docs.duplocloud.com/docs/automation-platform/overview-1/security-configuration-settings/gcp-firewall-rules/infrastructure-firewall-rules.md): Apply to an entire GCP infrastructure environment. Ideal for managing baseline network access at the environment level.
* [Tenant-Based Firewall Rules](https://docs.duplocloud.com/docs/automation-platform/overview-1/security-configuration-settings/gcp-firewall-rules/tenant-based-firewall-rules.md): Apply to individual tenants within an infrastructure. Useful for isolating tenant workloads or defining tenant-specific traffic policies.


---

# 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-1/security-configuration-settings/gcp-firewall-rules.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.
