custom roles

Related topics

• custom roles is an alternative to predefined role From the official documentation: “Consolidate multiple predefined roles into fewer custom roles to reduce the space consumed.”
• custom roles is part of IAM roles From the official documentation: “This requirement applies to both [predefined roles](/iam/docs/roles-permissions) and [custom roles](/iam/docs/roles-overview#custom).”
• custom roles is part of Identity and Access Management From the official documentation: “To support this, IAM offers [custom roles](/iam/docs/creating-custom-roles).”
• API Gateway works with custom roles From the official documentation: “If basic or predefined roles do not meet your specific needs, API Gateway supports the use of custom roles.”
• Cloud Storage works with custom roles From the official documentation: “VPC Service Controls supports [custom roles](/iam/docs/creating-custom-roles) for Cloud Storage in ingress and egress rules, but doesn't support the [predefined Cloud Storage roles](/storage/docs/access-control/iam-roles#standard-roles).”
• custom roles is part of IAM From the official documentation: “To support this, IAM offers [custom roles](/iam/docs/creating-custom-roles).”
• custom roles is part of roles From the official documentation: “Type of roles to list. Valid values are 'custom', 'predefined', or 'all'.”
• IAM permissions is part of custom roles From the official documentation: “A role is a collection of permissions.”
• BigQuery is an alternative to Cloud Storage From the official documentation: “The `import_result_sink` must be a Cloud Storage path or a BigQuery table.”
• BigQuery works with Cloud Storage From the official documentation: “Sample to load Avro data from Cloud Storage into a new BigQuery table”
• API Gateway works with Cloud Run From the official documentation: “API Gateway only supports Cloud Run gRPC services at this time.”
• Cloud Run works with Cloud Storage From the official documentation: “Receive events from Cloud Storage in a Cloud Run service”
• Cloud Run works with Identity and Access Management From the official documentation: “For example, a remote backend deployed on Cloud Run can use Identity and Access Management (IAM) to:”
• Cloud Storage bucket is part of Cloud Storage From the official documentation: “Create a Google Cloud Storage bucket”
• IAM secures BigQuery From the official documentation: “BigQuery uses IAM to manage access to resources.”
• IAM permissions is part of IAM roles From the official documentation: “IAM roles that apply to Cloud SQL and the permissions contained in each role.”
• IAM roles is part of Identity and Access Management From the official documentation: “IAM roles give the principals permissions to perform tasks on your App Topology resources.”
• Identity and Access Management secures Cloud Storage From the official documentation: “Cloud Storage uses Identity and Access Management (IAM) for authorization.”
• API Gateway secures Cloud Functions From the official documentation: “Deploy an API on API Gateway to secure traffic to a Cloud Functions backend using the Google Cloud CLI.”
• BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
• Cloud Functions works with Cloud Storage From the official documentation: “You can use Cloud Run functions to launch Workflows in response to Pub/Sub events or file changes in Cloud Storage.”
• IAM permissions is part of roles From the official documentation: “IAM permissions are [grouped into roles](/document-ai/docs/access-control/iam-roles), and you assign roles to users and groups.”
• IAM roles configures service accounts From the official documentation: “You can grant IAM roles to users, groups, and service accounts. These roles define what they can do with your resources.”
• API Gateway works with Cloud Functions From the official documentation: “The steps required to set up API Gateway to manage and secure a [Cloud Functions](/functions/docs) backend service are outlined in the API Gateway [Quickstarts](/api-gateway/docs/quickstarts).”
• API Gateway secures Cloud Run From the official documentation: “This page shows you how to set up API Gateway to manage and secure a [Cloud Run](/run/docs) backend service with gRPC.”
• BigQuery works with Cloud Run From the official documentation: “You can then use Cloud Run to transcode data present in the bucket and move it to BigQuery.”
• BigQuery depends on Cloud Storage From the official documentation: “BigQuery relies on Cloud Storage for staging file data and supports reading from and writing to several other sources and Google Cloud services.”
• BigQuery works with Cloud Storage bucket From the official documentation: “BigQuery lets you load [Datastore](/datastore) entities from a Cloud Storage bucket into a BigQuery table for analysis.”
• Cloud Functions depends on Cloud Run From the official documentation: “Cloud Run functions represent the next evolution of Cloud Functions, offering an event-driven programming model with enhanced control and scalability, leveraging the Cloud Run serverless platform.”
• Cloud Storage works with Google Cloud console From the official documentation: “The browser-based Google Cloud console tool lets you manage your Cloud Storage resources through a graphical interface.”
• Cloud Storage works with IAM From the official documentation: “Use IAM and Cloud Storage Terraform resources to create a public Cloud Storage bucket.”
• Cloud Storage works with Identity and Access Management From the official documentation: “To learn how to use IAM with Cloud Storage, see [Using IAM Permissions](/storage/docs/access-control/using-iam-permissions).”
• Google Cloud console configures IAM roles From the official documentation: “You can get and set IAM allow policies and IAM roles using the Google Cloud Console.”
• Google Cloud console configures roles From the official documentation: “You can grant these IAM roles using the Google Cloud console or the IAM API.”
• IAM secures Cloud Functions From the official documentation: “Use IAM to Secure and Control Access Learn how to configure security for your functions.”
• IAM secures Cloud Run From the official documentation: “Authenticated services are [protected by IAM](/run/docs/securing/managing-access).”
• IAM configures Cloud Storage From the official documentation: “Apply IAM policies consistently across all relevant assets and resources in your AI and ML systems, including the following: - Cloud Storage buckets that contain sensitive data or model artifacts.”
• IAM configures Cloud Storage bucket From the official documentation: “IAM controls permissioning throughout Google Cloud and lets you grant permissions at the bucket and project levels.”
• IAM secures Google Cloud console From the official documentation: “For information about the various user roles and getting access control to Google Cloud console see [Access control with IAM](https://cloud.google.com/support/docs/access-control).”
• IAM secures service accounts From the official documentation: “Authorized access: to ensure that only authorized service accounts can query external data, use Identity and Access Management (IAM) for centralized access control.”
• IAM permissions works with IAM roles From the official documentation: “This page lists the IAM roles and permissions for Apigee Registry.”
• IAM permissions depends on roles From the official documentation: “Permissions are not granted directly to users; permissions are instead granted indirectly through roles, which group permissions.”
• IAM roles secures Cloud Storage From the official documentation: “**Fine-grained access control**: Control agent access to Cloud Storage precisely using [IAM roles](/storage/docs/access-control/iam-roles).”
• IAM roles configures Cloud Storage bucket From the official documentation: “Provide your instance with the `storage.objectAdmin` and `objectViewer` [IAM roles](/storage/docs/access-control/iam-roles) for your bucket.”
• Identity and Access Management secures BigQuery From the official documentation: “Security in BigQuery is intrinsically linked to [Identity and Access Management (IAM)](/iam/docs/overview) in Google Cloud.”
• Identity and Access Management secures Cloud Functions From the official documentation: “You use [Identity and Access Management (IAM)](/iam) to authorize identities to perform administrative actions on functions created using the [Cloud Functions v2 API](/functions/docs/apis)—for example, using `gcloud functions`, the REST API, or Terraform.”
• Identity and Access Management secures Cloud Run From the official documentation: “Cloud Run services are secured by IAM.”
• Identity and Access Management configures Cloud Storage bucket From the official documentation: “You can use [Identity and Access Management (IAM)](/storage/docs/access-control/iam) to control access to individual buckets.”
• Identity and Access Management secures Cloud Storage bucket From the official documentation: “These modifications to that file define a second backup repository in a Cloud Storage bucket, accessed through Identity and Access Management (IAM).”
• Identity and Access Management configures IAM permissions From the official documentation: “You can use IAM to manage who can access your project and what they are allowed to do.”
• Identity and Access Management configures service accounts From the official documentation: “To manage this access, you grant specific Identity and Access Management (IAM) roles to the service accounts that receive events and invoke your target workloads.”
• predefined role is part of Identity and Access Management From the official documentation: “To make it easier to give these users the permissions that they need, Identity and Access Management (IAM) offers predefined roles that are designed for specific job functions.”
• predefined role is part of roles From the official documentation: “Type of roles to list. Valid values are 'custom', 'predefined', or 'all'.”
• roles configures service accounts From the official documentation: “To manage permissions within your project, you grant roles to individuals and service accounts.”
• service accounts is part of Identity and Access Management From the official documentation: “The Organization Policy Service provides constraints that can be used in [organization policies](/organization-policy/overview) to limit the usage of Identity and Access Management (IAM) [service accounts](/iam/docs/service-accounts).”