@twin.org/node 0.0.3-next.10

package/docs/configuration.md

@@ -0,0 +1,223 @@
+# @twin.org/node - Configuration
+
+## Extension Loading
+
+The TWIN Node supports loading extensions dynamically to extend its functionality. Extensions can be loaded from multiple sources using protocol-based syntax.
+
+### Extension Loading Syntax
+
+Extensions are configured via the `TWIN_EXTENSIONS` environment variable. Multiple extensions can be specified as a comma-separated list.
+
+#### Local File Extensions
+
+Load extensions from the local filesystem:
+
+```bash
+# Relative path
+TWIN_EXTENSIONS="./my-extension.mjs"
+
+# Absolute path
+TWIN_EXTENSIONS="/path/to/extension.mjs"
+```
+
+#### NPM Package Extensions
+
+Load extensions from npm packages. The package will be automatically downloaded and installed if not already cached:
+
+```bash
+# Basic npm package
+TWIN_EXTENSIONS="npm:@twin.org/identity-management-service"
+
+# Scoped package
+TWIN_EXTENSIONS="npm:@org/custom-extension"
+```
+
+**Note:** Version pinning (e.g., `npm:@twin.org/pkg@1.2.3`) is planned for a future release. Currently, the latest version is installed.
+
+#### HTTPS URL Extensions
+
+Load extensions from remote HTTPS URLs:
+
+```bash
+TWIN_EXTENSIONS="https://example.twin.org/extensions/my-module.mjs"
+```
+
+**⚠️ SECURITY WARNING:** Loading code from HTTPS URLs introduces security risks. Only load extensions from trusted sources that you control or verify.
+
+Security features:
+
+- Only HTTPS is allowed (HTTP is rejected)
+- Default 10 MB size limit to prevent DoS attacks
+- Downloaded modules are cached locally
+- Security warning is displayed when loading
+
+#### Multiple Extensions
+
+Load multiple extensions from different sources:
+
+```bash
+TWIN_EXTENSIONS="@twin.org/identity-management-service,npm:@twin.org/custom-service,./local-extension.mjs,https://example.com/remote.mjs"
+```
+
+### Extension Configuration Options
+
+#### Maximum Download Size
+
+Configure the maximum size (in MB) for HTTPS extension downloads:
+
+```bash
+TWIN_EXTENSIONS_MAX_SIZE_MB=10  # Default is 10 MB
+```
+
+#### Cache Management
+
+By default, downloaded extensions are cached in `.tmp/extensions/` directory to speed up subsequent startups. To clear the cache on each startup:
+
+```bash
+TWIN_EXTENSIONS_CLEAR_CACHE=true  # Default is false
+```
+
+#### Custom Cache Directory
+
+You can configure a custom directory for extension caching:
+
+```bash
+TWIN_EXTENSIONS_CACHE_DIRECTORY="cache"  # Default is ".tmp"
+```
+
+This allows you to:
+
+- Use a dedicated partition with more space
+- Separate cache by environment (dev/staging/prod)
+- Follow corporate storage policies
+- Create persistent cache directories for better performance
+
+### Extension API
+
+Extensions must export specific lifecycle methods to integrate with the node:
+
+#### `extensionInitialise(envVars, nodeEngineConfig)`
+
+Called during configuration phase. Allows the extension to modify environment variables and engine configuration.
+
+```typescript
+export async function extensionInitialise(
+  envVars: INodeEnvironmentVariables,
+  nodeEngineConfig: INodeEngineConfig
+): Promise<void> {
+  // Modify configuration here
+}
+```
+
+#### `extensionInitialiseEngine(engineCore)`
+
+Called after the engine is created but before the server starts.
+
+```typescript
+export async function extensionInitialiseEngine(engineCore: IEngineCore): Promise<void> {
+  // Register components, set up services, etc.
+}
+```
+
+#### `extensionInitialiseEngineServer(engineCore, engineServer)`
+
+Called after the engine server is created but before it starts listening.
+
+```typescript
+export async function extensionInitialiseEngineServer(
+  engineCore: IEngineCore,
+  engineServer: IEngineServer
+): Promise<void> {
+  // Add routes, configure server, etc.
+}
+```
+
+#### `extensionShutdown()`
+
+Called when the node is shutting down. Clean up resources here.
+
+```typescript
+export async function extensionShutdown(): Promise<void> {
+  // Clean up resources
+}
+```
+
+### Example Extension
+
+```typescript
+// my-extension.mjs
+export async function extensionInitialise(envVars, nodeEngineConfig) {
+  console.log('Extension initializing with config');
+}
+
+export async function extensionInitialiseEngine(engineCore) {
+  engineCore.logInfo('Custom extension loaded');
+}
+
+export async function extensionInitialiseEngineServer(engineCore, engineServer) {
+  // Add custom routes
+  engineServer.addRestRoute({
+    path: '/custom/endpoint',
+    method: 'GET',
+    handler: async () => ({ body: { message: 'Hello from extension!' } })
+  });
+}
+
+export async function extensionShutdown() {
+  console.log('Extension shutting down');
+}
+```
+
+### Cache Directory Structure
+
+Downloaded extensions are stored in:
+
+```text
+<execution-directory>/<cache-directory>/extensions/
+  ├── npm/                      # NPM packages
+  │   └── node_modules/
+  │       └── @twin.org/...
+  └── https/                    # HTTPS downloads
+      └── <hashed-filename>.mjs
+```
+
+Where `<cache-directory>` is:
+
+- `.tmp` by default
+- Configurable via `TWIN_EXTENSIONS_CACHE_DIRECTORY`
+
+Examples:
+
+- Default: `./.tmp/extensions/`
+- Custom: `./cache/extensions/` (if `TWIN_EXTENSIONS_CACHE_DIRECTORY="cache"`)
+- Absolute: `/var/cache/twin-node/extensions/` (if `TWIN_EXTENSIONS_CACHE_DIRECTORY="/var/cache/twin-node"`)
+
+### Security Best Practices
+
+1. **Prefer npm: protocol** over https: for third-party extensions (npm has package verification and malware scanning)
+2. **Use local files** (`./extension.mjs`) for maximum security and control
+3. **Verify HTTPS sources** before using - only load from domains you trust
+4. **Review extension code** before deployment, especially for HTTPS sources
+5. **Monitor cache directory** - review what's been downloaded to `.tmp/extensions/`
+6. **Use environment-specific configuration** - different extensions for dev/staging/prod
+
+### Troubleshooting
+
+#### Extension fails to load
+
+- Check that npm is installed and accessible in PATH (required for npm: protocol)
+- Verify the extension file/URL is accessible
+- Check `.tmp/extensions/` cache for partially downloaded files
+- Review node logs for specific error messages
+
+#### Clear extension cache manually
+
+```bash
+rm -rf .tmp/extensions
+```
+
+#### NPM package not found
+
+- Verify the package name is correct
+- Check network connectivity
+- Ensure npm registry is accessible

