Skip to content

S3 deliveries

Jump to bottom
Jiří Tomíček edited this page Feb 23, 2024 · 12 revisions
  • The S3 delivery must be registered using the API-endpoint 'register-delivery-s3' (see API Endpoints). There, the S3 credentials and S3 key prefix of the requested delivery need to be specified. The S3 key prefix should be as specific as possible and must uniquely identify a single delivery on the S3 repository.
  • The type of delivery is displayed in the overview of deliveries on the main page, in the 'type' column (see picture below).
  • Next, it is possible to work with the delivery in the same way (via UI or the same API-endpoints) as with the local (i.e. ZIP archive) delivery.
  • When running a QC job, the 'unzip' module is replaced by the 's3_download' module, which creates a local temporary copy of the delivery files. At the end of the job, the local copy of the data is deleted.
  • When submitting S3 delivery to the EEA, only reports (JSON and PDF) and supportive files are submitted.

Clone this wiki locally
⚡