Google GCS Pickup

note

For information on how to configure Google GCS, refer to Google GCS Setup.

Below is an example of a FarEarth Pickup configuration, for Google's GCS.

{
    "id": "farearth.client-satname-1-pickup",
    "protocol": "google-gcs",
    "rootPath": "/pickup",
    "dataRetentionWindow": "12 hours",
    "shareable": true,
    "properties": {
        "bucketName": "MY_BUCKET",
        "credFileB64": "...",
        "enableMultiPartCopy": true,
        "multiPartCopyLimitInMB": 64,
        "pubSubSubscriptionName": "projects/fe-pickup/subscriptions/pubsub-trigger",
        "pubSubSuffix": "_product.json"
    }
}

The required properties for the Google GCS are listed below.

Field	Details
bucketName	Name of the bucket as it is configured on Google GCS
credFileB64	Base-64 encoded version of the JSON credentials file provided by Google
enableMultiPartCopy	Default: true. Enables or disables multi-part copying which improves performance for large files
pubSubSubscriptionName	Name of the PubSub subscription to use for triggers. Example, projects/<my-project-name>/subscriptions/<my-pubsub-subscription-name>
pubSubSuffix	Suffix of products to detect on PubSub Triggers. Default is "_product.json"

FarEarth uses a secure data transfer mechanism, where the access credentials, including the credFileB64, never leave the FarEarth server where it is configured (example, the Gateway). This means that even if other FarEarth components, running in other security realms, require access to the data in Google Drive cloud storage, it requests the access via the Gateway, using industry-standard secure communication. Data is retrieved via short-lived, access-constrained, and pre-signed URLs.