# Create a Deployment
This section will step you through deploying an Airnode using a configuration that was built when creating an integration. An integration can be used for multiple deployments if desired. Deployments can be made on ASW or GCP.
There are a few things needed before creating a deployment:
- Acquire cloud provider account such as AWS or GCP.
- Acquire a blockchain provider account for the networks required.
- Install Docker.
Select the Deploy menu in the navigation bar on the left side of the page.
Then select the New Deployment button. ChainAPI will step-you-through the
# New Deployment
The deployment will use an integration you have already created to define and deploy an Airnode to a cloud provider of your choice.
Name the deployment. You won’t able to change this after saving the deployment.
# Cloud Provider Settings
Select the desired cloud provider and the region the Airnode should be deployed to. Additionally, decide which Airnode version to use.
# Add APIs and Networks
Here you will define the integration to use and which networks (chains) the Airnode will respond to.
Select the desire integration.
Select the desired network (chain) that the Airnode will respond to.
# No. of provider
How many blockchain providers does the integration use.
# Review Configuration
Review the deployment configuration before continuing. Go back to make changes.
# Download and Deploy
Here you will download the required deployment files to perform final editing of the required secrets.
# Download files
These files are needed to deploy your Airnode. Inside the zip file, you will find a README, a file based on your cloud provider selection, config folder, and output folder.
# Edit Files
Use the instruction in the README and comments in the other files to add secrets
config.json file will read.
# Use Docker container to deploy your Airnode
Copy and paste the commands below to your terminal at the directory with your config.json and secrets.env files.
Complete one deployment at a time. Starting multiple, simultaneous deployments will fail and need to be removed manually through your cloud provider’s web interface.
# Check deployment status
Once your deployment is completed, its status will change to either Active or Timed Out. If your deployment is Active, that means that we have received the Airnode heartbeat and your Airnode is active. If it’s Timed Out, something went wrong and you should start by checking the Deployment Checklist below, and check docker for any errors during deployment.
# Finish Deployment
Click on the Finish Deployment button after you have completed the deployment. This will take you to your list of deployments and display their statuses.