create_node
¶
create_node(
client_request_token: ClientRequestTokenString,
network_id: ResourceIdString,
node_configuration: NodeConfiguration,
*,
config_overrides: Optional[ManagedBlockchainClientConfig] = None,
member_id: Optional[ResourceIdString] = None,
tags: Optional[InputTagMap] = None,
) -> CreateNodeOutput
Creates a node on the specified blockchain network.
Applies to Hyperledger Fabric and Ethereum.
Parameters:
-
client_request_token(ClientRequestTokenString) –A unique, case-sensitive identifier that you provide to ensure the idempotency of the operation. An idempotent operation completes no more than one time. This identifier is required only if you make a service request directly using an HTTP client. It is generated automatically if you use an Amazon Web Services SDK or the CLI.
-
network_id(ResourceIdString) –The unique identifier of the network for the node.
Ethereum public networks have the following
NetworkIds:-
n-ethereum-mainnet
-
-
member_id(Optional[ResourceIdString], default:None) –The unique identifier of the member that owns this node.
Applies only to Hyperledger Fabric.
-
node_configuration(NodeConfiguration) –The properties of a node configuration.
-
tags(Optional[InputTagMap], default:None) –Tags to assign to the node.
Each tag consists of a key and an optional value. You can specify multiple key-value pairs in a single request with an overall maximum of 50 tags allowed per resource.
For more information about tags, see Tagging Resources in the Amazon Managed Blockchain Ethereum Developer Guide, or Tagging Resources in the Amazon Managed Blockchain Hyperledger Fabric Developer Guide.
Raises:
-
AccessDeniedException–You don't have sufficient access to perform this action.
-
InternalServiceErrorException–The request processing has failed because of an unknown error, exception or failure.
-
InvalidRequestException–The action or operation requested is invalid. Verify that the action is typed correctly.
-
ResourceAlreadyExistsException–A resource request is issued for a resource that already exists.
-
ResourceLimitExceededException–The maximum number of resources of that type already exist. Ensure the resources requested are within the boundaries of the service edition and your account limits.
-
ResourceNotFoundException–A requested resource doesn't exist. It may have been deleted or referenced incorrectly.
-
ResourceNotReadyException–The requested resource exists but isn't in a status that can complete the operation.
-
ThrottlingException–The request or operation couldn't be performed because a service is throttling requests. The most common source of throttling errors is creating resources that exceed your service limit for this resource type. Request a limit increase or delete unused resources if possible.
-
TooManyTagsException– -
UnknownServiceError–The service returned an error code this client does not model.