Phase 1 - Definition of Done

Scope boundaries

  • Creates minimal infrastructure required to deploy Lambda Identify service -- this includes CF, S3, API GW and all the required Lambdas
  • Only includes infrastructure deployment, no apps/specs this time
  • No Studio integration (uses scripts to deploy/manage infrastructure)
  • Configuration uses static files available to the deployment scripts 
  • Full observability via CloudWatch
  • Full data offload integration
  • Stretch goal: Sudio UI to manage users. May be a hack to connect existing Identify UI

 Decisions

  • Uses GitLab-hosted NPM registry to host and distribute packages.
  • A space is represented by an NPM app, including required packages via package.json
  • One of the NPM packages is a tool that allows deployment of the infrastructure defined by other packages.
  • Configuration is stored in a JSON file that has to be available at the time of running the tool. TBC whether this file is checked into the repo or not.
This article was updated on