Merge branch 'main' into vec4/allora-cdk

Author: Madisonw

.github/workflows/website-deploy.yaml

@@ -19,7 +19,7 @@ jobs:
       - uses: actions/checkout@v2
       - uses: actions/setup-node@v3
         with:
-          node-version: 18
+          node-version: 19
           cache: npm
           cache-dependency-path: website/package-lock.json
       - name: Install dependencies

.github/workflows/website-test-deploy.yml

@@ -17,7 +17,7 @@ jobs:
       - uses: actions/checkout@v2
       - uses: actions/setup-node@v3
         with:
-          node-version: 18
+          node-version: 19
           cache: npm
           cache-dependency-path: website/package-lock.json
 

.pre-commit-config.yaml

@@ -11,3 +11,7 @@ repos:
       - id: detect-aws-credentials
         args: ['--allow-missing-credentials']
       - id: forbid-submodules
+  - repo: https://github.com/iamthefij/docker-pre-commit
+    rev: master
+    hooks:
+      - id: docker-compose-check

README.md

@@ -1,13 +1,13 @@
 # AWS Blockchain Node Runners
 
-This repository contains sample [AWS Cloud Development Kit (CDK)](https://aws.amazon.com/cdk/) applications (Node Runner Blueprints) to deploy on AWS self-service blockchain nodes for various protocols. For more information see [Introducing AWS Blockchain Node Runners](https://aws-samples.github.io/aws-blockchain-node-runners/docs/intro).
+This repository contains sample [AWS Cloud Development Kit (CDK)](https://aws.amazon.com/cdk/) applications (Node Runner Blueprints) to deploy on AWS self-service blockchain nodes for various protocols. For more information, see [Introducing AWS Blockchain Node Runners](https://aws-samples.github.io/aws-blockchain-node-runners/docs/intro).
 
 ### Documentation
-For deployment instructions see [AWS Blockchain Node Runners Blueprints](https://aws-samples.github.io/aws-blockchain-node-runners/docs/Blueprints/intro)
+For deployment instructions, see [AWS Blockchain Node Runners Blueprints](https://aws-samples.github.io/aws-blockchain-node-runners/docs/Blueprints/intro).
 
 ### Adding blueprints for new nodes
 
-If you'd like propose a Node Runner Blueprint for your node see [Adding new Node Runner Blueprints](./docs/adding-new-nodes.md)
+If you'd like propose a Node Runner Blueprint for your node, see [Adding new Node Runner Blueprints](./docs/adding-new-nodes.md).
 
 ### Directory structure
 
@@ -19,7 +19,7 @@ If you'd like propose a Node Runner Blueprint for your node see [Adding new Node
 - `website/docs` - Place for the new blueprint deployment instructions. (If you are adding a new blueprint, use on of the existing examples to refer to the `README.md` file within your Node Runner Blueprint directory inside `lib`).
 
 ### License
-This repository uses MIT License. See more in [LICENSE](./LICENSE)
+This repository uses MIT License. See more in [LICENSE](./LICENSE).
 
 ### Contributing
 See [CONTRIBUTING](./CONTRIBUTING.md) for more information.

docs/setup-cloud9.md

@@ -1,3 +1,14 @@
+# AWS CloudShell
+
+To begin, ensure you login to your AWS account with permissions to create and modify resources in IAM, EC2, EBS, VPC, S3, KMS, and Secrets Manager.
+
+From the AWS Management Console, open the [AWS CloudShell](https://docs.aws.amazon.com/cloudshell/latest/userguide/welcome.html), a web-based shell environment. If unfamiliar, review the [2-minute YouTube video](https://youtu.be/fz4rbjRaiQM) for an overview and check out [CloudShell with VPC environment](https://docs.aws.amazon.com/cloudshell/latest/userguide/creating-vpc-environment.html) that we'll use to test nodes API from internal IP address space.
+
+Once ready, you can execute the commands to deploy and test blueprints in the CloudShell.
+
+***
+# AWS Cloud 9 IS NO LONGER USED (the instructions below will be removed soon, use AWS CloudShell instead)
+***
 # AWS Cloud9 Setup
 
 Most steps in this repository will need to be performed from a Linux command prompt. An especially convenient way of doing this is to use AWS Cloud9, a cloud-based Integrated Development Environment (IDE). Cloud9 allows you to edit source files and execute commands from an easy-to-use web interface. It comes pre-configured with many of the tools needed for software development, and because it runs in the AWS Cloud, it can be an especially easy way to access other cloud services. One other handy feature is that your Cloud9 instances automatically stop running after a configurable period of inactivity, which helps reduce costs.
@@ -16,18 +27,18 @@ Create an instance profile called **Cloud9-Developer-Access**
 
 ```bash
 cat > ec2-trust-policy.json <<EOF
-    {
-    "Version": "2012-10-17",
-        "Statement": [
-            {
-            "Effect": "Allow",
-            "Principal": {
-            "Service": "ec2.amazonaws.com"
-            },
-            "Action": "sts:AssumeRole"
-            }
-        ]
-    }
+{
+"Version": "2012-10-17",
+    "Statement": [
+        {
+        "Effect": "Allow",
+        "Principal": {
+        "Service": "ec2.amazonaws.com"
+        },
+        "Action": "sts:AssumeRole"
+        }
+    ]
+}
 EOF
 ```
 

lib/base/.gitignore

@@ -0,0 +1,11 @@
+*.js
+!jest.config.js
+*.d.ts
+node_modules
+
+# CDK asset staging directory
+.cdk.staging
+cdk.out
+.idea
+
+*-node.json

lib/base/.npmignore

@@ -0,0 +1,6 @@
+*.ts
+!*.d.ts
+
+# CDK asset staging directory
+.cdk.staging
+cdk.out