Full Featured in-browser TAK Client

&

Facilitate ETL operations to bring non-TAK data sources into a TAK Server

Testing locally can be done either running the server directly (recommended for development) or by running the provided Docker Compose services

If running on Ubuntu this will install the necessary dependencies

./cloudtak.sh install

Create a new Env Var file

cp .env.example .env

Start CloudTAK Locally

./cloudtak.sh start

Once the database and API service have built, the server will start on port 5000. In your webbrowser visit http://localhost:5000 to view the ETL UI

Installation outside of the docker environment is also fairly straightforward. In the ./api, perform the following

npm install
echo "CREATE DATABASE tak_ps_etl" | psql
cd web/
npm install
npm run build
cd ..
npm run dev

Almost all values with the exception of the initial Postgres Connection string are stored in the database and can be changed via the Administrative Interface in the Web UI.

Alternatively, values can be configured by setting Environment Variables on launch. Note that if this is done, environment variables present at launch they will OVERRIDE any values that might be present in the database

Any of the listed config keys present in the POST /config API can all be set via Env Vars at startup.

To do so, follow the following formatting rules:

• Append CLOUDTAK_Config_
• Replace any instance of :: with _
• All characters after CLOUDTAK_Config_ are case SENSITIVE

For example:

• media::url would map to: CLOUDTAK_Config_media_url
• group::Brown would map to: CLOUDTAK_Config_group_Brown

If using the provided CloudFormation templates, these values will be populated for you and you shoudl ignore this section. All defaults in CloudTAK assume you are deploying via the provided CloudFormation templates.

The following values can be overridden through the use environment variables.

|

The ETL service assumes several pre-requisite dependencies are deployed before initial ETL deployment. The following are dependencies which need to be created:

An AWS ACM certificate must also be generated that covers the subdomain that CloudTAK is deployed to as well as the second level wildcard. Where in the example below CloudTAK is deployed to ie: map.example.com The second level wildcard will be used for serving tiles, currently configured to be tiles.map.example.com

IE:

*.example.com
*.map.example.com

coe-ecr-etl

Can be created using the dfpc-coe/ecr repository.

From the ecr repo:

npm install
npx deploy create etl

coe-ecr-etl-tasks

Can be created using the dfpc-coe/ecr repository.

From the ecr repo:

npm install
npx deploy create etl-tasks

From the root directory, install the deploy dependencies

npm install

An script to build docker images and publish them to your ECR is provided and can be run using:

npm run build

from the root of the project. Ensure that you have created the necessary ECR repositories as descrived in the previos step and that you have AWS credentials provided in your current terminal environment as an aws ecr get-login-password call will be issued.

From the root directory, install the deploy dependencies

npm install

Deployment to AWS is handled via AWS Cloudformation. The template can be found in the ./cloudformation directory. The deployment itself is performed by Deploy which was installed in the previous step.

The deploy tool can be run via the following

npx deploy

To install it globally - view the deploy README

Deploy uses your existing AWS credentials. Ensure that your ~/.aws/credentials has an entry like:

[coe]
aws_access_key_id = <redacted>
aws_secret_access_key = <redacted>

Then deploy the webhooks sub-stack with:

npx deploy create <stack> --template cloudformation/webhooks.template.js

This will create the API Gateway resources necessary for accepting incoming ETL Data Events as well as internal data processing webhooks.

Deployment of the main stack can then be performed via the following:

npx deploy create <stack>
npx deploy update <stack>
npx deploy info <stack> --outputs
npx deploy info <stack> --parameters

Stacks can be created, deleted, cancelled, etc all via the deploy tool. For further information information about deploy functionality run the following for help.

npx deploy

Further help about a specific command can be obtained via something like:

npx deploy info --help