reference deployment

Chainlink Node on AWS

Provide external data to smart contracts on any blockchain

This Quick Start deploys highly available Chainlink nodes with default parameters and a blockchain to the Amazon Web Services (AWS) Cloud. It is for enterprise users who want to run a secure Chainlink node to provide external resources such as external APIs, tamper-proof price data, and verifiable randomness directly to smart contracts stored on the blockchain. 

A Chainlink node connects smart contracts with external data using a decentralized oracle network. Chainlink nodes, which can be run as Docker containers, can act as an oracle data provider to any local or private Ethereum network or testnets, including Rinkeby, Kovan, and Mainnet.

Chainlink logo

This Quick Start was developed by Chainlink Labs in collaboration with AWS. Chainlink Labs is an AWS Partner. 

  •  What you'll build
  • The Quick Start sets up the following:

    • A highly available architecture that spans two Availability Zones.*
    • A virtual private network (VPC) configured with public and private subnets, according to AWS best practices, to provide you with your own virtual network on AWS.*
    • In the public subnets:
      • An internet gateway to allow access to the internet.*
      • Managed network address translation (NAT) gateways to allow outbound internet access for the Chainlink node instances in the private subnets.*
      • A Linux bastion host in an Auto Scaling group to allow inbound Secure Shell (SSH) access to Amazon Elastic Compute Cloud (Amazon EC2) instances in public and private subnets.
    • In the private subnets:
      • Two Chainlink nodes in an Auto Scaling group that contains security groups for fine-grained inbound access control.
      • An Amazon Relational Database Service (Amazon RDS) PostgreSQL managed database instance.
    • An Elastic Load Balancing (ELB) load balancer to access the Chainlink node user interface.
    • Amazon CloudWatch logging of Chainlink nodes.
    • AWS Key Management Service (AWS KMS) resources with both AWS managed and customer managed keys.
    • AWS Secrets Manager to store credentials.
    • Amazon DevOps Guru tracking of your Chainlink node stack.

    *  The template that deploys the Quick Start into an existing VPC skips the components marked by asterisks and prompts you for your existing VPC configuration.

  •  How to deploy
  • To deploy your Chainlink node, follow the instructions in the deployment guide. A standard deployment takes about 45 minutes and includes these steps:

    1. Sign in to your AWS account. If you don't have an account, sign up for one at
    2. Launch the Quick Start. Before you create the stack, choose the AWS Region from the top toolbar. You can choose from two options:
    3. Perform post-deployment tasks. 

    Amazon may share user-deployment information with the AWS Partner that collaborated with AWS on the Quick Start.  

  •  Cost and licenses
  • You are responsible for the cost of the AWS services and any third-party licenses used while running this Quick Start reference deployment. There is no additional cost for using the Quick Start. 

    The AWS CloudFormation templates for this Quick Start include configuration parameters that you can customize. Some of the settings, such as the instance type, affect the cost of the deployment. For cost estimates, see the pricing page for each AWS service you use. Prices are subject to change.

    Tip: After you deploy the Quick Start, create AWS Cost and Usage Reports to track costs associated with the Quick Start. These reports deliver billing metrics to an Amazon Simple Storage Service (Amazon S3) bucket in your account. They provide cost estimates based on usage throughout each month and aggregate the data at the end of the month. For more information, see What are AWS Cost and Usage Reports?