Google Cloud 는 특정Google Cloud 리소스에 대한 세부적인 액세스 권한을 부여하고 다른 리소스에 대한 무단 액세스를 방지할 수 있는 Identity and Access Management (IAM)를 제공합니다. 이 페이지에서는 Service Directory API 역할을 설명합니다. IAM에 대한 자세한 내용은 IAM 문서를 참고하세요.
IAM을 사용하면 최소 권한의 보안 원칙을 적용하여 필요한 리소스에 대한 액세스 권한만 부여할 수 있습니다.
IAM을 사용하면 IAM 정책을 설정하여 누가어떤 리소스에 무슨 권한을 갖는지를 제어할 수 있습니다. IAM 정책은 사용자에게 특정 역할을 부여하여 특정 권한을 줍니다.
권한 및 역할
모든 Service Directory API 메서드는 호출자에게 필수 IAM 권한을 요구합니다. 사용자, 그룹 또는 서비스 계정에 역할을 부여하여 권한을 할당할 수 있습니다. 기본 소유자, 편집자, 뷰어 역할 외에도 프로젝트 사용자에게 Service Directory API 역할을 부여할 수 있습니다.
[[["이해하기 쉬움","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\nGoogle Cloud offers Identity and Access Management (IAM),\nwhich enables you to give more granular access to specific\nGoogle Cloud resources and prevents unwanted access to other\nresources. This page describes the Service Directory API roles. For a detailed\ndescription of IAM, read the [IAM documentation](/iam/docs).\n\nIAM enables you to adopt the\n[security principle of least privilege](https://wikipedia.org/wiki/Principle_of_least_privilege),\nso you grant only the necessary access to your resources.\n\nIAM enables you to control *who* has *what* permissions to\n*which* resources by setting IAM policies. IAM\npolicies grant specific roles to a user, giving the user certain\npermissions.\n\nPermissions and Roles\n---------------------\n\nEvery Service Directory API method requires the caller to have the necessary\nIAM permissions. You can assign permissions by granting roles to\na user, group, or service account. In addition to the basic Owner,\nEditor, and Viewer roles, you can grant Service Directory API roles to the users\nof your project.\n\n### Permissions\n\nYou can find out which permissions are required for each method in the\nService Directory\n[API reference documentation](/service-directory/docs/reference/rest).\n\n### Roles\n\nAccess Control using the Google Cloud console\n---------------------------------------------\n\nYou can use the Google Cloud console to manage access control for your\nregistry.\n\nTo set access controls at the project level: \n\n### Console\n\n1. In the Google Cloud console, go to the **IAM** page.\n\n [Go to IAM](https://console.cloud.google.com/iam-admin/iam)\n2. Select your project from the top pull-down menu.\n\n3. Click **Add**.\n\n4. In **New principals**, enter the email address of a new principal.\n\n5. Select the desired role from the drop-down menu: `servicedirectory.admin`,\n `servicedirectory.editor`, or `servicedirectory.viewer`\n\n6. Click **Save**.\n\n7. Verify that the principal is listed with the role that you granted.\n\nService Directory zones override IAM restrictions\n-------------------------------------------------\n\nWhen assigning a namespace to a Service Directory zone, the service names\nbecome visible to all clients on any networks that are authorized to\nquery the private zone. There is no IAM access control for DNS as\nthe DNS protocol does not provide authentication capability.\n\nWhat's next\n-----------\n\n- See the [IAM documentation](/iam/docs) for details on Identity and Access Management\n- See the [Overview](/service-directory/docs/overview) for an understanding of Service Directory."]]
