Top AI Repos — open-source AI, indexed and scored
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Top AI Repos tracks AI repositories on GitHub and answers two different questions about each one: is it moving right now, and would you bet a product on it.
Guide to running Vault on Cloud Run
| Date | Stars |
|---|---|
| 2026-07-24 | 407 |
| 2026-07-25 | 407 |
| 2026-07-28 | 407 |
| 2026-07-30 | 407 |
| 2026-08-06 | 407 |
Today
— stars today
This week
— stars this week
This month
— stars this month
Momentum
0.0
growth rate 0.00%/day
# Serverless Vault with Cloud Run
This tutorial walks you through deploying Hashicorp's [Vault](https://www.vaultproject.io) on [Cloud Run](https://cloud.google.com/run), Google Cloud's container based Serverless compute platform.
## Rational
Vault is a tool for encrypting data, managing secrets, and auditing access to them. Vault should be deployed to a secure and highly available environment to ensure applications have reliable access to secrets and credentials. Vault can leverage managed services such as [Cloud KMS](https://cloud.google.com/security-key-management) and [Google Cloud Storage](https://cloud.google.com/storage) to protect and store its data, and [Cloud Run](https://cloud.google.com/run) to serve it and capture audit logs.
While Vault can be deployed to Kubernetes, or a virtual machine, Cloud Run reduces operational complexity by delegating infrastructure management to the cloud provider. Cloud Run can scale Vault to zero when not in use, or be configured to [keep a single instance available](https://cloud.google.com/run/docs/configuring/min-instances) to serve [concurrent request](https://cloud.google.com/run/docs/configuring/concurrency) at the lowest latency possible. Cloud Run automatically captures Vault's audit logs and sends them to [Cloud Logging](https://cloud.google.com/logging/docs) for centralized storage and analysis.
> Cloud Run can also be configured to ensure only one instance of Vault is running at a given time. See the Cloud Run [maximum instances docs](https://cloud.google.com/run/docs/configuring/max-instances).
## Tutorial
Create a new Google Cloud project:
```
gcloud projects create \
--name vault-on-cloud-run \
--set-as-default
```
Type `y` at the prompt and press `enter`:
```
No project id provided.
Use [vault-on-cloud-run-XXXXXX] as project id (Y/n)? y
```
Before you can continue you must [enable billing](https://cloud.google.com/billing/docs/how-to/modify-project) on the project to enable the use of Cloud KMS as an [auto-unseal](https://learn.hashicorp.com/tutorials/vault/autounseal-gcp-kms) mechanism.
To streamline the rest of the tutorial define the key configuration settings and assign them to environment variables:
```
PROJECT_ID=$(gcloud config get-value project)
```
> `PROJECT_ID` holds the project id generated at the start of the tutorial.
```
GCS_BUCKET_NAME="${PROJECT_ID}-data"
```
> `GCS_BUCKET_NAME` holds the Google Cloud Storage bucket name used to persist Vault's data.
```
SERVICE_ACCOUNT_EMAIL="vault-server@${PROJECT_ID}.iam.gserviceaccount.com"
```
> `SERVICE_ACCOUNT_EMAIL` holds the Google Cloud IAM email address representing the `vault-server` service account.
```
CURRENT_USER_EMAIL=$(gcloud config list account --format "value(core.account)")
```
> `CURRENT_USER_EMAIL` holds the email address representing the current logged in Google Cloud user.
```
REGION=us-west1
```
> `REGION` holds the region in which to deploy the vault-server.
Enable the Cloud KMS, Cloud Run, Cloud Storage, and Secret Manager APIs:
```
gcloud services enable --async \
cloudkms.googleapis.com \
run.googleapis.com \
secretmanager.googleapis.com \
storage.googleapis.com
```
Create a service account for the Vault server:
```
gcloud iam service-accounts create vault-server
```
Create a GCS storage bucket to hold Vault's encrypted data:
```
gsutil mb gs://${GCS_BUCKET_NAME}
```
```
Creating gs://vault-on-cloud-run-XXXXXX-data/...
```
Grant the necessary permissions on GCS storage bucket for the `vault-server` service account:
```
gsutil iam ch \
serviceAccount:${SERVICE_ACCOUNT_EMAIL}:objectAdmin \
gs://${GCS_BUCKET_NAME}
```
Store the vault server config file in [Secret Manager](https://cloud.google.com/secret-manager):
```
gcloud secrets create vault-server-config \
--replication-policy automatic \
--data-file vault-server.hcl
```
Grant access to the `vault-server-config` secret to the `vaulExcerpt of 10,434 characters
Read on GitHubWould you bet a product on this? Bounded 0–100 and slow moving.
matched fp:0100bb43f345ef8d, topic:serverless