aktonay/skillz / skills/cloud/cloud-run-basics
cloud-run-basics
VerifiedManages Cloud Run services, jobs, and worker pools. Use when you need to deploy applications responding to HTTP requests (services), run event-triggered or scheduled tasks (jobs), or handle always-on pull-based background processing (worker pools).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.2 KB |
| references/cli-usage.md | markdown | 2.4 KB |
| references/client-library-usage.md | markdown | 3.4 KB |
| references/core-concepts.md | markdown | 6.5 KB |
| references/iac-usage.md | markdown | 2.0 KB |
| references/iam-security.md | markdown | 3.9 KB |
| references/mcp-usage.md | markdown | 1.9 KB |
references/iam-security.md
View on GitHub# Cloud Run IAM & security
Cloud Run uses Identity and Access Management (IAM) to secure your resources and control who can deploy or invoke them.
## Predefined IAM Roles
| Predefined Role | Usage |
| :--- | :--- |
| `roles/run.admin` | Full control over all Cloud Run resources. |
| `roles/run.invoker` | Invoke Cloud Run services and execute Cloud Run jobs. |
| `roles/run.developer` | Read and write access to services, jobs and worker pools; cannot
set IAM policies. |
| `roles/run.viewer` | Read-only access to Cloud Run resources. |
## Types of service accounts for service identity
Cloud Run resources run as a specific service account (the service
identity).
- **User-managed service account (recommended)**: You manually create this
service account and determine the most minimal set of permissions that
the service account needs to access specific Google Cloud resources. The
user-managed service account follows the format of `SERVICE_ACCOUNT_NAME@PROJECT_ID.iam.gserviceaccount.com`.
- **Compute Engine default service account:** Cloud Run automatically
provides the Compute Engine default service account as the default
service identity. The Compute Engine default service account
follows the format of `PROJECT_NUMBER-compute@developer.gserviceaccount.com`.
## Best practices
By default, the Compute Engine default service account is automatically
created. If you don't specify a service account when the
Cloud Run service or job is created, Cloud Run uses this service account.
Depending on your organization policy configuration, the default
service account might automatically be granted the Editor role on your
project. We strongly recommend that you disable the automatic role
grant by enforcing the `iam.automaticIamGrantsForDefaultServiceAccounts`
organization policy constraint. If you created your organization after
May 3, 2024, this constraint is enforced by default.
Create a user-managed service account with minimal
permissions for each Cloud Run resource.
To allow a service to access another GCP resource (e.g.,
Cloud SQL), grant the service's identity the appropriate IAM role on that
resource.
## Security controls
- **Ingress Settings:** Control whether your service is reachable from the
internet (`all`), only from within the VPC (`internal`), or via a load
balancer (`internal-and-cloud-load-balancing`).
- **VPC Egress:** Use a VPC connector or Direct VPC egress to allow Cloud Run to
access resources in your VPC.
- **Binary Authorization:** Ensure only trusted container images are deployed.
- **Secrets Management:** Use Secret Manager to securely pass sensitive
information (e.g., API keys, database passwords) to your containers as
environment variables or volumes.
## Public access
There are two ways to create a public Cloud Run service, you can either:
* Disable the Cloud Run Invoker IAM check (recommended).
* Assign the Cloud Run Invoker IAM role to the `allUsers` member type.
For more information, see:
[Cloud Run security overview](https://docs.cloud.google.com/run/docs/securing/managing-access#make-service-public).
## Configure IAP to secure access
By enabling IAP on Cloud Run directly, you can secure traffic with a single
click from all ingress paths, including default `run.app` URLs and load
balancers.
When you integrate IAP with Cloud Run, you can manage user or group access in
the following ways:
* Inside the organization - configure access to users who are within the same
organization as your Cloud Run service
* Outside the organization - configure access to users who are from
organizations different than your Cloud Run service
* No organization - configure access in projects that are not part of any
Google organization
Enabling IAP on a Cloud Run service can be as easy as deploying a new service with
the following flags:
```bash
gcloud run deploy SERVICE_NAME \
--region=REGION \
--image=IMAGE_URL \
--no-allow-unauthenticated \
--iap \
--quiet
```
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |