modified instance type and fixed cw dashboard

Author: Simon Goldberg

lib/xrp/README.md

@@ -45,13 +45,13 @@ This is the Well-Architected checklist for XRP nodes implementation of the AWS B
 |                         | 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.  |
 |                         |                                   | Following principle of least privilege access                                    | Privileges are scoped down.  |
 |                         | Application security              | Security focused development practices                                           | cdk-nag is being used with appropriate suppressions.  |
-| 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.  |
+| Cost optimization       | Service selection                 | Use cost effective resources                                                     | Cost efficient R7a instances are being used, which are ideal for high transaction and low latecy workloads.  |
 | Reliability             | Resiliency implementation         | Withstand component failures                                                     | This solution uses AWS Application Load Balancer with RPC nodes for high availability. |
 |                         | 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.  |
 | Performance efficiency  | Compute selection                 | How is compute solution selected?                                                | Compute solution is selected based on best price-performance.  |
 |                         | Storage selection                 | How is storage solution selected?                                                | Storage solution is selected based on best price-performance. |
 | 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.  |
-| Sustainability          | Hardware & services               | Select most efficient hardware for your workload                                 | Amazon EC2 I3 instances support the Sustainability Pillar of the AWS Well-Architected Framework by offering high-performance, storage-optimized computing that enables more efficient resource utilization, potentially reducing overall energy consumption and hardware requirements for data-intensive workloads.  |
+| Sustainability          | Hardware & services               | Select most efficient hardware for your workload                                 | Amazon EC2 R7a instances support the Sustainability Pillar of the AWS Well-Architected Framework by offering memory optimization that enables more efficient resource utilization, potentially reducing overall energy consumption and hardware requirements for data-intensive workloads.  |
 
 </details>
 

lib/xrp/sample-configs/.env-sample-mainnet

@@ -1,6 +1,6 @@
 AWS_ACCOUNT_ID="xxxxxxxxxxx"
 AWS_REGION="xxxxxxxxxx"
-XRP_INSTANCE_TYPE="i3.2xlarge"         #The solution was originally tested with the r7a.12xlarge instance type. Other instance types may work, but have not been extensively tested. i3.2xlarge is recommended for use by XRP Ledger
+XRP_INSTANCE_TYPE="r7a.2xlarge"         #The solution was originally tested with the r7a.12xlarge instance type. Other instance types will work, but have not been extensively tested.
 XRP_CPU_TYPE="x86_64" # All options: "x86_64". ARM currently not supported
 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
 DATA_VOL_SIZE="2000"                   # Current required data size to keep both smapshot archive and unarchived version of it

lib/xrp/sample-configs/.env-sample-testnet

@@ -1,6 +1,6 @@
 AWS_ACCOUNT_ID="xxxxxxxxxxx"
 AWS_REGION="xxxxxxxxxx"
-XRP_INSTANCE_TYPE="i3.2xlarge"         #The solution was originally tested with the r7a.12xlarge instance type. Other instance types may work, but have not been extensively tested. i3.2xlarge is recommended for use by XRP Ledger
+XRP_INSTANCE_TYPE="r7a.2xlarge"         #The solution was originally tested with the r7a.12xlarge instance type. Other instance types will work, but have not been extensively tested.
 XRP_CPU_TYPE="x86_64" # All options: "x86_64". ARM currently not supported
 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
 DATA_VOL_SIZE="2000"                   # Current required data size to keep both smapshot archive and unarchived version of it