Skip to main content

4. Avalanche Nodes Creation

caution

The Ash Console is currently in beta and not production-ready. It is under active development and subject to breaking changes.

danger

Running this step will occur costs on your cloud provider account.

We can finally deploy our 5 Avalanche node resources!

From the Ash Console project overview page, navigate to the Ressources tab:

  • Click on the Create Node(s) button.
  • Set local-node-01 for the name of the first node.
  • Select the cloud region you added in the previous step.
  • Choose a VM size between small, medium, and large (see Resource sizes for details on available sizes).
    For a devnet node, we recommend the small size.
  • Select the local-node-id-01 secret you created in the previous step.
  • (Optional) Configure the node with custom configurations if needed. See the ash.avalanche.node reference doc for a list of all supported configuration keys.
  • Click on the + button and repeat the process to add the 4 other nodes.

Ash Console nodes create

tip

Make sure to select the appropriate Node ID secret for each node and that the Bootstrap node option is ticked for the first node only.

Once the 5 nodes are in the list, click on the Create button.

The nodes will then be created one by one, this step can take up to a minute depending on the cloud provider:

Ash Console nodes creating

Health

It will take a few minutes before the local network is Bootstrapped and Healthy. You can get its updated status by clicking on the node name in the list of resources:

Ash Console node list

tip

You can SSH into any Ash Console-created resource. See SSH to a resource for details.

Once a node is Running, you can also query the node info endpoint with the avalanche node info command:

Command
ash avalanche node info -n 3.138.100.201
Output
Node '3.138.100.201:9650':
ID: NodeID-7Xhw2mDxuDS44j42TCB6U5579esbSt3Lg
Signer (BLS):
Public key: 0x900c9b119b5c82d781d4b49be78c3fc7ae65f2b435b7ed9e3a8b9a03e475edff86d8a64827fec8db23a6f236afbf127d
PoP: 0x8bfd6d4d2086b2b8115d8f72f94095fefe5a6c07876b2accf51a811adf520f389e74a3d2152a6d90b521e2be58ffe468043dc5ea68b4c44410eb67f8dc24f13ed4f194000764c0e922cd254a3588a4962b1cb4db7de4bb9cda9d9d4d6b03f3d2
Network: local
Public IP: 3.138.100.201
Staking port: 9651
Versions:
AvalancheGo: avalanchego/1.11.11
Database: v1.4.5
RPC Protocol: 37
Git commit: d3c09eb19d6e8c85a4757f17cd5da7e713c2baba
VMs:
AvalancheVM: v1.11.11
Coreth: v0.13.7
PlatformVM: v1.11.11
Subnet VMs:
'srEXiWaHuhNyGwPUi444Tu47ZEDwxTWrbQiuD7FmgSAQ6X7Dy': v0.6.10
Uptime:
Rewarding stake: 100%
Weighted average: 100%
note

Your node IP address will be different.

Your local Avalanche network is now up and running!

note

See the reference for more information about resources lifecycle management.