Organiza tus páginas con colecciones
Guarda y categoriza el contenido según tus preferencias.
En esta página, se describen los permisos y roles necesarios para usar y
configurar Blockchain Node Engine.
Los nodos de cadena de bloques exponen un extremo de API. Google no define esta API, pero forma parte del software de terceros que ejecutamos. Puedes ver un ejemplo de esto en el servidor JSON-RPC de Ethereum. Este extremo requiere una clave de API para acceder. Las claves de API se administran en Google Cloudy, por lo tanto, usan los permisos definidos en Control de acceso con IAM.
Estos permisos se agregaron al rol de administrador.
Funciones
En esta sección, se enumeran todos los roles seleccionados que proporciona el servicio de Blockchain Node Engine.
Lector
Otorga acceso de lectura a todos los recursos del Motor de nodos de cadenas de bloques. Destinado a ingenieros que usan nodos, pero no los administran. Se espera que un administrador proporcione las claves de API. El usuario no tiene acceso directo para buscar claves de API.
Otorga acceso completo a todos los recursos del Motor de nodos de cadenas de bloques. Está destinado a los administradores de nodos de cadenas de bloques.
Los administradores tienen todos los permisos disponibles para blockchainnodeengine.googleapis.com/viewer, además de los siguientes:
[[["Fácil de comprender","easyToUnderstand","thumb-up"],["Resolvió mi problema","solvedMyProblem","thumb-up"],["Otro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Información o código de muestra incorrectos","incorrectInformationOrSampleCode","thumb-down"],["Faltan la información o los ejemplos que necesito","missingTheInformationSamplesINeed","thumb-down"],["Problema de traducción","translationIssue","thumb-down"],["Otro","otherDown","thumb-down"]],["Última actualización: 2025-09-04 (UTC)"],[[["\u003cp\u003eThis page outlines the permissions and roles necessary for interacting with Blockchain Node Engine.\u003c/p\u003e\n"],["\u003cp\u003eBlockchain nodes expose an API endpoint that requires API keys for access, managed through Google Cloud's IAM system.\u003c/p\u003e\n"],["\u003cp\u003eThe Viewer role provides read access to Blockchain Node Engine resources, without direct access to API keys.\u003c/p\u003e\n"],["\u003cp\u003eThe Admin role offers full access to all Blockchain Node Engine resources, including managing API keys and creating/deleting blockchain nodes.\u003c/p\u003e\n"],["\u003cp\u003eIAM is the access control system and various links are provided to learn more about it, including links for access with API keys, and service usage.\u003c/p\u003e\n"]]],[],null,["# Permissions and roles\n\nThis page describes the permissions and roles that are required to use and\nconfigure Blockchain Node Engine.\n\nThe blockchain nodes themselves expose an API endpoint. Google does not define\nthis API, but is part of the third party software we run. You can see an example\nof this at\n[Ethereum's JSON-RPC Server](https://geth.ethereum.org/docs/rpc/server). This\nendpoint requires an API\nkey to access. API keys are managed in Google Cloud, and as such use the\npermissions defined on [Access control with IAM](/api-keys/docs/access-control).\nThese permissions have been added to the admin role.\n\nRoles\n-----\n\nThis section lists all curated roles provided by Blockchain Node Engine service.\n\n\n### Viewer\n\nGrants read access to all Blockchain Node Engine resources. Intended for\nengineers who use but do not manage nodes. API keys are expected to be provided\nfrom an admin. The viewer does not have direct access to look up\nAPI keys.\n\n[Blockchain Node Engine actions](/blockchain-node-engine/docs/reference/rest):\n\n- `blockchainnodeengine.googleapis.com/blockchainNodes.get`\n- `blockchainnodeengine.googleapis.com/blockchainNodes.list`\n- `blockchainnodeengine.googleapis.com/locations.get`\n- `blockchainnodeengine.googleapis.com/locations.list`\n- `blockchainnodeengine.googleapis.com/operations.get`\n- `blockchainnodeengine.googleapis.com/operations.list`\n\n[Retrieve project information](/resource-manager/reference/rest):\n\n- `cloudresourcemanager.googleapis.com/projects.get`\n- `cloudresourcemanager.googleapis.com/projects.list`\n\n[Return APIs information](/service-usage/docs/reference/rest):\n\n- `serviceusage.googleapis.com/services.get`\n\n### Admin\n\nGrants full access to all Blockchain Node Engine resources. Intended for\nblockchain node administrators.\n\nAdministrators have all permissions available to\n`blockchainnodeengine.googleapis.com/viewer` plus:\n\n\u003cbr /\u003e\n\n[API keys management](/api-keys/docs/reference/rest):\n\n- `apikeys.googleapis.com/keys.update`\n- `apikeys.googleapis.com/keys.create`\n- `apikeys.googleapis.com/keys.delete`\n- `apikeys.googleapis.com/keys.get`\n- `apikeys.googleapis.com/keys.getKeyString`\n- `apikeys.googleapis.com/keys.list`\n- `apikeys.googleapis.com/keys.undelete`\n\n[Blockchain Node Engine actions](/blockchain-node-engine/docs/reference/rest):\n\n- `blockchainnodeengine.googleapis.com/blockchainNodes.create`\n- `blockchainnodeengine.googleapis.com/blockchainNodes.delete`\n- `blockchainnodeengine.googleapis.com/operations.cancel`\n- `blockchainnodeengine.googleapis.com/operations.delete`\n\n[Enable APIs](/service-usage/docs/reference/rest):\n\n- `serviceusage.googleapis.com/services.enable`\n\nSee also\n--------\n\n- [Access control with IAM - API keys](/api-keys/docs/access-control)\n- [Access Control with IAM - Service usage](/service-usage/docs/access-control)\n- [IAM basic and predefined roles reference](/iam/docs/understanding-roles)\n- [IAM permissions reference](/iam/docs/permissions-reference)\n- [Manage access to projects, folders, and organizations](/iam/docs/granting-changing-revoking-access)\n- [Roles and permissions](/iam/docs/roles-overview)"]]
