Practical overview
When it fits
Use it when you need an AWS-based environment to deploy a supported blockchain node or compare infrastructure configurations. The repository offers AI-assisted and manual deployment paths.
Who it is for
- Teams deploying or testing blockchain nodes on AWS.
- Developers comparing node instance types, storage options or deployment modes.
- Protocol developers exploring the built-in or externally installed blueprint approach.
Documented uses
- Deploy a configured blockchain node on AWS.
- Compare single-node and high-availability deployment modes.
- Iterate on instance and storage choices, with optional AI-assisted configuration and troubleshooting.
- Select a built-in protocol blueprint or install an external blueprint.
Requirements & limits
The project is a public GitHub repository under the MIT-0 license. Deployment requires an AWS account, credentials and specified AWS resource permissions; no service price is stated.
- The primary deployment target is AWS, using AWS CDK.
- The README specifies Node.js 20 or later and AWS CLI as prerequisites.
- Single-node mode is described for testing; high availability is for evaluating production-like scenarios.
- Kiro CLI is optional and recommended for the AI-driven workflows; Python and uv are optional for MCP servers.
- The repository lists Ubuntu 24.04 LTS across x86_64 and ARM_64 deployments.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Prepare the project in AWS CloudShell
Clone the repository, install and build its dependencies, bootstrap CDK for the selected AWS account and region, and authenticate Kiro CLI.
Before you start
- AWS CloudShell with the documented Node.js, AWS CLI, and Git tools available.
- AWS credentials configured for an account with permissions to create the required resources.
- Kiro CLI available in CloudShell and an AWS Builder ID for authentication.
Steps
Clone the repository and enter its directory: the command below then
cd aws-blockchain-node-runners.git clone https://github.com/aws-samples/aws-blockchain-node-runners.gitInstall dependencies and build: the command below followed by the command below.
npm installnpm run buildBootstrap CDK in the configured account and region:
AWS_ACCOUNT_ID=$(aws sts get-caller-identity --query Account --output text);AWS_REGION=$(aws configure get region); the command below.npx cdk bootstrap aws://$AWS_ACCOUNT_ID/$AWS_REGIONAuthenticate Kiro CLI with
kiro-cli auth loginand follow the prompts.
Expected outcome
The repository is cloned, dependencies are installed and built, CDK is bootstrapped for the selected account and region, and Kiro CLI is authenticated. The documented next stage is the Deploy workflow in the Quickstart guide.
Guide limitations
- CDK bootstrap is required once per account and region.
- This recipe prepares the project; it does not deploy a node.
- The documented AWS CloudShell route assumes its tools and AWS credentials are already configured.
Deploy a node with the Kiro CLI deploy workflow
Use the documented Kiro CLI prompt to deploy a blockchain node configuration after completing project setup.
Before you start
- Complete the Quickstart setup: clone the repository, install dependencies, build, bootstrap CDK, and authenticate Kiro CLI.
- An AWS account and credentials with permissions to create the resources needed by the deployment.
Steps
Start the Kiro CLI in the prepared repository environment.
Invoke the deploy prompt with a protocol and network, for example:
@deploy Deploy an Ethereum mainnet full node.Follow the workflow, which recommends infrastructure, generates configuration files, and executes the CDK deployment.
Expected outcome
The workflow is intended to deploy the requested node configuration as an independent stack. The Quickstart guide also describes repeating the workflow for Ethereum, Solana, Base, BNB Chain, or Bitcoin.
Guide limitations
- The documented example does not specify the generated configuration values or guarantee deployment success.
- The AWS account must have permissions for the resources required by the chosen deployment.
- This guide covers the deployment prompt only; healthchecks and troubleshooting are separate workflows.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 13 October 2026
- Original website title
- aws-samples/aws-blockchain-node-runners · Official homepage title · retained in its source language