package/docs/deployment-docker.md

@@ -0,0 +1,189 @@
+# @twin.org/node - Deployment Docker
+
+## Docker Building
+
+To run the API server in the docker environment there is an example dockerfile in `deploy/dockerfile`:
+
+```shell
+# Set the base image
+FROM node:22
+
+# Create the app directory
+WORKDIR /app
+
+# Copy the package.json
+COPY package.json .
+
+# Install dependencies including dev dependencies needed for merge-locales
+RUN npm install --ignore-scripts
+
+# Copy the rest of the files to the image
+COPY . .
+
+# Compile translation messages
+RUN npm run merge-locales
+
+# Remove dev dependencies to reduce image size
+RUN npm prune --omit=dev
+
+# Expose the port the app runs on
+EXPOSE 3000
+
+# Set the environment variables that will override the .env file in the package
+ENV TWIN_HOST=0.0.0.0
+ENV TWIN_PORT=3000
+ENV TWIN_STORAGE_FILE_ROOT=/twin-node/data
+
+# Start the server
+CMD ["node", "src/index.mjs"]
+```
+
+You can build and execute this using docker from the root of the package with the following command.
+
+```shell
+docker build -t twin-node -f deploy/dockerfile . --load
+```
+
+> **Note**: The `--load` flag is required when using Docker Buildx to ensure the image is loaded into your local Docker registry. Without it, the image will only exist in the build cache.
+
+This will build and deploy an image called `twin-node` to your local docker server.
+
+## Bootstrapping
+
+Whenever the server starts it bootstraps all the components. If you have any entity storage configured to use `file` storage you should map a directory on the local host to contain the data, so that it remains persistent.
+
+```shell
+docker run -t -i -v /home/twin-node/data:/twin-node/data -p 3000:3000 twin-node
+```
+
+This example will map the local directory `/home/twin-node/data` and make it available in the docker container as `/twin-node/data` which is used to configure file entity storage using the environment variable `TWIN_STORAGE_FILE_ROOT`.
+
+The output from the docker container should be something like the following.
+
+```shell
+🌩️  TWIN Node Server v1.0.0
+
+Execution Directory: /app
+Locales Directory: /app/dist/locales
+Locales File: /app/dist/locales/en.json
+OpenAPI Spec File: /app/docs/open-api/spec.json
+Favicon File: /app/static/favicon.ico
+Environment Variable Prefix: TWIN_
+Default Environment File: /app/.env
+
+INFO [2025-10-03T01:23:42.634Z] EngineCore Engine is starting
+INFO [2025-10-03T01:23:42.635Z] EngineCore Debugging is enabled
+INFO [2025-10-03T01:23:42.636Z] EngineCore Loading state from file storage with filename "twin-node/data/engine-state.json"
+INFO [2025-10-03T01:23:42.637Z] EngineCore Configuring loggingConnector: console
+INFO [2025-10-03T01:23:42.637Z] EngineCore Configuring loggingConnector: entity-storage
+INFO [2025-10-03T01:23:42.638Z] EngineCore Configuring Entity Storage with name "log-entry" using "file" connector
+INFO [2025-10-03T01:23:42.638Z] EngineCore Configuring loggingConnector: multi
+INFO [2025-10-03T01:23:42.638Z] EngineCore Configuring loggingComponent: service
+...
+INFO [2025-10-03T01:23:42.655Z] EngineCore Bootstrap started
+...
+INFO [2025-10-03T01:23:42.662Z] EngineCore Generating mnemonic "weird focus prevent jewel enemy reveal supply dove then swallow topple goose case over endless garage width panic learn ask close fault immune shadow"
+INFO [2025-10-03T01:23:42.662Z] EngineCore Storing mnemonic
+INFO [2025-10-03T01:23:43.912Z] EngineCore Funding wallet "https://explorer.iota.org/address/0x69d531810657960fa07d346cb9bb7003e016e38c0b7486607002a10990ea0dd9?network=testnet"
+INFO [2025-10-03T01:23:46.547Z] EngineCore Generating node identity
+INFO [2025-10-03T01:23:49.584Z] EngineCore Node identity created "did:iota:testnet:0xc7aa88cd54c8c90fc1cbe5927b3e2fe33d478ca7b6b058020c0d87e8f88fac82"
+INFO [2025-10-03T01:23:49.585Z] EngineCore Identity explorer "https://explorer.iota.org/object/0xc7aa88cd54c8c90fc1cbe5927b3e2fe33d478ca7b6b058020c0d87e8f88fac82?network=testnet"
+INFO [2025-10-03T01:23:49.595Z] EngineCore Node identity "did:iota:testnet:0xc7aa88cd54c8c90fc1cbe5927b3e2fe33d478ca7b6b058020c0d87e8f88fac82"
+INFO [2025-10-03T01:23:49.596Z] EngineCore Creating node user "admin@node"
+INFO [2025-10-03T01:23:49.597Z] EngineCore Node Admin User Email "admin@node"
+INFO [2025-10-03T01:23:49.597Z] EngineCore Node Admin User Password "ayc^YC31TF%BVshQ"
+INFO [2025-10-03T01:23:49.600Z] EngineCore Creating user profile "did:iota:testnet:0xc7aa88cd54c8c90fc1cbe5927b3e2fe33d478ca7b6b058020c0d87e8f88fac82"
+INFO [2025-10-03T01:23:49.601Z] EngineCore Creating authentication key "did:iota:testnet:0xc7aa88cd54c8c90fc1cbe5927b3e2fe33d478ca7b6b058020c0d87e8f88fac82/auth-signing"
+INFO [2025-10-03T01:23:49.617Z] EngineCore Creating blob encryption key "did:iota:testnet:0xc7aa88cd54c8c90fc1cbe5927b3e2fe33d478ca7b6b058020c0d87e8f88fac82/blob-encryption"
+INFO [2025-10-03T01:23:49.624Z] EngineCore Created blob encryption key "did:iota:testnet:0xc7aa88cd54c8c90fc1cbe5927b3e2fe33d478ca7b6b058020c0d87e8f88fac82/blob-encryption" with value "4+S7bupEk/vLVhGxjKJ3jWw3uKo+3JsF8wYoB5B59bc="
+INFO [2025-10-03T01:23:50.314Z] EngineCore Adding attestation verification method "did:iota:testnet:0xc7aa88cd54c8c90fc1cbe5927b3e2fe33d478ca7b6b058020c0d87e8f88fac82#attestation-assertion"
+INFO [2025-10-03T01:23:56.408Z] EngineCore Adding immutable proof verification method "did:iota:testnet:0xc7aa88cd54c8c90fc1cbe5927b3e2fe33d478ca7b6b058020c0d87e8f88fac82#immutable-proof-assertion"
+INFO [2025-10-03T01:24:01.772Z] EngineCore Bootstrap complete
+INFO [2025-10-03T01:24:01.773Z] EngineCore Components are starting
+...
+INFO [2025-10-03T01:24:02.476Z] EngineCore Components have started
+INFO [2025-10-03T01:24:02.476Z] EngineCore Engine has started
+INFO [2025-10-03T01:24:02.477Z] EngineCore Saving state to file storage with filename "twin-node/data/engine-state.json"
+INFO [2025-10-03T01:24:02.496Z] FastifyWebServer Building Web Server
+...
+INFO [2025-10-03T01:24:03.111Z] FastifyWebServer Starting Web Server at address "0.0.0.0" on port "3000"
+INFO [2025-10-03T01:24:03.128Z] FastifyWebServer The Web Server started on http://0.0.0.0:3000
+```
+
+You will see it generated a node admin user with password for future use, these should be recorded as they will not be made visible again.
+
+To run the bootstrap again you would have to manually remove the `engine-state.json` from the data directory.
+
+## Docker Running
+
+To run the server we use exactly the same command as before, when the `engine-state.json` exists the component states are passed in to the components.
+
+```shell
+docker run -t -i -v /home/twin-node/data:/twin-node/data -p 3000:3000 twin-node
+```
+
+You should now see output similar to the following:
+
+```shell
+🌩️  TWIN Node Server v1.0.0
+
+Execution Directory: /app
+Locales Directory: /app/dist/locales
+Locales File: /app/dist/locales/en.json
+OpenAPI Spec File: /app/docs/open-api/spec.json
+Favicon File: /app/static/favicon.ico
+Environment Variable Prefix: TWIN_
+Default Environment File: /app/.env
+
+INFO [2025-10-03T01:23:42.634Z] EngineCore Engine is starting
+INFO [2025-10-03T01:23:42.635Z] EngineCore Debugging is enabled
+INFO [2025-10-03T01:23:42.636Z] EngineCore Loading state from file storage with filename "twin-node/data/engine-state.json"
+INFO [2025-10-03T01:23:42.637Z] EngineCore Configuring loggingConnector: console
+INFO [2025-10-03T01:23:42.637Z] EngineCore Configuring loggingConnector: entity-storage
+INFO [2025-10-03T01:23:42.638Z] EngineCore Configuring Entity Storage with name "log-entry" using "file" connector
+INFO [2025-10-03T01:23:42.638Z] EngineCore Configuring loggingConnector: multi
+INFO [2025-10-03T01:23:42.638Z] EngineCore Configuring loggingComponent: service
+...
+INFO [2025-10-03T01:23:42.655Z] EngineCore Bootstrap started
+...
+INFO [2025-10-03T01:27:34.331Z] EngineCore Wallet already funded
+INFO [2025-10-03T01:27:35.064Z] EngineCore Node identity already exists "did:iota:testnet:0xc7aa88cd54c8c90fc1cbe5927b3e2fe33d478ca7b6b058020c0d87e8f88fac82"
+INFO [2025-10-03T01:27:35.065Z] EngineCore Identity explorer "https://explorer.iota.org/object/0xc7aa88cd54c8c90fc1cbe5927b3e2fe33d478ca7b6b058020c0d87e8f88fac82?network=testnet"
+INFO [2025-10-03T01:27:35.065Z] EngineCore Node identity "did:iota:testnet:0xc7aa88cd54c8c90fc1cbe5927b3e2fe33d478ca7b6b058020c0d87e8f88fac82"
+INFO [2025-10-03T01:27:35.066Z] EngineCore Node user already exists "admin@node"
+INFO [2025-10-03T01:27:35.066Z] EngineCore User profile already exists "did:iota:testnet:0xc7aa88cd54c8c90fc1cbe5927b3e2fe33d478ca7b6b058020c0d87e8f88fac82"
+INFO [2025-10-03T01:27:35.067Z] EngineCore Authentication key already exists "did:iota:testnet:0xc7aa88cd54c8c90fc1cbe5927b3e2fe33d478ca7b6b058020c0d87e8f88fac82/auth-signing"
+INFO [2025-10-03T01:27:35.067Z] EngineCore Blob encryption key already exists "did:iota:testnet:0xc7aa88cd54c8c90fc1cbe5927b3e2fe33d478ca7b6b058020c0d87e8f88fac82/blob-encryption"
+INFO [2025-10-03T01:27:35.807Z] EngineCore Verification method for attestation already exists "did:iota:testnet:0xc7aa88cd54c8c90fc1cbe5927b3e2fe33d478ca7b6b058020c0d87e8f88fac82#attestation-assertion"
+INFO [2025-10-03T01:27:36.512Z] EngineCore Verification method for immutable proof already exists "did:iota:testnet:0xc7aa88cd54c8c90fc1cbe5927b3e2fe33d478ca7b6b058020c0d87e8f88fac82#immutable-proof-assertion"
+INFO [2025-10-03T01:27:36.512Z] EngineCore Bootstrap complete
+INFO [2025-10-03T01:24:01.773Z] EngineCore Components are starting
+...
+INFO [2025-10-03T01:24:02.476Z] EngineCore Components have started
+INFO [2025-10-03T01:24:02.476Z] EngineCore Engine has started
+INFO [2025-10-03T01:24:02.477Z] EngineCore Saving state to file storage with filename "twin-node/data/engine-state.json"
+INFO [2025-10-03T01:24:02.496Z] FastifyWebServer Building Web Server
+...
+INFO [2025-10-03T01:24:03.111Z] FastifyWebServer Starting Web Server at address "0.0.0.0" on port "3000"
+INFO [2025-10-03T01:24:03.128Z] FastifyWebServer The Web Server started on http://0.0.0.0:3000
+```
+
+You should now be able to access the server in the browser [http://localhost:3000/info](http://localhost:3000/info).
+
+On successfully communicating with the server you should see something similar to the following returned from the request:
+
+```json
+{
+  "name": "TWIN Node Server",
+  "version": "1.0.0"
+}
+```
+
+The logging in the docker container should also show the request and response.
+
+```shell
+INFO [2024-07-24T08:46:25.283Z] ===> GET /info
+INFO [2024-07-24T08:46:25.287Z] <=== 200 GET /info duration: 3987µs {"name":"TWIN Node Server","version":"1.0.0"}
+```
+
+The API server responds to the correct terminate signals so that when the docker container is stopped the server will also stop gracefully.

package/docs/deployment-ec2.md

@@ -0,0 +1,193 @@
+# @twin.org/node - Deployment Amazon AWS EC2
+
+## Amazon AWS EC2 Instance
+
+To run the server on an AWS EC2 instance follow the steps below:
+
+First follow one of the many online guides to create your EC2 instance with the ability to connect to it in terminal mode.
+
+Network requirements are for the `https` port to be open to any address range i.e. `0.0.0.0`.
+
+You should alias a domain name to the IP address of the instance e.g. `twin-node-api.example.com` using your DNS provider e.g. Cloudflare.
+
+## Install Git
+
+For retrieving the code from the repo.
+
+```shell
+sudo yum install git -y
+git -version
+```
+
+## Install NVM and Node
+
+For building and running the application.
+
+```shell
+curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash
+nvm install 20
+node -v
+```
+
+## Install nginx
+
+To serve the app through an https reverse proxy.
+
+```shell
+sudo yum install nginx -y
+nginx -v
+```
+
+## Configuring nginx
+
+We need to configure nginx to use the certificate and reverse proxy https traffic to the node server.
+
+```shell
+sudo nano /etc/nginx/nginx.conf
+```
+
+The configuration should be along the lines of:
+
+```shell
+server {
+    listen 80;
+    server_name twin-node-api.example.com;
+
+    # Redirect all traffic
+    return 301 https://$server_name$request_uri;
+}
+
+server {
+    listen [::]:443 ssl ipv6only=on;
+    listen 443 ssl;
+
+    server_name twin-node-api.example.com;
+
+    ssl_certificate /etc/ssl/certs/nginx-selfsigned.crt;
+    ssl_certificate_key /etc/ssl/private/nginx-selfsigned.key;
+
+    location / {
+        # Redirect the https traffic to the node instance
+        proxy_pass http://localhost:3000;
+        proxy_set_header Host $host;
+        proxy_set_header X-Real-IP $remote_addr;
+        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+        proxy_set_header X-Forwarded-Proto $scheme;
+    }
+
+    location /socket {
+        # Redirect the wss traffic to the node instance
+        proxy_pass http://localhost:3000;
+        proxy_set_header Host $host;
+        proxy_set_header Upgrade $http_upgrade;
+        proxy_set_header Connection "upgrade";
+    }
+}
+```
+
+Once configured you can restart nginx with `sudo systemctl restart nginx`
+
+Run `sudo systemctl enable nginx` to auto start the server on instance startup.
+
+## Building the server
+
+We clone the repo, build it and then make a copy of the relevant .env file.
+
+```shell
+git clone https://github.com/twinfoundation/node.git
+cd apps
+npm install
+npm run dist
+cd apps/node
+cp .env.example-entity-storage .env
+```
+
+The .env file can be modified to suit your own use case. For example to set the location for the storage.
+
+```shell
+TWIN_STORAGE_FILE_ROOT="/home/ec2-user/twin-node/"
+```
+
+## Bootstrapping the server
+
+You can now bootstrap the server, this will initialise all the required services and generate an initial configuration file. You should take note of the information in the logging as it will display information such as node admin passwords which will only be displayed once.
+
+```shell
+node ./dist/es/index.js
+```
+
+You should also now be able to access the server at `https://twin-node-api.example.com`
+
+## Configure the server to restart with server
+
+We now need to install the server as a service, so that after any reboot it will continue to run.
+
+Stop the server with `Ctrl-C`.
+
+Create a service file e.g. `twin-node.service`
+
+You might need to modify the location for the node version, you can find this out using `whereis node`
+
+```shell
+[Unit]
+Description=TWIN Node Server
+After=network.target
+
+[Service]
+ExecStart=/home/ec2-user/.nvm/versions/node/v20.16.0/bin/node /home/ec2-user/twin-node/apps/twin-node/dist/es/index.js
+Restart=always
+User=ec2-user
+Group=ec2-user
+Environment=PATH=/usr/bin:/usr/local/bin
+Environment=NODE_ENV=production
+WorkingDirectory=/home/ec2-user/twin-node/apps/twin-node/
+
+[Install]
+WantedBy=multi-user.target
+```
+
+Reload systemd and start the service.
+
+```shell
+sudo systemctl daemon-reload
+sudo systemctl enable ./twin-node.service
+sudo systemctl start twin-node.service
+```
+
+To check the status of the service.
+
+```shell
+sudo systemctl status twin-node.service
+```
+
+or
+
+```shell
+sudo journalctl -u twin-node | tail
+```
+
+## Upgrade EC2 Instance
+
+To upgrade a previous installation on an EC2 instance with the latest version.
+
+```shell
+sudo systemctl stop twin-node.service
+cd apps
+git reset --hard
+git pull
+npm i
+npm run dist
+cd apps/node
+
+# Update any env vars if necessary
+# nano .env
+
+# If you want to start from clean configuration you should remove the databases manually
+# and also remove the engine-state file
+# rm /home/ec2-user/twin-node/engine-state.json
+
+# To perform a test run before launching the service permanently
+# npm run start
+
+sudo systemctl start twin-node.service
+```

package/docs/deployment.md

@@ -0,0 +1,4 @@
+# @twin.org/node - Deployment
+
+- [Docker](./deployment-docker.md) - Guide to deploying with docker.
+- [Amazon AWS EC2](./deployment-ec2.md) - Guide to deploying with Amazon AWS EC2.