Overview

Airnode is deployed with the following files:

config.json: specifies the API–Airnode integrations and various node and deployment parameters.
secrets.env: holds secrets used by Airnode such as the Airnode mnemonic, API keys, blockchain provider URLs, and more.
aws.env: (AWS deployments only) holds AWS credentials and is required by the Docker deployer image.
gcp.json: (GCP deployments only) holds GCP project information and is required by the Docker deployer image. This file is downloaded from a GCP project. See the guide Deploying an Airnode on GCP for more information.

Airnode deployments utilize secrets such as security scheme values (i.e., API keys) and blockchain provider URLs. These secrets are injected into config.json from secrets.env using standard shell variable interpolation syntax (e.g. ${VARIABLE}). This way secrets are stored separately but are available as part of the configuration during the Airnode runtime.

The config.json file does NOT reference values in aws.env as aws.env is read directly by the deployer image.

The deployer image outputs a receipt.json file after deployment, which contains information about the deployment that can be referred to later on for interaction or removal.

FLEX_END_TAG

Overview ​

Overview