Valid email address: You will receive a temporary password used to access your instance.
Amazon EC2 Public Key (InstanceKey). You must create or upload a key pair to your AWS account. https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-key-pairs.html
ARNCertificate: You must create or import an ssl certificate to the AWS Certificate Manager service. This requires a registered domain name you can access.
How to create a certificate: https://docs.aws.amazon.com/acm/latest/userguide/gs-acm-request-public.html
How to import an existing certificate: https://docs.aws.amazon.com/acm/latest/userguide/import-certificate.html
Access to a full archive node running a blockchain with an EVM client. The node will be connected during installation using the EthereumJsonRPC parameters. BlockScout currently supports Geth, Parity, RSK and Ganache.
If you leave the
CognitoCallbackDomain parameter blank during installation and want to use your own domain later, you will need to route traffic to the LoadBalancer and change the Cognito App client settings.
A) Re-route your DNS
Example instruction to route traffic using Route 53: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-elb-load-balancer.html
B) Configure Cognito settings
Change the callback URL(s) in client settings. https://docs.aws.amazon.com/cognito/latest/developerguide/cognito-user-pools-app-settings.html
Most parameters can be left as default during installation. For a full list of variables see the ENV variables list.
The following parameters require a user-input value.
SSL certificate from point 3 above. More information on certificates is available here: https://docs.aws.amazon.com/acm/latest/userguide/acm-overview.html
Add the domain(s) where you will access BlockScout and append “/oauth2/idpresponse" to the end. If you do not have a domain, leave this field blank. It will be populated with the LoadBalancerDNS created at the end of the process.
Enter any valid email. You will receive a temporary password here after deployment.
Add a secure password here for database access. Record this password for later access.
This is the node url used to fetch blocks, transactions, receipts & tokens. See the instructions on setting up a node on AWS for more information. If setup through AWS, you can find the address in EC2 Dashboard -> Instances -> click to corresponding archive node instance.
You will retrieve the ip address and add the port number afterwards. The port for Parity is 8545.
Input the same value as above. This is used to fetch internal transactions and block traces.
The Network RPC endpoint in websocket mode. The default parity port is 8546.
Any transaction from the chain can be used. This hash provides a sample query in the GraphIQL Playground and always begins with “0x…”
IP address range for access to your LoadBalancer instance. Recommend using
From step 2 above. The instance key is located at EC2 Dashboard -> Network & Security -> Key Pairs. It should be available as a dropdown.
Secret key for production assets protection in base64. You can generate this on the command line of your local machine using the following command: "openssl rand -base64 16"