Tag: Amazon Managed Blockchain

This series of posts provides a comprehensive introduction to running IPFS (InterPlanetary File System) on AWS: In Part 1, we introduce the IPFS concepts and test IPFS features on an Amazon Elastic Compute Cloud (Amazon EC2) instance In Part 2, we propose a reference architecture and build an IPFS cluster on Amazon Elastic Kubernetes Service […]

This series of posts provides a comprehensive introduction to running IPFS (InterPlanetary File System) on AWS: In Part 1, we introduce the IPFS concepts and test IPFS features on an Amazon Elastic Compute Cloud (Amazon EC2) instance In Part 2, we propose a reference architecture and build an IPFS cluster on Amazon Elastic Kubernetes Service […]

IPFS (InterPlanetary File System) is a storage protocol that allows content to be stored in a decentralized manner on the global IPFS network, without relying on any central entity. IPFS-enabled applications can benefit from a high level of redundancy and low latency, because content can be replicated, looked up, and downloaded from nearby IPFS nodes. […]

This post builds upon the full-stack non-fungible token (NFT) development environment setup outlined in a previous post, which is considered a prerequisite to the topics we discuss in this post. Part 1 discussed how to set up a development environment; in this post we walk you through a complete NFT marketplace application using Amazon Managed […]

Amazon Managed Blockchain is a fully managed service that makes it easy to create and manage blockchain networks using the open-source blockchain framework Hyperledger Fabric. In this post, we explore how to use AWS CodePipeline and related services to automate the deployment of chaincode. Chaincode is a program that typically handles business logic agreed to […]

This post discusses how these telecommunication companies used Amazon Managed Blockchain to build a universal mobile identity card platform and how this service works.

In the first post of this series, you learned how to build a Hyperledger Fabric network using Amazon Managed Blockchain. In this post, you deploy and run Hyperledger Explorer to visualize the Fabric network that you created.

This post demonstrates how to set up a blockchain application written in Java to read and write data to Managed Blockchain using the Fabric Java SDK. The Java SDK allows customers with applications written in Java to integrate blockchain support with their existing codebase. This makes it easier to handle rich data structures and complex business logic before writing records to the blockchain. You can also integrate Managed Blockchain using the Fabric Node.js SDK. For more information, see Building serverless blockchain application with Fabric Node.js SDK.

Many AWS customers use AWS Organizations and shared virtual private clouds (VPCs) to reduce operational costs and optimize the use of shared resources. For example, shared VPCs allow you to segregate ownership between systems management and application development teams. For more information, see VPC sharing: A new approach to multiple accounts and VPC management. Using […]

This is a guest post from Sammy Jordan, Assistant Treasurer at Contura Energy, in partnership with Emile Baizel, Sr. Blockchain Architect at AWS. In their own words, “Contura Energy is a Tennessee-based coal supplier with affiliate mining operations across major coal basins in Virginia, West Virginia, and Pennsylvania. We export metallurgical coal, a key raw material in steelmaking, to customers on five continents and approximately 25 countries.” Contura chose to run the blockchain network on Amazon Managed Blockchain because it’s a fully managed service that scales automatically, as needed, and removes a lot of the heavy lifting needed to operate a blockchain network. Additionally, you can easily integrate Managed Blockchain with other AWS services, and Managed Blockchain simplifies growing and administering the blockchain network. Network governance and inviting new members can be done via the AWS Management Console, and each member is billed separately based on their own usage.