Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://cloud.google.com/storage/docs/authentication/managing-hmackeys below:

Manage HMAC keys for service accounts | Cloud Storage

• Discover

• Product overview
• Storage Intelligence overview

• Get started

• Terraform support for Cloud Storage
• Configure and manage Storage Intelligence

• Create buckets

• Create a bucket
• Domain-named bucket verification

• Access and manage buckets

• List buckets
• Change the default storage class of a bucket
• Move and rename buckets
• Delete buckets

• Upload and download objects

• About objects
• Overview of uploads and downloads

• Access and manage objects

• List objects
• Copy, rename, and move objects
• Change an object's storage class
• Tools to access and manage objects using a directory structure
• Object transcoding
• Delete objects

• Get insights on your stored data

• Analyze stored data with Gemini Cloud Assist

• Cache objects

• About caching

• Control data lifecycles

• Options for controlling data lifecycles

• Make requests

• Consistency in Cloud Storage operations
• Batched requests
• Use long-running operations
• Paginate results
• URI wildcards

• Secure data

• Monitor data and usage

• Use Cloud Audit Logs with Cloud Storage
• Usage logs and storage logs
• Use Cloud Audit Logs with storage batch operations
• Use Cloud Logs with storage batch operations
• Use Cloud Audit Logs with Storage Insights
• Use gRPC client-side metrics
• Use client-side traces

• Protection, backup, and recovery

• Overview

• Mount buckets with Cloud Storage FUSE

• Overview
• Quickstart
• Install Cloud Storage FUSE
• Mount buckets

• Work across products, Clouds, and platforms

• Best practices for media workloads
• Interoperability
• Use Cloud Storage with Big Data
• Integration with Google Cloud Platform services and tools

• Troubleshoot

• Troubleshooting

• AI and ML
• Application development
• Application hosting
• Compute
• Data analytics and pipelines
• Databases
• Distributed, hybrid, and multicloud
• Generative AI
• Industry solutions
• Networking
• Observability and monitoring
• Security
• Storage

• Access and resources management
• Costs and usage management
• Google Cloud SDK, languages, frameworks, and tools
• Infrastructure as code
• Migration

• Google Cloud Home
• Free Trial and Free Tier
• Architecture Center
• Blog
• Contact Sales
• Google Cloud Developer Center
• Google Developer Center
• Google Cloud Marketplace
• Google Cloud Marketplace Documentation
• Google Cloud Skills Boost
• Google Cloud Solution Center
• Google Cloud Support
• Google Cloud Tech Youtube Channel

Stay organized with collections Save and categorize content based on your preferences.

Overview

This page shows you how to create, disable, and delete Hash-based Message Authentication Code (HMAC) keys associated with service accounts in your project.

Before using this feature in Cloud Storage, you must meet the following requirements:

1. Have sufficient permission to work with HMAC keys in the selected project:

   • If you own the project, you most likely have the necessary permissions.

   • You should have the IAM permissions that are prefixed with storage.hmacKeys for the project. See Using IAM Permissions for instructions on how to get a role, such as Storage HMAC Key Admin, that has these permissions.

2. Have a service account in your project that you intend to create HMAC keys for. See Creating a service account if you don't currently have one.

3. Make sure the following organization policy constraints are disabled:

   • constraints/storage.restrictAuthTypes (must be disabled for HMAC key authentication)

   • constraints/iam.disableServiceAccountKeyCreation

   See Creating and managing organization policies for instructions on how to check and disable constraints.

To create an HMAC key for a service account:

1. In the Google Cloud console, go to the Cloud Storage Settings page.

   Go to Settings

2. Select the Interoperability tab.

3. Click add_box Create a key for a service account.

4. Select the service account you want the HMAC key to be associated with.

5. Click Create key.

To learn how to get detailed error information about failed Cloud Storage operations in the Google Cloud console, see Troubleshooting.

Use the hmac create command:

gcloud storage hmac create SERVICE_ACCOUNT_EMAIL

Where SERVICE_ACCOUNT_EMAIL is the email address associated with your service account. For example, example-service-account@my-pet-project.iam.gserviceaccount.com.

If successful, the response contains an HMAC key resource, including values for the accessId and secret.

For more information, see the Cloud Storage C++ API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

For more information, see the Cloud Storage C# API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

For more information, see the Cloud Storage Go API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

For more information, see the Cloud Storage Java API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

For more information, see the Cloud Storage Node.js API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

For more information, see the Cloud Storage PHP API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

For more information, see the Cloud Storage Python API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

For more information, see the Cloud Storage Ruby API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

You can use a Terraform resource to create an HMAC key. This sample also includes a resource to create a service account.

1. Have gcloud CLI installed and initialized, which lets you generate an access token for the Authorization header.

2. Use cURL to call the JSON API with a POST hmacKeys request:

   curl -X POST \
     -H "Authorization: Bearer $(gcloud auth print-access-token)" \
     "https://storage.googleapis.com/storage/v1/projects/PROJECT_IDENTIFIER/hmacKeys?serviceAccountEmail=SERVICE_ACCOUNT_EMAIL"

   Where:

   • PROJECT_IDENTIFIER is the ID or number for the project associated with the key you want to create. For example, my-pet-project.
   • SERVICE_ACCOUNT_EMAIL is the email address associated with your service account. For example, example-service-account@my-pet-project.iam.gserviceaccount.com.

1. Have gcloud CLI installed and initialized, which lets you generate an access token for the Authorization header.

