This document outlines the steps involved in deploying the orchestrator, which is built with Webpack.

Prerequisites:

• A basic understanding of Webpack and its build process.
• Access to the frontend project repository.
• Access to the AWS Masiv Platform and Oasis accounts.
• Familiarity with AWS interface and resource management.

1. Getting started

• Clone the repo at masivapp-orchestrator - Repos (visualstudio.com)

• Install dependencies

  npm install
  

2. Build the project

• Use the build script from the package.json package.json file depending on the desired environment (labs, test or prod)

  # For labs
  npm run build:labs
  
  # For test
  npm run build:test
  
  # For prod
  npm run build:prod
  

3. Update the CSP policy (⚠️ Required)

Open the Generated index_csp.html:

• Locate the generated index_csp.html file in your project's build directory and open it in a browser.

Generate Hashes:

• Inspect the browser's developer console or network tab to identify the hashes generated for the static resources (e.g., scripts, stylesheets, images).

  • It may look like this:

  

• Collect these hashes and note them down. (e.g. ‘sha256-hJbVqSaMjbweHWEBD8PtyXgtuSlasFH5vTUyQxRhlK0=’)

Update the hashes:

CSP hashes are different depending on the deployment environment. While the CSP policy in labs is **report-only,** let’s just focus on prod environment.

⚠️ It’s important to update the policy in both resources because Cloudfront function handles white label frontend and lambda edge handles frontend.masivapp.com access.

It’s mandatory to update the CSP policy in the following resources. Here’s the step by step:

1. Update CSP in Cloudfront function

• Log in to the Masiv_plataform_Prod AWS account.
• Locate the oasis-add-csp-headers Cloudfront function
• Modify the value of the content-security-policy header to include the generated hashes for the relevant resources.