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/xrp/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
@@ -45,13 +45,13 @@ This is the Well-Architected checklist for XRP nodes implementation of the AWS B
45
45
|| Authorization and access control | Use instance profile with Amazon Elastic Compute Cloud (Amazon EC2) instances | This solution uses AWS Identity and Access Management (AWS IAM) role instead of IAM user. |
46
46
||| Following principle of least privilege access | Privileges are scoped down. |
47
47
|| Application security | Security focused development practices | cdk-nag is being used with appropriate suppressions. |
48
-
| Cost optimization | Service selection | Use cost effective resources |AWS Graviton-based Amazon EC2 instances are being used, which are cost effective compared to Intel/AMD instances. |
48
+
| Cost optimization | Service selection | Use cost effective resources |Cost efficient I3 instances are being used, which are ideal for high transaction and low latecy workloads. |
49
49
| Reliability | Resiliency implementation | Withstand component failures | This solution uses AWS Application Load Balancer with RPC nodes for high availability. |
50
50
|| 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. |
51
-
| Performance efficiency | Compute selection | How is compute solution selected? | Compute solution is selected based on best price-performance, i.e. AWS Graviton-based Amazon EC2 instances. |
51
+
| Performance efficiency | Compute selection | How is compute solution selected? | Compute solution is selected based on best price-performance. |
52
52
|| Storage selection | How is storage solution selected? | Storage solution is selected based on best price-performance. |
53
53
| Operational excellence | Workload health | How is health of workload determined? | Health of workload is determined via AWS Application Load Balancer Target Group Health Checks, on port 8545. |
54
-
| Sustainability | Hardware & services | Select most efficient hardware for your workload | This solution uses AWS Graviton-based Amazon EC2 instances which offer the best performance per watt of energy use in Amazon EC2. |
54
+
| Sustainability | Hardware & services | Select most efficient hardware for your workload | This solution uses I3 instance class which is Storage Optimized instances for high transaction and low latency. |
0 commit comments