AWS Amazon Managed Blockchain
Browse all Amazonaws APIs★ Only Publicly Available OpenAPI DocumentCloud InfrastructureComputehmac27 EndpointsREST
For Agents
Provision and operate Hyperledger Fabric blockchain networks, manage members, peer nodes, and governance proposals through one API.
Use for: I need to create a new Hyperledger Fabric network for a supply chain consortium, Invite a member to join an existing blockchain network, Provision a new peer node for our member in availability zone us-east-1a, List all proposals currently open on a network
Not supported: Does not handle smart contract execution, wallet management, or token transfers — use for blockchain network, member, node, and governance provisioning only.
Jentic publishes the only available OpenAPI specification for Amazon Managed Blockchain, keeping it validated and agent-ready. Amazon Managed Blockchain is a fully managed service for creating and operating blockchain networks built on open-source frameworks such as Hyperledger Fabric and read access to Ethereum. The control plane covers networks, members, peer nodes, proposals, voting, accessor tokens, and tag management. It removes the operational burden of provisioning ordering services, certificate authorities, and peer nodes so teams can focus on chaincode and application logic.
Install Jentic One Beta
Connect the Amazon Managed Blockchain to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Amazon Managed Blockchain, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Amazon Managed Blockchain API.
Create Hyperledger Fabric blockchain networks with configurable framework and edition
Invite members to a network through governance proposals and votes
Provision and update peer nodes with chosen instance types and availability zones
Submit and vote on proposals for network membership and configuration changes
Issue accessor tokens that grant signed access to Ethereum nodes for read calls
List and inspect networks, members, nodes, proposals, and invitations across regions
Tag networks and resources for cost allocation and access control
Use Cases
Patterns agents use Amazon Managed Blockchain API for, with concrete tasks.
★ Supply Chain Consortium Network
Manufacturers, logistics partners, and retailers stand up a permissioned Hyperledger Fabric network on Managed Blockchain to share traceability records. The API creates the network, admits each partner as a member through governance proposals, and provisions peer nodes per organization. AWS handles ordering services, certificate authorities, and node patching so the consortium owns only the chaincode and integration code.
Call CreateNetwork with FRAMEWORK=HYPERLEDGER_FABRIC and STARTER edition, then create a member for our organization with an admin user, and provision a single peer node in us-east-1a
Decentralised Application Backend
dApp teams use Managed Blockchain accessors to issue read-only access tokens for Ethereum mainnet and testnets without running their own nodes. CreateAccessor returns a billing token used to authorise JSON-RPC read calls; the API also handles listing and revoking accessors. This pattern offloads node operations and lets the agent focus on transaction crafting via wallets external to AWS.
Call CreateAccessor with AccessorType=BILLING_TOKEN, then list current accessors and return the active token for use against Ethereum read endpoints
Network Governance Workflows
Consortium operators use proposal and voting endpoints to admit or remove members, change configuration, and audit decisions. CreateProposal opens the vote, ListProposals shows open and closed items, and VoteOnProposal records each member's choice. All actions are tagged with members and timestamps so the consortium has an audit trail of governance.
List open proposals on the network, then vote YES on a specific ProposalId on behalf of MemberId m-ABC123
AI Agent Blockchain Operations
AI agents use Managed Blockchain through Jentic to provision nodes, monitor network status, and execute governance actions on behalf of operators. Jentic isolates AWS Signature v4 credentials in the vault and exposes the network, member, node, and proposal operations as discoverable tools so the agent can answer 'add a peer node in eu-west-1' without learning the AWS SDK.
Search Jentic for 'create a blockchain peer node', load the CreateNode operation, and execute it for NetworkId n-NET123 and MemberId m-MEM123 with an InstanceType of bc.t3.medium in availability zone eu-west-1a
Key Endpoints
27 endpoints — jentic publishes the only available openapi specification for amazon managed blockchain, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/networks
Create a new blockchain network
POST
/networks/{networkId}/members
Create a member within a network
POST
/networks/{networkId}/members/{memberId}/nodes
Create a peer node for a member
POST
/networks/{networkId}/proposals
Create a governance proposal
POST
/networks/{networkId}/proposals/{proposalId}/votes
Vote on a proposal
GET
/networks/{networkId}
Describe a blockchain network
POST
/accessors
Create an Ethereum accessor token
POST
/networks
Create a new blockchain network
POST
/networks/{networkId}/members
Create a member within a network
POST
/networks/{networkId}/members/{memberId}/nodes
Create a peer node for a member
POST
/networks/{networkId}/proposals
Create a governance proposal
POST
/networks/{networkId}/proposals/{proposalId}/votes
Vote on a proposal
GET
/networks/{networkId}
Describe a blockchain network
POST
/accessors
Create an Ethereum accessor token
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
AWS access keys are stored encrypted in the Jentic vault. Each Managed Blockchain call is signed with Signature Version 4 server-side so the agent never sees raw keys, and IAM policies scope what networks and resources the agent can touch.
Intent-based discovery
Agents search by intent (e.g. 'create a blockchain network' or 'invite a member') and Jentic returns matching Managed Blockchain operations such as CreateNetwork, CreateMember, and CreateNode with their input schemas.
Time to first call
Direct integration: 2-4 days for IAM, async resource readiness handling, and SDK plumbing. Through Jentic: under an hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Amazon Managed Blockchain API through Jentic.
Why is there no official OpenAPI spec for Amazon Managed Blockchain?
AWS does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Amazon Managed Blockchain via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Amazon Managed Blockchain API use?
The control-plane API uses AWS HMAC request signing (Signature Version 4) with an access key ID and secret access key scoped via IAM. Through Jentic, AWS credentials sit in the encrypted vault and are signed into each request server-side, so the agent only handles short-lived scoped sessions.
Can I provision peer nodes with the Amazon Managed Blockchain API?
Yes. POST /networks/{networkId}/members/{memberId}/nodes creates a peer node with a chosen InstanceType (e.g. bc.t3.medium) and AvailabilityZone. GET on the same path lists existing nodes; the per-node DescribeNode endpoint returns status, framework attributes, and logging configuration.
What are the rate limits for the Amazon Managed Blockchain API?
AWS does not document per-second request limits for Managed Blockchain control-plane operations in the public spec. Instead, soft quotas apply to the number of networks, members per network, and nodes per member. Check the AWS service quotas console for current limits in your region.
How do I create a governance proposal through Jentic?
Search Jentic for 'create a blockchain proposal' to surface POST /networks/{networkId}/proposals. Load the schema with the Jentic SDK (pip install jentic), then execute it with the proposing MemberId and the Actions object describing the change. Use VoteOnProposal to record subsequent votes.
Is Amazon Managed Blockchain free?
No. Managed Blockchain charges per member per hour, per peer node by instance hours, and for data written and storage on the network. There is no free tier — see the AWS Managed Blockchain pricing page for current rates by framework and edition.
GET STARTED