Before you begin, you will need a Deepgram Account Representative. To reach one, contact us!

Your Deepgram Account Representative will guide you through the process of setting up:

Ahead of your planned on-prem deployment, your Deepgram Account Representative will need:

  • your Deepgram Console account email address
  • your Deepgram Console Project ID

Providing this information will allow Deepgram to supply:

  • download links to your customized configuration files, which will include your license ID
  • download links to required models, including at least one pre-trained AI model for testing purposes

Deploying Deepgram on AWS requires some preparation. In this section, you will learn how to expose and access your application in a secure and stable manner. You will need to perform some of these steps in the AWS Management Console and some in your local terminal.

Accessing Your Cloud Environment

AWS uses public-key cryptography to secure login information for your instance. A Linux instance has no password; you use a key pair to log in to your instance securely. For the following steps, be sure to use a non-root AWS account.

Create an Amazon EC2 Key Pair

If you don’t already have an Amazon EC2 key pair, you will need to create one in order to access the AWS EC2 Virtual Machine. To learn how, read Create a key pair using Amazon EC2 in Amazon’s documentation.

At the end of this process, your browser should download a private-key.pem file for your key pair. Move this file to a secure and memorable location.

Create an Amazon EC2 Instance

​To begin your on-prem installation, you must create an Amazon EC2 instance.

  1. Navigate to the EC2 Dashboard and confirm that the proper AWS Region is configured, then choose Launch Instance to open the wizard.

  2. For the Choose an Amazon Machine Image (AMI) wizard step, choose a basic configuration to serve as a template for your instance:


    Recommended AMIs

    Deepgram recommends the following Linux AMIs for use on AWS:

    • Ubuntu Server 20.04 LTS (HVM), SSD Volume Type
    • Red Hat Enterprise Linux (RHEL) 7 (HVM) ami-078a6a18fb73909b2
    • Red Hat Enterprise Linux 8 ami-08970fb2e5767e3b8
    • Search for Ubuntu Server 20.04 LTS (HVM), SSD Volume Type.
    • Ensure the 64-bit (x86) option is selected.
    • Choose Select.
  3. For the Choose an Instance Type wizard step, select the hardware configuration of your instance:

    • Filter by the g4dn family type.
    • Select the g4dn.2xlarge instance.
    • Select Next: Configure Instance Details.


Avoid selecting Review and Launch. If you do so, the wizard will complete the other configuration settings for you and will miss some important settings.

  1. For the Configure Instance Details wizard step, review the default instance detail selections, then select Next: Add Storage.
  2. For the Add Storage wizard step, increase the size of the Root volume to 32 GB, and then select Next: Add Tags.
  3. For the Add Tags wizard step, select “Add Tag”:
    • For the key, type Name.
    • For the value, type On-Premises.
    • Select Next: Configure Security Group.
  4. For the Configure Security Group wizard step, select Create a new security group.
    • For the name, type On-Premises.
    • For the description, type On-Premises Security Group.
    • Ensure the first rule (of type SSH) is listed, and provide the description SSH for Administration.
    • Select Add Rule, then select HTTPS from the dropdown, and provide the description HTTPS for Deepgram API.
    • Select Review and Launch.
  5. For the Review Instance Launch wizard step, ensure all of the instance details match what you entered in the previous steps, and then select Launch.
  6. In the Select an existing key pair or create a new key pair modal, ensure that choose an existing key pair is selected, then choose the key pair you created in the Create an Amazon EC2 Key Pair section. Check the acknowledgement box, and select Launch Instances.
  7. Once the instance successfully launches, review its details in the EC2 instances list, and make note of its Public IPv4 DNS entry.

Log in to the AWS EC2 instance

To complete the rest of the installation, including configuring your environment and transferring files between your local computer and your AWS instance, you must connect to the AWS EC2 instance that you launched.

  1. Open the terminal application for your computer.

  2. Connect to your AWS instance:

    ssh -i private-key.pem [email protected]_HOSTNAME


Be sure to replace the AWS_HOSTNAME placeholder value with the hostname for your instance. Also check that the path to your private-key.pem file is correct.


For AWS Ubuntu instances, the default username is ubuntu, not user as their documentation would suggest.

  1. If you receive a message that indicates that the authenticity of the host can’t be established, type yes, then press the Enter key on your keyboard.

What’s Next

Depending on which Linux AMI you've selected, you'll want to follow the steps in one of these deployment guides.