Prerequisites
However you choose to deploy Anvil Enterprise, there are few things you’ll need to set up first.
Domain Names
Anvil requires two domain names to operate:
- A primary domain (
anvil.example.com). This is where your developers will access the Anvil development environment. - A wildcard app domain (
*.apps.example.com). This is where your Anvil Apps will be deployed — each app gets its own subdomain.
We also recommend provisioning a third domain to use for metrics and monitoring (metrics.anvil.example.com).
Once you’ve chosen your domain names, make sure you are able to configure DNS records to point them to your deployment environment. If you’re deploying to AWS, then Anvil can automatically handle DNS and TLS configuration for you.
For trial purposes, it is possible to configure Anvil Enterprise to run from a single hostname. Do not do this in production as it removes the security barriers between applications and the Anvil editor.
TLS Certificates
You have a choice of using an Anvil-supplied service to perform HTTPS termination, or using your own infrastructure (e.g. an HTTP load balancer). See the TLS Certificates page for more details.
If you’re deploying to AWS, then Anvil can automatically handle DNS and TLS configuration for you.
SMTP Credentials
Anvil requires the ability to send email. You’ll need credentials for an SMTP service — if you need an external provider, we recommend Sendgrid or AWS SES.
Licence Key and Registry Credentials
In order to run Anvil Enterprise, you will need a licence key and credentials for the Anvil Registry in order to pull the necessary container images. These will be shared with you by a member of the Anvil team during the installation process.
SSO Credentials (Optional)
Anvil includes native integrations for a number of external services. Each of these features is optional, but if you want to use them with Anvil Enterprise you will need to obtain credentials:
Do you still have questions?
Our Community Forum is full of helpful information and Anvil experts.