custom roles

Related topics

• custom roles is an alternative to predefined roles From the official documentation: “Generally, we recommend that you [use predefined roles](/iam/docs/choose-predefined-roles) instead of basic or custom roles.”
• 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).”
• 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”
• Application Default Credentials secures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
• Application Default Credentials works with Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• Application Default Credentials works with Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• Application Default Credentials secures Pub/Sub From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• Application Default Credentials works with BigQuery From the official documentation: “Create a BigQuery client using application default credentials.”
• Pub/Sub depends on Application Default Credentials From the official documentation: “To authenticate to Pub/Sub, set up Application Default Credentials.”
• Application Default Credentials secures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• BigQuery depends on Application Default Credentials From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
• BigQuery works with Pub/Sub From the official documentation: “createBigQuerySubscription creates a Pub/Sub subscription that exports messages to BigQuery.”
• Cloud Storage is an alternative to Pub/Sub From the official documentation: “To keep audit logs for a longer period of time or to use more powerful search capabilities, you can route copies of your audit logs to Cloud Storage, BigQuery, or Pub/Sub.”
• Cloud Storage works with Pub/Sub From the official documentation: “| **Google Cloud** | Cloud Storage | Pub/Sub |”
• Application Default Credentials configures BigQuery From the official documentation: “To authenticate to BigQuery, set up Application Default Credentials.”
• Application Default Credentials secures IAM From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
• BigQuery is an alternative to Pub/Sub From the official documentation: “To keep audit logs for a longer period of time or to use more powerful search capabilities, you can route copies of your audit logs to Cloud Storage, BigQuery, or Pub/Sub.”
• Cloud Storage depends on Application Default Credentials From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials.”
• 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.”
• Application Default Credentials configures Cloud Storage From the official documentation: “To authenticate to Cloud Storage, set up Application Default Credentials. For more information, see [Set up authentication for client libraries](/storage/docs/authentication#client-libs).”
• Application Default Credentials works with Identity and Access Management From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
• BigQuery works with Identity and Access Management From the official documentation: “BigQuery uses Identity and Access Management (IAM) for authorization.”
• 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.”
• predefined 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).”
• roles configures permissions From the official documentation: “You can grant permissions by granting roles to a principal.”
• Application Default Credentials works with IAM From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
• 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.”
• 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 permissions From the official documentation: “You can edit permissions and labels for multiple secrets 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 depends on Application Default Credentials From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
• 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 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 works with Pub/Sub From the official documentation: “Pub/Sub relies on a standard OAuth authentication used by other Google Cloud products and supports granular IAM, enabling access control for individual resources.”
• IAM secures Pub/Sub From the official documentation: “Access control with IAM Learn how Pub/Sub uses IAM for 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 permissions From the official documentation: “Assign one or more IAM roles to a principal to grant permissions.”
• Identity and Access Management depends on Application Default Credentials From the official documentation: “To authenticate to IAM, set up Application Default Credentials.”
• 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 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 permissions From the official documentation: “Your administrator can give you the required permissions through Identity and Access Management (IAM).”
• Identity and Access Management secures Pub/Sub From the official documentation: “Pub/Sub uses Identity and Access Management (IAM) for authorization.”
• 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.”