Skip to content

Latest commit

 

History

History
55 lines (39 loc) · 1.55 KB

private.md

File metadata and controls

55 lines (39 loc) · 1.55 KB

Private service

Let's deploy a container to non publicly accessible Cloud Run service. We can use the service in helloworld folder from before.

Deploy to Cloud Run

PROJECT_ID=$(gcloud config get-value project)
SERVICE_NAME=helloworld-private
REGION=us-central1

gcloud run deploy $SERVICE_NAME \
  --image gcr.io/$PROJECT_ID/helloworld \
  --no-allow-unauthenticated \
  --platform managed \
  --region $REGION

This creates a private Cloud Run service.

Test the service

If you test the service by visiting the url of the service, you get a 403 Forbidden error:

SERVICE_URL=$(gcloud run services describe $SERVICE_NAME --region $REGION --format 'value(status.url)')

curl https://helloworld-private-paelpl5x6a-ew.a.run.app

<html><head>
<meta http-equiv="content-type" content="text/html;charset=utf-8">
<title>403 Forbidden</title>
</head>
<body text=#000000 bgcolor=#ffffff>
<h1>Error: Forbidden</h1>
<h2>Your client does not have permission to get URL <code>/</code> from this server.</h2>
<h2></h2>
</body></html>

There's an Authenticate section in Cloud Run docs that shows how to authenticate for different use cases.

For testing, you can go to the Cloud Run console and under the service url, you can see an example on how to call the service with the Authorization header:

Cloud Run Console

Try again:

curl -H \
"Authorization: Bearer $(gcloud auth print-identity-token)" \
${SERVICE_URL}

Hello World!