Skip to content

Data Access Deployment⚓︎

A deployment wrapper script has been prepared for a ‘data access’ deployment - that is focused on the Resource Catalogue and Data Access services.

The script deploy/data-access/data-access achieves this by appropriate configuration of the environment variables, before launching the eoepca.sh deployment script. The deployment configuration is captured in the file deploy/data-access/data-access-options.

The data-access deployment applies the following configuration:

  • Assumes a private deployment - i.e. no external-facing IP/ingress, and hence no TLS
    To configure an external-facing deployment with TLS protection, then see section Public Deployment
  • No TLS for service ingress endpoints
  • Services deployed:
    • Resource Catalogue for data discovery
    • Data Access for data visualisation and download
  • Includes data specification for CREODIAS Sentinel-2, which can be exploited if running in a CREODIAS VM connected to the eodata network - see description of variable CREODIAS_DATA_SPECIFICATION
  • Open ingress are enabled for unauthenticated access to resource-catalogue and data-access services
  • Other eoepca services not deployed

Initiate Deployment⚓︎

Deployment is initiated by invoking the script…

./deploy/data-access/data-access

The Resource Catalogue is accessed at the endpoint resource-catalogue-open.<domain> - e.g. resource-catalogue-open.192.168.49.2.nip.io.

The Data Access View Server is accessed at the endpoint data-access-open.<domain> - e.g. data-access-open.192.168.49.2.nip.io.

Data Harvesting⚓︎

See section Harvest CREODIAS Data to harvest the default data specification from the CREODIAS data offering.