GCP

Creating a Service Account via Google Cloud Console (UI)

CK CK 3788 
Created at
Updated at  
1,069 0 0

I wanted to use Vertex AI, and learned that I need some sort of Service Account that does not need to set user permission whenever we need to use it.

In Google Cloud Platform (GCP), a Service Account is a special type of Google account intended for non-human users, like applications or virtual machines, to authenticate and access GCP resources securely. Unlike Google Workspace users which represent individual people with email addresses and passwords, Service Accounts are identified by email-like addresses managed by GCP, and are authenticated using cryptographic keys instead of passwords. To use Vertex AI API, you'll need a Service Account with the appropriate permissions (e.g., Vertex AI User, Vertex AI Administrator) granted through IAM (Identity and Access Management) to authorize your application to make API calls and access the necessary data and services.
 

What you will have after creating Service Accounts

After creating service accounts, you will have API identities that your applications can use to authenticate and authorize themselves to access Google Cloud resources. Specifically, you'll typically have:

  • Service Account Email Address: This is the unique identifier for the service account. It looks like an email address (e.g., my-service-account@project-id.iam.gserviceaccount.com). It's used to grant permissions.
  • Service Account Keys (Optional but Common): These are used by your application to prove its identity.
    • JSON Key: This is the most common type, especially when the application is running outside of Google Cloud. It contains a private key used to generate credentials. Important: Store this securely! Don't commit it to a code repository or leave it in a public directory.
    • Other Key Types (Less Common): Other key types exist for specific scenarios, but JSON keys are generally the most versatile.
  • IAM Permissions: These determine what the service account is allowed to do. You grant roles to the service account at the project, folder, or resource level using IAM (Identity and Access Management).

 

How do you create a Service Account via Google Cloud Console (UI)?

1. Go to the IAM & Admin > Service Accounts

Creating a Service Account via Google Cloud Console (UI)

 

2. Click "Create Service Account"

Fill in:

  • Service account name (e.g., vertex-ai-client)
  • (Optional) Description

Click "Create and Continue".

 

3. Grant This Service Account Access to the Project

Choose a role that gives access to Vertex AI. Common choices:

  • Vertex AI User (roles/aiplatform.user)
  • Optionally, add:
    • roles/storage.objectViewer if reading from Cloud Storage.
    • roles/aiplatform.admin for full access (use with caution).

Click Continue → Done.

 

4. Generate and Download a Key File

  1. Find your service account in the list.
  2. Click the three dots menu (⋮) → Manage keys.
  3. Click Add Key → Create new key.
  4. Choose JSON.
  5. Click Create → the key file will download (.json).

⚠️ Keep this file secure. It contains credentials that allow access to your Google Cloud services.

 

In summary, creating a service account gives you an identity and the means (keys, if you generate them) to *use* that identity to access Google Cloud resources in a controlled and secure way. It allows your application to act *as* the service account, following the IAM policies you've defined for it.
 

Tags GCP Service Account Google Cloud Console Service Account Vertex AI Facebook X
Comments 0
Similar posts
  1. How to Get a YouTube Channel ID from a URL in PHP
    1,030
  2. Google OAuth Token Expiration: Causes and Solutions
    31
  1. Step-by-Step Guide to Using Google AI Gemini API with CURL
    3,210
  2. Improving nested_fields data access experience with a persistent user-defined function (aka UDF) in Google Big Query
    1,505
  3. Creating a query based on record type data field in Google BigQuery
    1,642
Recently updated
  1. Why 100% SEO Guarantees Better User Engagement and How to Achieve It in Your Service
    57
  2. Why SPF and DKIM Are Essential for Linux Email Servers?
    51
  3. How do I create animated background for Google Meet?
    23,256
  4. MaxMind GeoLite2 vs. DB-IP Lite vs. ip-api.com: Choosing the Right Free IP Geolocation Solution
    273
  5. Meet Valkey: Why Redis Changed Its License, Why Valkey is Better, and How to Use It as a Drop-in Replacement
    105
  6. How Rogue Web Scrapers Are Stealing My Content and Destroying My Server
    170
  7. Array of arguments passed to script in PHP
    99
  8. Invalid Auction Storms in Ad Tech
    108
  9. Building MRC-Compliant Instrumentation in Ad Tech: Implementation Steps and Key Challenges
    209
  10. The Two Clocks of Ad Server Architecture
    78
  11. Frequency Cap Architecture Overview
    527
  12. Collecting Proof-of-Play from 100,000 Screens
    154
  13. Vector Search in Relational Databases (RDBs): Trends & Usage Environments
    303
  14. What is RedisVL?
    117
  15. Designing a Skill Registry Architecture: Minimize Token Usage and Maximize AI Performance
    247
  16. TPU & GPU Cluster Management Tools
    258
  17. The Concept of Scaffolding in AI Agents
    245
  18. Beyond Static Pipelines: Architecting LLM Multi-Agent Systems for Autonomous Workflow Orchestration
    599
  19. AI-DLC vs. AI-SDLC: Model-Centric vs. System-Centric AI Development
    269
  20. Fine-Tuning Open-Weight LLMs: Training, Licensing, and Deploying Custom Models with Ollama
    355
  21. Inside the Next-Generation Streaming Architecture: Ultra-Low Latency, SGAI, and AI Codecs
    207
  22. Machine Learning: Training vs. Ranking
    231
  23. The Continuous Learning Machine: Designing a Loop That Actually Turns
    229
  24. The Next-Gen Low-Latency Standards: LL-HLS & MoQ
    204
  25. Designing a Data Curation System Around a Vector Database
    230
  26. Extracting Context from Live Video: The Architecture Got Simpler When We Stopped Building Features
    264
  27. The New Ad Stack Behind Live Sports Streaming: Inside SGAI, EABN, and the Standards Race to Fix Live Monetization
    674
  28. Designing MLOps Architectures to Handle Seasonal Data Drift in EV Fleet Models
    201
  29. From 15 to 40+ FPS: Accelerating PyTorch Object Detection on Automotive ECUs
    233
  30. Understanding Data Lineage
    272