Run Your Own Mirror Node
Overview
A Hedera Mirror Node is a node that receives pre-constructed files from the Hedera Mainnet. These pre-constructed files include transaction records and account balance files. Transaction records include information about a transaction, like the transaction ID, transaction hash, account, etc. The account balance files give you a snapshot of the balances for all accounts at a given timestamp.
In this tutorial, you will run your own Hedera Mirror Node. You will need to create either a Google Cloud Platform (GCP) or an Amazon Web Services (AWS) account if you do not have one already. The Hedera Mirror Node object storage bucket, where you will pull the account balance and transaction data from, is stored in GCP or AWS bucket and is configured for requester pays. This means the mirror node operator is responsible for the operational costs of reading and retrieving data from the GCP/AWS. A GCP/AWS account will provide the necessary billing information for requesting the data.
Run Your Own Mirror Node with Google Cloud Storage (GCS)Run Your Mirror Node with Amazon Web Services S3 (AWS)Minimum Hardware Requirements & Associated Costs
To run a Hedera Mirror Node, you'll need specific hardware and resources. The recommended minimum requirements for running a Mirror Node, along with the associated costs, are outlined below.
Cloud SQL for PostgreSQL
Instance Type: db-highmem-4
Location: Iowa
Number of Instances: 1
Total hours per month: 730.0
SSD Storage: 250.0 GiB
Backup: 250.0 GiB
The estimated cost for Cloud SQL for PostgreSQL per month is USD 303.46.
*The Mainnet full node needs a much bigger database (50TB) for the complete transaction history.
PLEASE NOTE: These are estimated costs, and actual costs will vary depending on usage and any changes to the pricing of the resources used. Always refer to the most recent price lists from the respective services for accurate costs.
Last updated
