> 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/gcp-services.md).

# GCP Services

Managing GCP services and related components

DuploCloud provides several configurable components when running Google Cloud Provider's Google Kubernetes Engine (GKE).

Applications involve GCP Services such as Cloud Armour, Redis and SQL databases, Storage Buckets, Load Balancers, and so on.

Using DuploCloud, you can create unlimited Services within each Tenant, using application-centric inputs. At the same time, the platform ensures that the lower-level nuances are programmed to best practices for security and compliance.

## Supported Services for DuploCloud GCP

In addition to GKE standard and auto-pilot, the following services are supported. Supported Services are listed in alphabetical order, following the core services: Containers and Load Balancers.

### Core Services

* [Containers and Services](/docs/automation-platform/overview-1/gcp-services/containers.md)
* [Load Balancers](/docs/automation-platform/overview-1/gcp-services/step-4-create-a-load-balancer.md)

### Additional Services

* [GCP Databases](/docs/automation-platform/overview-1/gcp-services/gcp-databases.md)
  * [Cloud SQL](/docs/automation-platform/overview-1/gcp-services/gcp-databases/cloud-sql.md)
  * [Firestore Database](/docs/automation-platform/overview-1/gcp-services/gcp-databases/firestore-database.md)
  * [Managed Redis](/docs/automation-platform/overview-1/gcp-services/gcp-databases/managed-redis.md)
* [Cloud Armour](/docs/automation-platform/overview-1/gcp-services/cloud-armour.md)
* [Cloud Credentials](/docs/automation-platform/overview-1/gcp-services/cloud-credentials.md)
* [Cloud Functions](/docs/automation-platform/overview-1/gcp-services/cloud-functions.md)
* [Cloud Run Service](/docs/automation-platform/overview-1/gcp-services/cloud-run-service.md)
* [Cloud Scheduler](/docs/automation-platform/overview-1/gcp-services/s3-bucket-1.md)
* [Cloud Storage](/docs/automation-platform/overview-1/gcp-services/s3-bucket-2.md)
* [Cloud Tasks](/docs/automation-platform/overview-1/gcp-services/cloud-tasks.md)
* [Node Pools](/docs/automation-platform/overview-1/gcp-services/node-pools.md)
* [Pub/Sub](/docs/automation-platform/overview-1/gcp-services/s3-bucket-3.md)
* [GCP Secrets Manager](/docs/automation-platform/overview-1/gcp-services/gcp-secrets-manager.md)
* [GCP Security Command Center](/docs/automation-platform/overview-1/gcp-services/gcp-security-command-center.md)
* [Virtual Private Cloud (VPC) Peering](/docs/automation-platform/overview-1/gcp-services/virtual-private-cloud-vpc-peering.md)


---

# 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/gcp-services.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.