Skip to content

Commit 401f47f

Browse files
committed
Theta. Corrected pricing example in the README
1 parent 70766c5 commit 401f47f

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

lib/theta/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ This is the Well-Architected checklist for Edge nodes implementation of the AWS
3737
| | | Following principle of least privilege access | In all node types, root user is not used (using special user "bcuser" instead). |
3838
| | Application security | Security focused development practices | cdk-nag is being used with appropriate suppressions. |
3939
| Cost optimization | Service selection | Use cost effective resources | Although we can run the Edge Node without a GPU, we choose to use a `g4dn.xlarge` w/ a T4 GPU & 256gb GP3 EBS Storage to take advantage of the jobs the Theta Edge Network has to offer|
40-
| | Cost awareness | Estimate costs | Single RPC node with `g4dn.xlarge` EBS gp3 volumes about 256 GB(10000 IOPS, 125 MBps/s throughput) with On-Demand pricing will cost around US$296.81 per month in the US East (N. Virginia) region. More cost-optimal option with 3 year EC2 Instance Savings plan the cost goes down to $159.80 USD. To create your own estimate use [AWS Pricing Calculator](https://calculator.aws/#/) |
40+
| | Cost awareness | Estimate costs | Single RPC node with `g4dn.xlarge` EBS gp3 volumes about 256 GB(10000 IOPS, 125 MBps/s throughput) with On-Demand pricing will cost around US$439.46 per month in the US East (N. Virginia) region. More cost-optimal option with 3 year EC2 Instance Savings plan the cost goes down to $254.77 USD. To create your own estimate use [AWS Pricing Calculator](https://calculator.aws/#/) |
4141
| Reliability | Resiliency implementation | Withstand component failures | Docker service and Edge Node container is set to always restart in the case of an EC2 outage. There is no restart mechanism on the single node instance as of now. |
4242
| | Data backup | How is data backed up? | Considering blockchain data is replicated by nodes automatically and Theta nodes sync on run, we don't use any additional mechanisms to backup the data. |
4343
| | 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. |

0 commit comments

Comments
 (0)