Amazon Managed Blockchain for Ethereum allows you to create nodes and join them to Ethereum public networks. A node is a computer that connects to a blockchain network. A blockchain network consists of multiple parties (or peers) connected each other in a decentralized way. We commonly refer to a node as a peer node. With Amazon Managed Blockchain, you are charged for the peer node, peer node storage, and the number of Ethereum requests you make.
The pricing below is for Amazon Managed Blockchain for Ethereum.
AWS Pricing Calculator
Calculate your Amazon Managed Blockchain and architecture cost in a single estimate.
Create your custom estimate now »
On-Demand peer node pricing
Amazon Managed Blockchain eliminates the overhead required to manually provision hardware and you can easily scale infrastructure up or down to meet the demands of your application. With Amazon Managed Blockchain peer node pricing, you pay for the nodes you create. You pay per second, with a 1 minute minimum.
Peer node storage
Ethereum peer nodes store a history of all the transactions on the network. With Amazon Managed Blockchain, your peer node storage automatically scales with your needs. Peer node storage is charged in GB per month increments.
Except as otherwise noted, our prices are exclusive of applicable taxes and duties, including VAT and applicable sales tax. For customers with a Japanese billing address, use of AWS is subject to Japanese Consumption Tax.
A request is an Ethereum API call to your node that transfers data to and from Ethereum networks. For example, a retailer can track the provenance information of rare collectibles by storing their business transactions on the Ethereum networks via API calls. Ethereum APIs enable you to read and write transactions, retrieve blocks, fetch logs, and subscribe to real-time events. With Managed Blockchain for Ethereum, charges for each request accrue in increments of 32 KB of data exchanged or 500 ms response time, whichever comes first. For example, for an API call that exchanged 32KB of data at a 300ms response time, you will be charged for one request. However, if the API call exchanged 60KB of data at 300 ms response time, you’ll be charged for two requests since the data exchanged was greater than 32KB but less than 64KB. For a 30 KB request at 600ms, you’ll again be charged for two requests since the response time exceeded 500ms. If the API call exchanged 64KB of data at 1000 ms response time, you’ll be charged for two requests.
You are an events company that is interested in joining the Ethereum main network to record and track event tickets. Your application requires you to provision two c5.large nodes for high availability. Each node has a 300GB ledger, and 30 million requests are made to these nodes during the month.
The monthly cost for this is:
Monthly on-demand peer node cost: 2 X ($0.136 per hr X 24hrs) X 30 days = $195.84
Monthly peer node storage cost: 2 X 300GB* X $0.10 per GB-month = $60
*Assuming main network ledger is 300GB
Monthly Requests: 30million X $3 per million = $90
Total Monthly Cost: $346