Skip to content

Exploitation Deployment⚓︎


A deployment wrapper script has been prepared for an ‘exploitation’ deployment - that provides deployment/execution of processing via the ADES, supported by Resource Catalogue and Data Access services.

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

The exploitation 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:
    • ADES for processing
    • Resource Catalogue for data discovery
    • Data Access for data visualisation and download
    • Minio for S3 object storage
  • ADES stage-out to Minio
  • 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
    Note that it may be necessary to set the variable CREODIAS_EODATA_S3_ENDPOINT if different from the default - for example the value for the WAW3-2 Cloudferro cloud.
  • Open ingress are enabled for unauthenticated access to ADES, resource-catalogue and data-access services
  • Other eoepca services not deployed

Initiate Deployment⚓︎

Deployment is initiated by invoking the script…


The ADES service is accessed at the endpoint

The Resource Catalogue is accessed at the endpoint

The Data Access View Server is accessed at the endpoint

Post-deploy Manual Steps⚓︎

To complete the deployment, see section Post-deployment Manual Steps of the Scripted Deployment page.

Example Requests - s-expression on CREODIAS⚓︎

NOTE that this example processing request requires harvesting data from CREODIAS, which can only be performed if the deployment is made to a CREODIAS VM with access to the eodata network - see description of variable CREODIAS_DATA_SPECIFICATION.

Section Processing provides an example of a simple self-contained processing deployment and execution, and access to the processing results.

In addition to the snuggs example, the file deploy/samples/requests/processing/s-expression.http has been prepared to exploit data that has been registered within the Resource Catalogue and Data Access services.

First the input data for processing must be harvested into the resource management services.
Sentinel-2 data on 2nd Sept 2020…

./deploy/bin/harvest ./deploy/samples/harvester/config-Sentinel2-2020.09.02.yaml

Then the s-expression.http file provides sample requests for OGC API Processes operations:

  • List Processes
  • Deploy Process
  • Get Process Details
  • Execute Process
  • Get Job Status
  • Get Job Results

NOTE that the first requests in the file provide optional calls to obtain a user access token (openidConfiguration / authenticate) - to be used in the case that protected (not ‘open’) endpoints are deployed.

The files snuggs.http and s-expression.http describe the HTTP requests for the ADES OGC API Processes endpoint, and is designed for use with the Visual Studio Code (vscode) extension REST Client. Install in vscode with ext install

Various variables, such as to specify the @domain for your deployment, can be configured at the top of the file.

At the completion of successful processing execution, the procesing results are obtained as described in section Processing Results.

Data Harvesting⚓︎

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