2. Use cURL to call the XML API with a POST HMAC Key request:

   curl -X POST \
     -H "Authorization: Bearer $(gcloud auth print-access-token)" \
     "https://storage.googleapis.com/?Action=CreateAccessKey&UserName=SERVICE_ACCOUNT_EMAIL"

   Where SERVICE_ACCOUNT_EMAIL is the email address associated with your service account. For example, example-service-account@my-pet-project.iam.gserviceaccount.com.

To list the HMAC keys for a project, and get information about the keys:

1. In the Google Cloud console, go to the Cloud Storage Settings page.

   Go to Settings

2. Select the Interoperability tab.

   Service accounts that have HMAC keys associated with them appear in the Access keys for service accounts subsection of the Service account HMAC section.

3. Click the name of a specific service account to see the HMAC keys associated with it and the status of those keys.

1. Use the hmac list command to list hmac keys in your project:

   gcloud storage hmac list

   If successful, the command returns a list of hmac key access IDs, along with the state of each key and the service account associated with each key.

2. Use the hmac describe command to retrieve metadata for a specific key:

   gcloud storage hmac describe KEY_ACCESS_ID 

   Where KEY_ACCESS_ID is the access ID for the desired key.

For more information, see the Cloud Storage C++ API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

The following sample retrieves a list of HMAC keys associated with a project:

The following sample retrieves information for a specific HMAC key:

For more information, see the Cloud Storage C# API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

The following sample retrieves a list of HMAC keys associated with a project:

The following sample retrieves information for a specific HMAC key:

For more information, see the Cloud Storage Go API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

The following sample retrieves a list of HMAC keys associated with a project:

The following sample retrieves information for a specific HMAC key:

For more information, see the Cloud Storage Java API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

The following sample retrieves a list of HMAC keys associated with a project:

The following sample retrieves information for a specific HMAC key:

For more information, see the Cloud Storage Node.js API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

The following sample retrieves a list of HMAC keys associated with a project:

The following sample retrieves information for a specific HMAC key:

For more information, see the Cloud Storage PHP API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

The following sample retrieves a list of HMAC keys associated with a project:

The following sample retrieves information for a specific HMAC key:

For more information, see the Cloud Storage Python API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

The following sample retrieves a list of HMAC keys associated with a project:

The following sample retrieves information for a specific HMAC key:

For more information, see the Cloud Storage Ruby API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

The following sample retrieves a list of HMAC keys associated with a project:

The following sample retrieves information for a specific HMAC key:

To switch an HMAC key between being active and inactive:

1. In the Google Cloud console, go to the Cloud Storage Settings page.

   Go to Settings

2. Select the Interoperability tab.

3. In the Access keys for service accounts subsection, click the name of the service account associated with the HMAC key whose status you want to update.

4. Click the status of the key you want to update.

   • If you are changing the key's state from Inactive to Active, click Deactivate in the window that appears.

   • If you are changing the key's state from Active to Inactive, no additional steps are required.

Use the hmac update command:

gcloud storage hmac update ACCESS_KEY_ID STATE

Where:

• ACCESS_KEY_ID is the access ID associated with the key you are updating.
• STATE is either --activate or --deactivate.

If successful, the command returns the updated metadata of the HMAC key.

For more information, see the Cloud Storage C++ API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

The following sample deactivates an HMAC key:

The following sample activates an HMAC key:

For more information, see the Cloud Storage C# API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

The following sample deactivates an HMAC key:

The following sample activates an HMAC key:

For more information, see the Cloud Storage Go API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

The following sample deactivates an HMAC key:

The following sample activates an HMAC key:

For more information, see the Cloud Storage Java API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

The following sample deactivates an HMAC key:

The following sample activates an HMAC key:

For more information, see the Cloud Storage Node.js API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

The following sample deactivates an HMAC key:

The following sample activates an HMAC key:

For more information, see the Cloud Storage PHP API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

The following sample deactivates an HMAC key:

The following sample activates an HMAC key:

For more information, see the Cloud Storage Python API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

The following sample deactivates an HMAC key:

The following sample activates an HMAC key:

For more information, see the Cloud Storage Ruby API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

The following sample deactivates an HMAC key:

The following sample activates an HMAC key:

When you change the state of an HMAC key, it takes up to 3 minutes for the state change to propagate through the Cloud Storage system. For this reason, you should wait at least 3 minutes between making an HMAC key inactive and deleting the key.

An HMAC key must be in an inactive state in order to delete it. To delete an inactive HMAC key:

1. In the Google Cloud console, go to the Cloud Storage Settings page.

   Go to Settings

2. Select the Interoperability tab.

3. In the Access keys for service accounts subsection, click the name of the service account associated with the HMAC key you want to delete.

4. Click the Trash icon associated with the key you want to delete.

5. In the dialog that appears, enter the first 10 characters of the access key ID as they are given in the window.

6. Click Delete.

Use the hmac delete command:

gcloud storage hmac delete ACCESS_KEY_ID

Where ACCESS_KEY_ID is the access ID associated with the key you are deleting.

If successful, the command does not return a response.

For more information, see the Cloud Storage C++ API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

For more information, see the Cloud Storage C# API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

For more information, see the Cloud Storage Go API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

For more information, see the Cloud Storage Java API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

For more information, see the Cloud Storage Node.js API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

For more information, see the Cloud Storage PHP API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

For more information, see the Cloud Storage Python API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

For more information, see the Cloud Storage Ruby API reference documentation.

To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see Set up authentication for client libraries.

• Follow the guidelines for migrating from user account HMAC keys to service account HMAC keys.
• Use an HMAC key in an authenticated request.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-10-02 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-10-02 UTC."],[],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.5