Skip to content

Update access node specs #782

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 4 commits into from
May 15, 2024
Merged

Update access node specs #782

Changes from 3 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
b856fab
Update node-provisioning.md
vishalchangrani May 15, 2024
ca40118
Update node-provisioning.md
vishalchangrani May 15, 2024
bd941ce
Update node-provisioning.md
vishalchangrani May 15, 2024
7878d85
Update node-provisioning.md
vishalchangrani May 15, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 3 additions & 16 deletions docs/networks/node-ops/node-operation/node-provisioning.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ The hardware your Node will need varies depending on the role your Node will pla
| **Consensus** | 2 cores | 16 GB | 200 GB | n2-standard-4 | m6a.xlarge |
| **Execution** | 64 cores | 800 GB | 9 TB | n2-highmem-128 | r6i.32xlarge |
| **Verification** | 2 cores | 16 GB | 200 GB | n2-highmem-2 | r6a.large |
| **Access** | 4 cores | 16 GB | 750 GB | n2-standard-4 | m6i.xlarge |
| **Access** | 16 cores | 64 GB | 750 GB | n2-standard-16 | m6i.4xlarge |
| **Observer** | 2 cores | 4 GB | 300 GB | n2-standard-4 | m6i.xlarge |

_Note: The above numbers represent our current best estimate for the state of the network. These will be actively updated as we continue benchmarking the network's performance._
Expand All @@ -24,27 +24,14 @@ _Note: The above numbers represent our current best estimate for the state of th

Most of the load on your nodes will be messages sent back and forth between other nodes on the network. Make sure you have a sufficiently fast connection; we recommend at _least_ 1Gbps, and 5Gbps is better.

Each node will require either a static IPv4 address or a fixed DNS name. Either works, and we'll refer to this more generally as your 'Node Address' from here on out.
Each node will require a fixed DNS name and we will refer to this more generally as your 'Node Address' from here on out.

<Callout type="info" title="Node Address Requirements">
Your Node Address must be a publicly routable IPv4 address or valid DNS name
Your Node Address must be a publicly routable valid DNS name
that points to your node. This is how other nodes in the network will
communicate with you.
</Callout>

While both a static IPv4 and a domain name are possible, we prefer and recommend that node operators register their node under a domain that they control. This gives the Flow network more options for resiliency and resistance to adverse network conditions.

<Callout type="warning" title="Registering a domain name for your Flow Node">
Crash recovery and denial of service attacks are two concerns that operators can mitigate relying on each of DNS indirection and IP routing. The later requires more involvement.

Running a node behind an operator-controlled hostname (rather than "just" an IP) is a simple and cheap measure that:

- offers additional technical pathways to let operators improve resiliency and security,
- lets them opt in to those measures as a reaction to an attack,
- does not preclude any lower-level IP-based resiliency approaches.

</Callout>

Your firewalls must expose **TCP/3569** for Node communication. If you are running an Access Node, you must also expose the GRPC port **9000**.

![Flow Architecture](flow-architecture.png)
Expand Down
Loading