Bring hosting stability to the remotesensingdata.gov.scot GEO server

[jonparsonsjncc]

Migration of the scot lidar geoserver and API onto the new AWS infrastructure.

Prerequisites

• jncc-srsp live and beta accounts already exist
• catalogue API docker container exists and doesn't need updating

Assumptions

• Can copy the existing data/config as is and update later if needed

Product breakdown structure

• New beta and live environments hosted within the new AWS environment
• An infrastructure diagram of the new system, generated automatically

Work breakdown structure
To be done in terraform (using emodnet as a template)

• Set up new geoserver + supporting services in the jncc-srsp accounts [3 days]
  • Can probably just use kartoza/geoserver container as no need to store db credentials for scot lidar
  • Can probably get rid of the S3 IAM role as the data updates will be done by devs
• Create a new RDS instance in jncc-shared-live [1 day]
• Set up a new database in the jncc-shared-live RDS instance (start with db.t3.small?) [1 day]
• Set up new catalogue API in the jncc-srsp accounts [3 days]
• Set up codepipeline/codebuild for catalogue API in the jncc-cicd account [2 days]
• Investigate progress on ImageMosaic S3 source work - Cathy talk to Matt

Manually?

• Populate data [4 days]
  • Copy geoserver raster data to S3
  • Copy geoserver config to EFS
  • Copy catalogue API data to RDS
  • Tilecache ???
• Update jenkins jobs for catalogue API deployment [2 days]
• Switchover of srsp-ows.jncc.gov.uk domain (live switchover to new geoserver)? [1 day]
  • Add redirect for old WMS?
• Move remotesensingdata.gov.scot to AWS
• Clean up/turn off old jncc-prod services [1 day]

Time code
P315