TCN Server on AWS

This repo contains server and infrastructure code for deploying and running CoEpi Cloud API on AWS.

• Compute: AWS Lambda
• Data Store: DynamoDB
• Routing and Load Balancing: API Gateway
• Permissions Management: IAM

Getting Started

Requirements:

• JDK11 or newer

Infrastructure Setup

All infrastructure concerns are managed by Terraform (v0.12+). You can either download Terraform from their site, or install it with Choco (Windows), brew (macOS), or your Linux distribution's package manager.

Terraform tracks the state of your infrastructure in a tfstate file, which can be stored either locally or remotely. While we recommend remote state, both options are documented here for convenience.

Option 1: Remote Terraform State (Recommended)

First, create an S3 bucket to store your Terraform remote state. This will need to be uniquely named, and should be private and encrypted. A script has been provided to do this for you:

TFSTATE_BUCKET=your_bucket_name_here ./scripts/terraform_setup.sh

(If you're not sure what to name your bucket, try something like <your github username>-tcn-infra.)

With your bucket created, go to ./terraform in the project root directory. Copy backend.local.example to backend.local. Edit the contents to update the bucket property to match the bucket name you created above. E.g.,

bucket = "s3-bucket-with-your-terraform-state"

(The backend.local file is specific to your development environment and is ignored by source control using .gitignore.)

Finally, initialize your Terraform project:

terraform init -backend-config=backend.local

Option 2: Local Terraform State

In a terminal, navigate to ./terraform and run the following to initialize your Terraform state:

terraform init

Build

./gradlew build

Then build the shadow jar for the Lambda:

./gradlew api-aws-lambda:shadowJar

Deploy

These steps assume you have already initialized Terraform as described in "Infrastructure Setup" above.

1. Ensure you have the AWS CLI configured, working, and pointing to the default AWS account you wish to deploy to.
2. Ensure you've run the "Build" step above
3. cd to the terraform folder in this repo
4. Run terraform plan to see what changes will be applied to your AWS account
5. Run terraform apply -auto-approve to make the changes and deploy the server.
6. When the Terraform scripts are updated or you wish to redeploy, repeat steps 7 and 8.

The API Gateway root URL will be echoed to the shell, and you can CURL the deployed API:

v4

curl -X POST https://e6f2c4llfk.execute-api.us-west-1.amazonaws.com/v4/tcnreport -d "ZXlKMFpYTjBJam9pWW05a2VTSjk="
curl -X GET https://e6f2c4llfk.execute-api.us-west-1.amazonaws.com/v4/tcnreport

Running

For running the server on your developer AWS account, follow the steps below under AWS Insfrastructure Setup section.

For testing the lambda function and API locally, you can use SAM CLI. Below docs should be helpful.

https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-cli-install.html

https://docs.aws.amazon.com/serverless-application-model/latest/developerguide/serverless-sam-cli-using-invoke.html

Documentation for API Endpoints

Swagger Definition and API documentation is located under api_definition folder:

The API can be tested by pasting the definition on Swagger Editor

v4

Method	HTTP request	Description
tcnreportPost	POST /tcnreport	Submit symptom or infection report following TCN 0.4.0 protocol
tcnreportGet	GET /tcnreport?date={report_date}?intervalNumber={interval}?intervalLengthMs={interval_length_ms}	Returns a list of reports generated on the specified date and interval