app-orchestrator v1.0.0

App Orchestrator

This project manages the resources related to the app orchestrator. This project doesn't belong to the frontend-infrastructure stack because it needs to deployed in a specific region. See here more Lambda@Edge restrictions.

Dependencies

JoSe (Joust Serverless) package

Used to deploy the application using AWS cross-account roles, follow Joust's naming conventions, etc.

Configure this project

1. Firstly, create a .env file in the root of this project:

touch .env

2. In the .env file, specify the following variables:

# .env
STACK_NAME=app-orchestrator
PROJECT_NAME=app-orchestrator
AWS_ACCOUNT={AWS_ACCOUNT} # eg. 67********80
ENVIRONMENT={ENVIRONMENT} # eg. Dev
AWS_REGION=us-east-1 # Needs to be us-east-1 because of lambda@edge

3. Extract and configure the Cloudformation params needed by this stack by running:

jose extract-template-variables

4. This will generate a .template.env file in the root of this project. Open that file and replace the {...} to set the params with the appropriate values:

# .template.env
CERTIFICATE_ARN={certificate-arn} # Find it in 1Password or manually generate one for your environment, if needed
CLOUDFRONT_OAI={CloudFrontOriginAccessIdentity} # fetch value from frontend-infrastructure stack outputs

5. Confirm the buckets created by the frontend-infrastructure stack match the app orchestrator. A future improvement for this step would be to have variables or exploring StackSets.

Please note that the values provided above may have changed since these instructions were written so use them as a guide only.

Deploying the Cloudformation Stack

Once the steps above are completed, run the following make command to deploy the stack with Cloudformation:

make deploy

Make sure to follow the instructions in JoSe and configure your aws-cli with the correct AWS credentials.