Deploy Features API to Production

[smohiudd]

Description

VEDA Features API has been refactored to use cdk instead of terraform and is included in this repo: https://github.com/NASA-IMPACT/veda-features-api-cdk. Features API is currently deployed in the UAH account as a staging environment. The main stakeholder/user of this service is the EIS Fire team who ingest daily data to the database. To support more stables services and include the deployment in veda-deploy, Features API must be deployed to MCP.

• deploy Features API to MCP production environment. There is currently a switch in veda deploy for Features API which is set to false.
• Create db with snapshot of veda-wfs3-west2-staging rds and use it to create the production features api
• Cutover VEDA dashboard to production features API and update external reference in production catalog for eis_fire_perimter dataset https://openveda.cloud/api/stac/collections/eis_fire_perimeter

Acceptance Criteria

• Features API is deployed to MCP using veda-deploy and is hosting EIS Fire data
• Production Features API is used in VEDA dashboard for eis_fire_perimeter dataset

[botanical]

I created a new release https://github.com/NASA-IMPACT/veda-features-api-cdk/releases/tag/v1.0.0 and also made some changes to include boostrap_qualifier for MCP.

The features API is hosted here: https://openveda.cloud/api/features/

[anayeaye]

Awesome, I see all of the collections from the current features api (https://firenrt.delta-backend.com/collections) are reachable via the mcp-prod features API so we have our DB user set up properly.

[botanical]

I need to fix the following pages on the landing page:

• Collection metadata
• Collection queryables
• Collection Features
• Collection Feature
• Collection Vector Tiles
• Collection TileSets
• Collection TileSet

[botanical]

Okay so those links on the landing page might not even be that important? @smohiudd , do you know if users will be accessing the API using the docs page? https://openveda.cloud/api/features/docs Everything's good from there.

[smohiudd]

@botanical looks those links weren't working on the old staging deployment (https://firenrt.delta-backend.com/) either so I think we should be ok. It's probably a bug to bring up with the tipg project.