Community Note
- Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
- Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
- If you are interested in working on this issue or have submitted a pull request, please leave a comment
What is the outcome that you are trying to reach?
Run Polygon PoS full nodes on AWS using the Node Runners framework, with both single-node and highly-available deployment options.
Polygon PoS is one of the most widely adopted EVM-compatible chains, particularly in FinTech and VASP (Virtual Asset Service Provider) sectors. Despite its popularity, there is currently no Node Runners blueprint for it — the previous issue #7 was closed as stale without implementation.
Describe the solution you would like
A Polygon PoS blueprint under lib/polygon/ using Erigon (0xpolygon/erigon) as a single-container all-in-one client.
Why Erigon: During implementation, we discovered that the traditional Heimdall+Bor dual-container approach is currently unreliable:
- Polygon's Heimdall v1→v2 migration (completed for Amoy testnet, in progress for mainnet) breaks P2P connectivity for v1 clients
- The Heimdall v2 Docker image (
0xpolygon/heimdall-v2) has init bugs that prevent startup — reported in heimdall-v2#568
Erigon solves this by connecting to Polygon's official Heimdall API endpoint (--bor.heimdall=https://heimdall-api.polygon.technology) instead of running a local Heimdall node. This is:
- Simpler (one container vs two)
- More reliable (no Heimdall v1/v2 migration issues)
- Consistent with Erigon's official Polygon support
- Built-in OtterSync for torrent-based snapshot sync (no manual snapshot download needed)
Scope:
- Single node deployment (
polygon-single-node)
- Highly available RPC nodes with ALB + ASG (
polygon-ha-nodes)
- Mainnet + Amoy testnet configurations
- Graviton (ARM) support via
0xpolygon/erigon:v3.4.0
- CloudWatch metrics cron
Hardware (Mainnet):
| Component |
Spec |
| Instance |
m7g.4xlarge (Graviton3, 16 vCPU, 64 GB) |
| Storage |
8 TB gp3, 16,000 IOPS, 1,000 MB/s |
| Est. cost |
~$1,100/month per node (us-east-1) |
Describe alternatives you have considered
- Heimdall + Bor (traditional) — Blocked by Heimdall v1→v2 migration and Docker image bugs
- Manual Docker Compose without CDK — Works but lacks IaC benefits, CloudWatch integration, and reproducibility
Additional context
Community Note
What is the outcome that you are trying to reach?
Run Polygon PoS full nodes on AWS using the Node Runners framework, with both single-node and highly-available deployment options.
Polygon PoS is one of the most widely adopted EVM-compatible chains, particularly in FinTech and VASP (Virtual Asset Service Provider) sectors. Despite its popularity, there is currently no Node Runners blueprint for it — the previous issue #7 was closed as stale without implementation.
Describe the solution you would like
A Polygon PoS blueprint under
lib/polygon/using Erigon (0xpolygon/erigon) as a single-container all-in-one client.Why Erigon: During implementation, we discovered that the traditional Heimdall+Bor dual-container approach is currently unreliable:
0xpolygon/heimdall-v2) has init bugs that prevent startup — reported in heimdall-v2#568Erigon solves this by connecting to Polygon's official Heimdall API endpoint (
--bor.heimdall=https://heimdall-api.polygon.technology) instead of running a local Heimdall node. This is:Scope:
polygon-single-node)polygon-ha-nodes)0xpolygon/erigon:v3.4.0Hardware (Mainnet):
Describe alternatives you have considered
Additional context