You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: lib/solana/README.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -67,7 +67,7 @@ This is the Well-Architected checklist for Solana nodes implementation of the AW
67
67
||| Following principle of least privilege access | In all node types, root user is not used (using special user "solana" instead). |
68
68
|| Application security | Security focused development practices | cdk-nag is being used with appropriate suppressions. |
69
69
| Cost optimization | Service selection | Use cost effective resources | 1/ AMD-based instances are used for Consensus and RPC node to save the costs. Consider compiling Graviton-based binaries to improve costs for compute. 2/ Cost-effective EBS gp3 are preferred instead of io2. 3/ Solana nodes generate a substantial amount of outgoing data traffic, which deeds to be addressed with non-technical means like getting private agreements with AWS. |
70
-
|| Cost awareness | Estimate costs | Single RPC node with `r6a.8xlarge` EBS gp3 volumes about 2549 GB with On-Demand pricing will cost around US$1,596.43 per month in the US East (N. Virginia) region. More cost-optimal option with 3 year Compute Savings plan the cost goes down to $962.84 USD. Additionally, the data transfer costs can be about $1,356.80 USD per month for 15TB of outgoing traffic. |
70
+
|| Cost awareness | Estimate costs | Single RPC node with `r7a.12xlarge` EBS gp3 volumes about 2549 GB with On-Demand pricing will cost around US$2,665.67 per month in the US East (N. Virginia) region. More cost-optimal option with 3 year Compute Savings plan the cost goes down to $1,643.52 USD. Additionally, the data transfer costs can be about $1,356.80 USD per month for 15TB of outgoing traffic. Check pricing with [AWS Calculator](https://calculator.aws/)|
71
71
| Reliability | Resiliency implementation | Withstand component failures | This solution uses AWS Application Load Balancer with RPC nodes for high availability. Newly provisioned Solana nodes triggered by Auto Scaling get up and running in about 30-50 minutes. |
72
72
|| Data backup | How is data backed up? | Considering blockchain data is replicated by nodes automatically and Solana nodes sync from start within an hour, we don't use any additional mechanisms to backup the data. |
73
73
|| Resource monitoring | How are workload resources monitored? | Resources are being monitored using Amazon CloudWatch dashboards. Amazon CloudWatch custom metrics are being pushed via CloudWatch Agent. |
@@ -85,8 +85,8 @@ This is the Well-Architected checklist for Solana nodes implementation of the AW
85
85
| Usage pattern | Ideal configuration | Primary option on AWS | Data Transfer Estimates | Config reference |
86
86
|---|---|---|---|---|
87
87
| 1/ Consensus node | 48 vCPU, 384 GiB RAM, Accounts volume: 500GiB, 7K IOPS, 700 MB/s throughput, Data volume: 2TB, 9K IOPS, 700 MB/s throughput | r7a.12xlarge, Accounts volume: 500GiB, 7K IOPS, 700 MB/s throughput, Data volume: 2TB, 9K IOPS, 700 MB/s throughput | Proportional to the amount at stake. Between 200TB to 400TB/month |[.env-sample-consensus](./sample-configs/.env-sample-consensus)|
Copy file name to clipboardExpand all lines: lib/solana/sample-configs/.env-sample-extendedrpc
+3-3Lines changed: 3 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -16,12 +16,12 @@ SOLANA_CPU_TYPE="x86_64" # All options: "x86_64", "ARM_64".
16
16
# Data volume configuration
17
17
SOLANA_DATA_VOL_TYPE="gp3" # Other options: "io1" | "io2" | "gp3" | "instance-store" . IMPORTANT: Use "instance-store" option only with instance types that support that feature, like popular for node im4gn, d3, i3en, and i4i instance families
18
18
SOLANA_DATA_VOL_SIZE="2000" # Current required data size to keep both smapshot archive and unarchived version of it
19
-
SOLANA_DATA_VOL_IOPS="9000" # Max IOPS for EBS volumes (not applicable for "instance-store")
19
+
SOLANA_DATA_VOL_IOPS="12000" # Max IOPS for EBS volumes (not applicable for "instance-store")
20
20
SOLANA_DATA_VOL_THROUGHPUT="700" # Max throughput for EBS gp3 volumes (not applicable for "io1" | "io2" | "instance-store")
21
21
# Accounts volume configuration
22
-
SOLANA_ACCOUNTS_VOL_TYPE="gp3" # Other options: "io1" | "io2" | "gp3" | "instance-store" . IMPORTANT: Use "instance-store" option only with instance types that support that feature, like popular for node im4gn, d3, i3en, and i4i instance families
22
+
SOLANA_ACCOUNTS_VOL_TYPE="io2" # Other options: "io1" | "io2" | "gp3" | "instance-store" . IMPORTANT: Use "instance-store" option only with instance types that support that feature, like popular for node im4gn, d3, i3en, and i4i instance families
23
23
SOLANA_ACCOUNTS_VOL_SIZE="500" # Current required data size to keep both smapshot archive and unarchived version of it
24
-
SOLANA_ACCOUNTS_VOL_IOPS="4000" # Max IOPS for EBS volumes (not applicable for "instance-store")
24
+
SOLANA_ACCOUNTS_VOL_IOPS="7000" # Max IOPS for EBS volumes (not applicable for "instance-store")
25
25
SOLANA_ACCOUNTS_VOL_THROUGHPUT="700" # Max throughput for EBS gp3 volumes (not applicable for "io1" | "io2" | "instance-store")
26
26
# Secrets configuration
27
27
SOLANA_NODE_IDENTITY_SECRET_ARN="none" # Optional. The ARN of the secret in AWS Secrets Manager with the node identity key pair. In case you want to provision a node but keep the old identity.
0 commit comments