IAM에서 Google Cloud 리소스 액세스 권한은 최종 사용자에게 직접 부여되지 않습니다. 대신 권한이 역할로 그룹화되고 역할은 인증된 주 구성원에게 부여됩니다. 주 구성원 유형은 사용자, 그룹, 서비스 계정 또는 Google 도메인 중 하나일 수 있습니다.
IAM 정책은 어떤 역할이 어떤 주 구성원에게 부여되는지 정의하고 적용합니다. 그러면 이 정책이 리소스에 연결됩니다.
이 페이지에서는 Cloud Load Balancing 관련 IAM 역할 및 권한에 대해 간략히 설명합니다. IAM에 대한 자세한 설명은 IAM 문서를 참조하세요.
역할 및 권한
부하 분산 안내 가이드의 예시를 따르려면 주 구성원은 인스턴스, 방화벽 규칙, VPC 네트워크를 만들어야 합니다. 다음 방법 중 하나로 필요한 권한을 제공할 수 있습니다.
부하 분산과 관련된 사전 정의된 역할을 부여합니다.
사전 정의된 역할에 포함된 특정 권한을 보려면 다음 섹션을 참조하세요.
[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-09-04(UTC)"],[],[],null,["# Roles and permissions\n\nWhen you use Cloud Load Balancing, you make API requests. Each API request requires\nthat the [Identity and Access Management (IAM) principal](/iam/docs/overview#how_cloud_iam_works) who\nmakes the request has appropriate permission to create, modify, or delete the\nassociated resources.\n\nIn IAM, permission to access a Google Cloud resource\nisn't granted directly to the end user. Instead, permissions are grouped\ninto roles, and roles are granted to authenticated principals. Principals can be\nof the following types: a user, group, service account, or Google domain.\nAn IAM policy defines and enforces what roles are\ngranted to which principals, and this policy is then attached to a resource.\n\nThis page provides an overview of relevant IAM roles and\npermissions for Cloud Load Balancing. For a detailed description of\nIAM, see the [IAM documentation](/iam/docs).\n\nRoles and permissions\n---------------------\n\nTo follow the examples in the load balancing [how-to guides](/load-balancing/docs/how-to), principals\nneed to create instances, firewall rules, and VPC networks. You\ncan provide the necessary permissions in one of the following ways:\n\n- Grant the [predefined roles](/compute/docs/access/iam) that are related to load\n balancing.\n To view the specific permissions included in the predefined roles, see the\n following sections:\n\n - Compute Load Balancer Admin role ([`roles/compute.loadBalancerAdmin`](/compute/docs/access/iam#compute.loadBalancerAdmin))\n - Compute Network Admin role ([`roles/compute.networkAdmin`](/compute/docs/access/iam#compute.networkAdmin))\n - Compute Security Admin role ([`roles/compute.securityAdmin`](/compute/docs/access/iam#compute.securityAdmin))\n - Compute Instance Admin role ([`roles/compute.instanceAdmin`](/compute/docs/access/iam#compute.instanceAdmin))\n- [Create and grant custom roles](/iam/docs/creating-custom-roles) that at least contain the\n permissions included in the predefined roles.\n\n- Use [basic roles](/iam/docs/understanding-roles#basic), making the principals project owners\n or editors. Whenever possible, avoid using the basic roles; they grant a\n large number of permissions, which violates the principle of least privilege.\n\nRole change latency\n-------------------\n\nCloud Load Balancing caches IAM permissions for five minutes,\nso it takes up to five minutes for a role change to become effective.\n\nManaging Access Control for Cloud Load Balancing using IAM\n----------------------------------------------------------\n\nYou can get and set IAM policies using the Google Cloud console, the\nIAM API, or the Google Cloud CLI. See [Granting,\nchanging, and revoking access](/iam/docs/granting-changing-revoking-access) for details.\n\nWhat's next\n-----------\n\n- Learn more about [IAM](/iam/docs).\n- [Grant IAM roles](/iam/docs/granting-changing-revoking-access).\n- Learn about [IAM Conditions for forwarding\n rules](/load-balancing/docs/access-control/iam-conditions).\n- Learn about [organization policy constraints for Cloud Load\n Balancing](/load-balancing/docs/org-policy-constraints)."]]
