Guidance for Automating Ethereum Node Validator using AWS Graviton

In this architecture, we use infrastructure as code (IaC) to deploy AWS resources in a reliable and repeatable way. AWS CDK is a key aspect of achieving IaC in this Guidance. AWS CDK is an open-source software development framework that enables the creation and deployment of AWS resources using familiar programming languages such as TypeScript, Python, and Java. It allows developers to define cloud infrastructure in code, which can then be versioned, reviewed, and tested like any other software code.

Using AWS CDK to deploy AWS resources provides several technical benefits, including repeatability and consistency, higher-level abstraction, code reuse, and support for standard software development practices. These benefits can help improve the reliability and efficiency of the deployment process, reducing the risk of errors and improving the overall quality of the AWS resources.

Read the Operational Excellence whitepaper

This architecture uses Systems Manager to access resources instead of using secure shell (SSH) access (which can be a security risk if not properly managed). To minimize the attack surface, no ports are open. Systems Manager enables secure remote management of instances, making it easier to manage instances across multiple accounts and AWS Regions. In addition to Systems Manager, this architecture uses AWS Identity and Access Management (IAM) to manage user access to resources. With Systems Manager and IAM, only authorized users will have access to AWS resources, reducing the risk of unauthorized access and data breaches. Systems Manager and IAM also provide audit trails and monitoring capabilities, enabling you to track user activity and identify any potential security issues.

Read the Security whitepaper

This is a loosely-coupled microservices architecture, where everything runs as a Docker container. A loosely coupled microservices architecture provides several benefits for building a reliable system, including increased flexibility and agility, better fault isolation, improved resource utilization, and enhanced testing and debugging capabilities.

Additionally, using Prometheus and Grafana as a containerized monitoring stack supports log collection and metrics visualization. Prometheus is an open-source monitoring system that collects and stores time-series data from various sources, including applications and systems. Grafana is a visualization tool that provides a powerful and user-friendly dashboard for displaying metrics and logs collected by Prometheus. The combination of Prometheus and Grafana provides a powerful and comprehensive monitoring solution for AWS resources. The ability to collect and store time-series data and visualize it in an application and user-friendly dashboard enables easy monitoring and troubleshooting of this Guidance, improving the reliability and performance of the AWS resources and reducing the risk of downtime or performance issues to adjacent systems.

Read the Reliability whitepaper

Scaling, traffic patterns, and data access patterns are important considerations when designing a blockchain node architecture, as they can have a significant impact on the performance and reliability of the node.

Scaling is the ability of the blockchain node to handle increasing numbers of transactions and users. With this Guidance, a single AWS CDK command can increase the number of nodes in the network, which helps distribute the load and improve performance.

Traffic patterns are types of requests and data that are sent and received by the blockchain node. Data access patterns are how data is accessed and queried from the blockchain database. Understanding traffic patterns and data access patterns can help you optimize the performance of the node, allocate resources appropriately, and improve the user experience. The Prometheus and Grafana containers can help with monitoring and visualizing these metrics.

Read the Performance Efficiency whitepaper

We use a c6g.2xlarge AWS Graviton-based instance based on Rocket Pool's current recommendation. This is the optimized instance for this blockchain deployment. After the node validator is deployed, we recommend using AWS Cost Explorer to evaluate the cost of the c6g.2xlarge instance over time and to identify any potential savings opportunities. Additionally, we recommend using Amazon EC2 Reserved Instances (RIs), which can provide a discount of up to 72% compared to on-demand pricing. By continuously evaluating the cost of the selected instance type and identifying opportunities to optimize, you can use the most cost-effective services without compromising on performance or reliability.

This is a single node architecture. Blockchain nodes are highly decentralized, meaning you can spin up new nodes with single AWS CDK command. In this architecture, you do not need automatic scaling mechanisms to save on costs.

Read the Cost Optimization whitepaper

In this Guidance, we prioritize energy efficiency, reduce hardware requirements, and minimize the carbon footprint of running the node. We run the validator node on AWS Graviton-based instances, which use a lower energy footprint and cost less. The validator node in this Guidance uses a lightweight Ethereum client (Geth), which consumes fewer resources than a full node.

The validator node stores data on a solid-state drive (SSD) rather than a traditional hard disk drive (HDD), because SSDs are energy-efficient and have a longer lifespan. By adopting a minimalistic architecture, the Ethereum node validator in this Guidance can significantly reduce its energy consumption and carbon footprint, contributing to a more sustainable blockchain network.

Read the Sustainability whitepaper