Building Private Blockchains with Amazon Managed Blockchain - Operating Hyperledger Fabric
Learn how to build a private blockchain network with Hyperledger Fabric, develop chaincode, and manage member governance.
Choosing Between Managed Blockchain and QLDB
Managed Blockchain is a managed service for Hyperledger Fabric 2.2 LTS that lets you build private blockchain networks for multiple organizations, with up to 14 members in the Standard edition. AWS has announced that it will stop accepting new customers on October 29, 2026, and end support for Managed Blockchain on September 29, 2027. While QLDB provided an immutable ledger within a single organization, Managed Blockchain enables distributed trust across multiple organizations. Note that QLDB was discontinued on July 31, 2025; for single-organization audit trails, the official migration target is an audit-table design on Aurora PostgreSQL.
Network Setup and Chaincode Development
You can create a network through the console or API by specifying the framework (Hyperledger Fabric), edition (Starter or Standard), and voting policy. When you create a member, peer nodes and a CA are automatically provisioned. Chaincode is Hyperledger Fabric's smart contract that defines business logic. It supports Fabric 2.2 LTS and can be developed in Go, Node.js, or Java. You install it on peer nodes, approve it, and then commit it to a channel. Chaincode implements transaction validation rules, data read/write logic, and access control. One possible workflow is to test on a local Hyperledger Fabric network in your development environment, then deploy to Managed Blockchain after verification.
Governance and Operations
Managed Blockchain's vote-based governance lets network participants vote on adding or removing members. You can choose from majority, unanimous, or a specific percentage for the voting policy. Each member operates their own peer nodes and shares data through channels. Channels can consist of a subset of members, allowing you to restrict specific transactions to only the relevant parties. Peer node scaling is handled by changing the instance type to accommodate increasing transaction volumes. CloudWatch metrics let you monitor transaction commit latency and throughput to detect performance degradation early.
Managed Blockchain Pricing
Managed Blockchain pricing consists of membership (network participation fee), peer nodes, and storage. Starter edition membership is about 0.30 USD per hour (about 216 USD per month), and Standard edition is about 0.65 USD (about 468 USD per month) (as of August 2026). Peer nodes start at about 0.034 USD per hour (about 24 USD per month) with bc.t3.small. Because of the nature of blockchain, the cost of the whole network increases as more members participate, so it is important to agree in advance on a cost-sharing model among the participating organizations. For development and test environments, the Starter edition is sufficient.
When Blockchain Is a Good Fit
Blockchain is not a solution for everything, and it is important to identify the uses it suits. It delivers the most value when multiple organizations are involved and want to maintain a shared ledger in a relationship where they cannot fully trust one another. Its strength is that the parties can share transaction records without an intermediary and all hold a history that cannot be tampered with. Supply chain tracking, transaction records between organizations, and asset provenance management are typical examples. Conversely, for records managed by a single organization, an ordinary database is often enough. Whether the requirements of multiple parties, tamper resistance, and no intermediary all come together is the criterion for adopting it.
Member and Node Design
A Hyperledger Fabric network consists of participating organizations (members) and the peer nodes that hold the ledger. Each member operates peer nodes and validates and records transactions. Design components such as the mechanism that finalizes the order of transactions and channels that share information only among specific members according to your requirements. Use channel design to control whether all information is shown to everyone or limited to only some of the parties. Deciding node placement and how to divide channels based on the scale of the network and the relationships among participating organizations leads to the design of a blockchain platform that balances functionality and confidentiality.
Security and Access Control
In a blockchain, strictly managing who is a legitimate participant is a prerequisite. Certificates are issued to each member and user, and operation permissions are controlled based on that identity. Configure the network so that only authorized participants can join it and carry out transactions. Share information that requires confidentiality in limited channels, and do not show it to members who are not involved. The ledger itself is a robust record that cannot be tampered with, but participation management at the entrance and the confidentiality of the data handled require separate design. Combine identity management with certificates and the separation of information with channels to build a secure network.
Operational Monitoring and Scaling
To operate a blockchain network stably, continuously monitor the operating status and resource usage of each node. When transaction volume grows, add or strengthen peer nodes to increase processing capacity. Ledger data accumulates over time, so manage storage capacity in a planned way as well. When you update chaincode (the processing logic that runs on the ledger), reach agreement among the participating members and roll it out carefully. Also prepare governance procedures, such as new members joining or leaving, as part of operations. Precisely because the platform involves multiple organizations, careful monitoring and change management are the key to stable operations.
Summary
Managed Blockchain is a service for operating private blockchains across multiple organizations in a managed environment. It lets you delegate Hyperledger Fabric infrastructure management to AWS so you can focus on chaincode development and business logic.
References (Official AWS Resources)
The primary sources for this page are the official AWS website and documentation. Check the official pages below for the latest specifications and pricing.
If this page and the official documentation disagree, treat the official documentation as authoritative.