Duo Network Gateway on the AWS Cloud

Quick Start Reference Deployment

QS

September 2020
Jacob Julian, Cisco Systems Inc.
Muffadal Quettawala and Shivansh Singh, Amazon Web Services

Visit our GitHub repository for source files and to post feedback, report bugs, or submit feature ideas for this Quick Start.

This Quick Start was created by Cisco Systems Inc. in collaboration with Amazon Web Services (AWS). Quick Starts are automated reference deployments that use AWS CloudFormation templates to deploy key technologies on AWS, following AWS best practices.

Overview

This Quick Start reference deployment guide provides architectural considerations and configuration steps for deploying a Duo Network Gateway cluster on the AWS Cloud in high-availability mode with scaling based on CPU load. The guide addresses common scalability, high-availability, and security requirements when adding Duo authentication to web applications and Secure Shell (SSH) connections on the AWS Cloud.

This guide is designed for mulitple audiences, including IT architects, network administrators, DevOps professionals, and Duo instance owners who are planning to implement or extend their Duo Network Gateway deployment on the AWS Cloud. It also provides links for viewing and launching AWS CloudFormation templates that automate the deployment.

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

Duo Network Gateway on AWS

This Quick Start deploys Duo Network Gateway on the AWS Cloud in high-availability mode with scaling in a matter of minutes.

With Duo Network Gateway, users can securely access internal web applications from any device, using any browser, from anywhere in the world, without having to install or configure remote access software on their device. Users can remotely connect (via SSH) to configured hosts through Duo Network Gateway after installing Duo’s connectivity tool, providing server access without a virtual private network (VPN).

For more details about the features and functionality of Duo Network Gateway, see the Duo Network Gateway documentation.

AWS costs

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

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

After you deploy the Quick Start, create AWS Cost and Usage Reports to deliver billing metrics to an Amazon Simple Storage Service (Amazon S3) bucket in your account. These reports 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?

Software licenses

This Quick Start requires a license for Duo Beyond. If you do not currently have a license for Duo Beyond, you can get a trial license at https://signup.duo.com/

The trial license of Duo Beyond gives you 30 days of free usage. After this time, you can upgrade to a production license by purchasing a subscription license of Duo Beyond.

Architecture

Deploying this Quick Start for a new VPC with default parameters builds the following Duo Network Gateway environment in the AWS Cloud.

Architecture
Figure 1. Quick Start architecture for Duo Network Gateway on AWS

As shown in figure 1, the Quick Start sets up the following:

  • A highly available architecture that spans two Availability Zones.*

  • A 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, managed network address translation (NAT) gateways to allow outbound internet access for resources in the private subnets.*

  • In the private subnets:

    • Duo Network Gateway portal servers for providing end users access to the product interface.

    • A Duo Network Gateway admin server for completing configuration tasks.

    • An Amazon ElastiCache for Redis instance with a Redis replication group for storing the configuration for Duo Network Gateway.

  • Elastic Load Balancing for accepting incoming traffic for the Duo Network Gateway admin server and then distributing that traffic to the Duo Network Gateway portal servers using an AWS Auto Scaling group.

  • An Amazon Route 53 public hosted zone to route traffic for the Duo Network Gateway domain and its subdomains.

  • SSL/TSL certificates in AWS Certificate Manager (ACM) for the Duo Network Gateway portal and admin server load balancers.

  • AWS Systems Manager to manage access to the Duo Network Gateway portal and admin servers.

  • (Optional) Amazon Simple Storage Service (Amazon S3) bucket for Duo Network Gateway portal server scripted deployment.

*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.

Planning the deployment

Specialized knowledge

This deployment requires a moderate level of familiarity with AWS services. If you’re new to AWS, see Getting Started Resource Center and AWS Training and Certification. These sites provide materials for learning how to design, deploy, and operate your infrastructure and applications on the AWS Cloud.

This Quick Start assumes familiarity with basic concepts of networking and Linux system administration, as well as basic knowledge of Duo Security.

AWS account

If you don’t already have an AWS account, create one at https://aws.amazon.com by following the on-screen instructions. Part of the sign-up process involves receiving a phone call and entering a PIN using the phone keypad.

Your AWS account is automatically signed up for all AWS services. You are charged only for the services you use.

Technical requirements

Before you launch the Quick Start, review the following information and ensure that your account is properly configured. Otherwise, deployment might fail.

Resource quotas

If necessary, request service quota increases for the following resources. You might request quota increases to avoid exceeding the default limits for any resources that are shared across multiple deployments. The Service Quotas console displays your usage and quotas for some aspects of some services. For more information, see What is Service Quotas? and AWS service quotas.

Resource This deployment uses

VPCs

1

Elastic IP addresses

2

AWS Identity and Access Management (IAM) security groups

5

IAM roles

2

Auto Scaling groups

1

Application Load Balancers

2

Route53 Public hosted zone

1

EC2 Instances

3 or more

NAT Gateways

2

Supported Regions

  • All AWS Regions

Certain Regions are available on an opt-in basis. For more information, see Managing AWS Regions.

EC2 key pairs

Make sure that at least one Amazon EC2 key pair exists in your AWS account in the Region where you plan to deploy the Quick Start. Make note of the key pair name. You need it during deployment. To create a key pair, see Amazon EC2 key pairs and Linux instances.

For testing or proof-of-concept purposes, we recommend creating a new key pair instead of using one that’s already being used by a production instance.

IAM permissions

Before launching the Quick Start, you must sign in to the AWS Management Console with IAM permissions for the resources that the templates deploy. The AdministratorAccess managed policy within IAM provides sufficient permissions, although your organization may choose to use a custom policy with more restrictions. For more information, see AWS managed policies for job functions.

This Quickstart assumes that the user has:

  1. A registered domain name e.g. mycompany.com that is registered externally or via AWS Route53.

  2. A public hosted zone created in AWS Route53. In order to route internet traffic for a domain, AWS Route53 requires a public hosted zone to be created as a secondary step for either an external or AWS Route53 registered domain name.

Once the public hosted zone is created, the Quickstart provides 2 deployment parameter options to the user:

Option1:

The user specifies the public hosted zone ID and subdomain names for the Duo Network Gateway admin and portal server load balancers as input parameters to the Quickstart template. With this option, the Quickstart subsequently generates tls certificates (in AWS ACM) and then creates resource records for the load balancer in the public hosted zone.

Option 2:

The user leaves the public hosted zone ID and subdomain parameters blank, but instead specifies the ARN(s) of certificates (either created by or imported in ACM) as input parameters to the Quickstart template. In this option, the Quickstart assumes that the user will manually provision the certificates and the resource record sets in the public hosted zone. The certificate ARN is used by the Quickstart when creating the load balancer listeners.

Deployment options

This Quick Start provides two deployment options:

  • Deploy Duo Network Gateway into a new VPC (end-to-end deployment). This option builds a new AWS environment consisting of the VPC, subnets, NAT gateways, security groups, bastion hosts, and other infrastructure components. It then deploys Duo Network Gateway into this new VPC.

  • Deploy Duo Network Gateway into an existing VPC. This option provisions Duo Network Gateway in your existing AWS infrastructure.

The Quick Start provides separate templates for these options. It also lets you configure Classless Inter-Domain Routing (CIDR) blocks, instance types, and Duo Network Gateway settings, as discussed later in this guide.

As an additional deployment option, you can upload a scripted configuration file for Duo Network Gateway at the time of deployment. This file must be generated according to Duo documentation. Once created, the file must be uploaded to an Amazon S3 bucket and specified during deployment using the 'ConfigYAMLPath' parameter. Typically, the scripted configuration option is used in automated workflows and command-line or programmatic methods of deploying this Quick Start. This supported scripted configuration is different than the scripted backup and restore feature, which is also supported by Duo Network Gateway.

Deployment steps

Sign in to your AWS account

  1. Sign in to your AWS account at https://aws.amazon.com with an AWS Identity and Access Management (IAM) user role that has the necessary permissions. For details, see Planning the deployment earlier in this guide.

  2. Make sure that your AWS account is configured correctly, as discussed in the Technical requirements section.

Launch the Quick Start

You are responsible for the cost of the AWS services used while running this Quick Start reference deployment. There is no additional cost for using this Quick Start. For full details, see the pricing pages for each AWS service used by this Quick Start. Prices are subject to change.
  1. Sign in to your AWS account, and choose one of the following options to launch the AWS CloudFormation template. For help with choosing an option, see deployment options earlier in this guide.

Deploy Duo Network Gateway into a new VPC on AWS

Deploy Duo Network Gateway into an existing VPC on AWS

If you’re deploying Duo Network Gateway into an existing VPC, make sure that your VPC has two private subnets in different Availability Zones for the workload instances, and that the subnets aren’t shared. This Quick Start doesn’t support shared subnets. These subnets require NAT gateways in their route tables to allow the instances to download packages and software without exposing them to the internet.

Also, make sure that the domain name option in the DHCP options is configured according to the Amazon VPC documentation. You will provide your VPC settings when you launch the Quick Start.

Each deployment takes about 15 minutes to complete.

  1. Check the AWS Region that’s displayed in the upper-right corner of the navigation bar, and change it if necessary. This Region is where the network infrastructure for Duo Network Gateway is built. The template is launched in the us-east-1 Region by default.

  1. On the Create stack page, keep the default setting for the template URL, and then choose Next.

  2. On the Specify stack details page, change the stack name if needed. Review the parameters for the template. Provide values for the parameters that require input. For all other parameters, review the default settings and customize them as necessary.

+ In the following tables, parameters are listed by category and described separately for the deployment options. When you finish reviewing and customizing the parameters, choose Next.

+ NOTE: Unless you are customizing the Quick Start templates for your own deployment projects, keep the default settings for the parameters Quick Start S3 bucket name, Quick Start S3 bucket Region, and Quick Start S3 key prefix. Changing these settings automatically updates code references to point to a new Quick Start location. For more information, see the AWS Quick Start Contributor’s Guide.

+ === Launch into a new VPC .VPC network configuration

Parameter label (name) Default value Description

Availability Zones (AvailabilityZones)

Requires input

List of Availability Zones to use for the subnets in the VPC. Only two Availability Zones are used for this deployment, and the logical order of your selections is preserved.

VPC CIDR (VPCCIDR)

10.0.0.0/16

CIDR block for the VPC.

Public subnet 1 CIDR for application load balancer (PublicSubnet1CIDR)

10.0.128.0/20

CIDR block for the public (DMZ) subnet 1 located in Availability Zone 1.

Public subnet 2 CIDR for application load balancer (PublicSubnet2CIDR)

10.0.144.0/20

CIDR block for the public (DMZ) subnet 2 located in Availability Zone 2.

Private subnet 1 CIDR for Duo Network Gateway servers (PrivateSubnet1CIDR)

10.0.0.0/19

CIDR block for private subnet 1 located in Availability Zone 1.

Private subnet 2 CIDR for Duo Network Gateway servers (PrivateSubnet2CIDR)

10.0.32.0/19

CIDR block for private subnet 2 located in Availability Zone 2.

Table 1. Duo Network Gateway configuration
Parameter label (name) Default value Description

ARN of the load balancer’s SSL certificate (ACMSSLCertificateArn)

Blank string

Amazon Resource Name (ARN) of the load balancer’s SSL certificate. If you don’t provide values for DomainName and HostedZoneID, provide a value for ACMSSLCertificateArn.

Admin server EC2 instance type (AdminServerInstanceType)

t3.medium

Admin server EC2 instance type

Allowed CIDR block for external access to the load balancer (AdminServerRemoteAccessCIDR)

Requires input

The allowed CIDR block for remote access to the Duo Network Gateway admin server. Always restrict traffic on the admin server’s port 8443 to authorized network ranges only and not widely to the internet.

Subdomain for the admin server (AdminServerSubdomain)

Blank string

Sub-domain for the admin server. Fully qualified domain name for the admin server will be created by adding the DomainName parameter value as a suffix. For example, if the provided value is 'adminserver' and the DomainName parameter value is 'corp.com', then the fully qualified domain name for the admin server will be 'adminserver.corp.com'

Auth token for the Redis cluster (AuthToken)

DuoRedisAuthToken

The auth token for the Redis cluster.

S3 bucket path of the Duo Network Gateway config file (ConfigYAMLPath)

Blank string

(Optional) S3 bucket path of the scripted configuration YAML file. (e.g. https://duoconfigbucket.s3.amazonaws.com/scripts/config/dng_config.yml)

Fully qualified domain name for the Duo Network Gateway load balancer (DomainName)

Blank string

Fully qualified domain name for the Duo Network Gateway load balancer. If you don’t provide a value for ACMSSLCertificateArn, use the HostedZoneID. If you provide a value for this parameter, you must also provide a corresponding HostedZoneID.

Route 53-hosted zone ID of the domain name (HostedZoneID)

Blank string

Route 53-hosted zone ID of the domain name. If you don’t provide an ACMSSLCertificateArn value, the Quick Start creates the ACM certificate for you using HostedZoneID in conjunction with DomainName. This HostedZoneID should be for the corresponding DomainName parameter value.

Name of an existing EC2 key pair (KeyPairName)

Requires input

NO_DESCRIPTION

Number of replicas per shard (NumReplicas)

1

Number of replicas per shard in the Redis replication group.

Number of shards in the cluster (NumShards)

1

Number of shards in the cluster.

Portal server EC2 instance type (PortalServerInstanceType)

t3.medium

Portal server EC2 instance type

The value used for the name tag of the portal server (PortalServerName)

PortalServer

The value used for the name tag of the portal server

Allowed CIDR block for external access to the load balancer (PortalServerRemoteAccessCIDR)

Requires input

Allowed CIDR block for external access to the load balancer

Subdomain for the portal server (PortalServerSubdomain)

Blank string

Subdomain for the portal server. Fully qualified domain name for the portal server will be created by adding the DomainName parameter value as suffix. For example, if the provided value is 'portalserver' and the DomainName parameter value is 'corp.com', then the fully qualified domain name for the portal server will be 'portalserver.corp.com'

Type of Redis cache node (RedisCacheNodeType)

cache.t3.medium

Choose a value for the type of Redis Cache node.

Redis replication group version (RedisEngineVersion)

3.2.6

Redis replication group version.

(Optional) Redis snapshot name (SnapshotName)

Blank string

(Optional) Name of a snapshot from which you want to restore (leave blank to create an empty cache).

Redis snapshot retention limit (SnapshotRetentionLimit)

35

The number of days that Amazon ElastiCache retains automatic Redis snapshots before deleting them (set to 0 to disable backups).

Table 2. AWS Quick Start configuration
Parameter label (name) Default value Description

Quick Start S3 bucket name (QSS3BucketName)

aws-quickstart

S3 bucket name for the Quick Start assets. Quick Start bucket name can include numbers, lowercase letters, uppercase letters, and hyphens (-). It cannot start or end with a hyphen (-).

Quick Start S3 bucket Region (QSS3BucketRegion)

us-east-1

The AWS Region where the Quick Start S3 bucket (QSS3BucketName) is hosted. When using your own bucket, you must specify this value.

Quick Start S3 key prefix (QSS3KeyPrefix)

quickstart-cisco-duo-network-gateway/

S3 key prefix for the Quick Start assets. Quick Start key prefix can include numbers, lowercase letters, uppercase letters, hyphens (-), and forward slash (/).

Launch into an existing VPC

Table 3. VPC Network configuration
Parameter label (name) Default value Description

VPC CIDR (VPCCIDR)

10.0.0.0/16

CIDR block for the VPC.

ID of the VPC (VPCID)

Requires input

ID of the VPC (e.g., vpc-0343606e).

Public subnet 1 ID for application load balancer (PublicSubnet1ID)

Requires input

ID of the public subnet 1 that you want to provision the load balancers of admin and portal servers into (e.g., subnet-a0246dcd).

Public subnet 2 ID for application load balancer (PublicSubnet2ID)

Requires input

ID of the public subnet 1 that you want to provision the load balancers of admin and portal servers into (e.g., subnet-a0246dcd).

Private subnet 1 ID for Duo Network Gateway servers (PrivateSubnet1ID)

Requires input

ID of the private subnet 1 that you want to provision the admin and portal servers into (e.g., subnet-a0246dcd).

Private subnet 2 ID for Duo Network Gateway servers (PrivateSubnet2ID)

Requires input

ID of the private subnet 2 that you want to provision the admin and portal servers into (e.g., subnet-a0234dcs).

Table 4. Duo Network Gateway configuration
Parameter label (name) Default value Description

ARN of the load balancer’s SSL certificate (ACMSSLCertificateArn)

Blank string

Amazon Resource Name (ARN) of the load balancer’s SSL certificate. If you don’t provide values for DomainName and HostedZoneID, provide a value for ACMSSLCertificateArn.

Admin server EC2 instance type (AdminServerInstanceType)

t3.medium

Admin server EC2 instance type.

Allowed CIDR block for external access to the load balancer (AdminServerRemoteAccessCIDR)

Requires input

The allowed CIDR block for remote access to the Duo Network Gateway admin server. Always restrict traffic on the admin server’s port 8443 to authorized network ranges only, not widely to the internet.

Subdomain for the admin server (AdminServerSubdomain)

Blank string

Subdomain for the admin server. Fully qualified domain name for the admin server will be created by adding the DomainName parameter value as a suffix. For example, if the provided value is 'adminserver' and the DomainName parameter value is 'corp.com', then the fully qualified domain name for the admin server will be 'adminserver.corp.com'.

Auth token for the Redis cluster (AuthToken)

DuoRedisAuthToken

The auth token for the Redis cluster.

S3 bucket path of the Duo Network Gateway config file (ConfigYAMLPath)

Requires input

(Optional) S3 bucket path of the scripted configuration YAML file. (e.g. https://duoconfigbucket.s3.amazonaws.com/scripts/config/dng_config.yml).

Fully qualified domain name for the Duo Network Gateway load balancer (DomainName)

Blank string

Fully qualified domain name for the Duo Network Gateway load balancer. If you don’t provide a value for ACMSSLCertificateArn, use the HostedZoneID. If you provide a value for this, you must also provide a corresponding HostedZoneID.

Route 53-hosted zone ID of the domain name (HostedZoneID)

Blank string

Route 53-hosted zone ID of the domain name. If you don’t provide an ACMSSLCertificateArn value, the Quick Start creates the ACM certificate for you using HostedZoneID in conjunction with DomainName. This HostedZoneID should be for the corresponding DomainName parameter value.

Name of an existing EC2 key pair (KeyPairName)

Requires input

NO_DESCRIPTION

Number of replicas per shard in Redis replication group (NumReplicas)

1

Number of replicas per shard.

Number of shards in the cluster (NumShards)

1

Number of shards in the cluster.

Portal server EC2 instance type (PortalServerInstanceType)

t3.medium

Portal server EC2 instance type.

Name tag of portal server (PortalServerName)

PortalServer

The value used for the name tag of the portal server.

Allowed CIDR block for external access to load balancer (PortalServerRemoteAccessCIDR)

Requires input

Allowed CIDR block for external access to the load balancer.

Subdomain for portal server (PortalServerSubdomain)

Blank string

Subdomain for the portal server. Fully qualified domain name for the portal server will be created by adding the DomainName parameter value as a suffix. For example, if the provided value is 'portalserver' and the DomainName parameter value is 'corp.com', then the fully qualified domain name for the portal server will be 'portalserver.corp.com'.

Type of Redis cache node (RedisCacheNodeType)

cache.t3.medium

Choose a value for the type of Redis Cache node.

Redis replication group version (RedisEngineVersion)

3.2.6

Redis replication group version.

(Optional) Redis snapshot name (SnapshotName)

Blank string

(Optional) Name of a snapshot from which you want to restore (leave blank to create an empty cache).

Redis snapshot retention limit (SnapshotRetentionLimit)

35

Number of days that Amazon ElastiCache retains automatic Redis snapshots before deleting them (set to 0 to disable backups).

Table 5. AWS Quick Start configuration
Parameter label (name) Default value Description

Quick Start S3 bucket name (QSS3BucketName)

aws-quickstart

S3 bucket name for the Quick Start assets. Quick Start bucket name can include numbers, lowercase letters, uppercase letters, and hyphens (-). It cannot start or end with a hyphen (-).

Quick Start S3 bucket Region (QSS3BucketRegion)

us-east-1

The AWS Region where the Quick Start S3 bucket (QSS3BucketName) is hosted. When using your own bucket, you must specify this value.

Quick Start S3 key prefix (QSS3KeyPrefix)

quickstart-cisco-duo-network-gateway/

S3 key prefix for the Quick Start assets. Quick Start key prefix can include numbers, lowercase letters, uppercase letters, hyphens (-), and forward slash (/).

+ . On the Configure stack options page, you can specify tags (key-value pairs) for resources in your stack and set advanced options. When you’re finished, choose Next. . On the Review page, review and confirm the template settings. Under Capabilities, select the two check boxes to acknowledge that the template creates IAM resources and might require the ability to automatically expand macros. . Choose Create stack to deploy the stack. . Monitor the status of the stack. When the status is CREATE_COMPLETE, the Duo Network Gateway deployment is ready. . Use the values displayed in the Outputs tab for the stack, as shown in Figure 2, to view the created resources.

cfn_outputs
Figure 2. Duo Network Gateway outputs after successful deployment

Post deployment steps

After the Quick Start has been successfully created, you can interact with Duo Network Gateway from a web browser. Perform the following steps:

  1. In a browser, navigate to https://<URL-of-the-network-gateway-load-balancer>:8443 from a network in the 'AdminServerRemoteAccessCIDR' subnet, and log in to the Duo Network Gateway admin console. Your browser warns you about an untrusted certificate the first time you access the page. Dismiss the warning and continue to the page.

  2. On the first page of the Duo Network Gateway configuration screen, choose a password for the Duo Network Gateway admin console. After entering a password that meets the requirements, choose Save and Continue.

set_dng_password
  1. On the Make Duo Network Gateway visible to the internet page, either fill in the fields, as shown in the following image, or choose the Already have a Duo Network Gateway configuration file? Import it now link to import a configuration file.

dng_config

Note the following recommendations when filling in the fields:

  • As this Quick Start uses load balancers that present SSL security to end users, you can use a certificate for the connection between the load balance and Duo Network Gateway. There are two options for providing this certificate:

    • If you want to provide your own SSL certificate for Duo Network Gateway, choose Change Certificate and select Provide my own certificate.

    • If you want to use self-signed certificates for the Duo Network Gateway server, choose the Present a self-signed certificate to incoming connections option.

  • After selecting the This Duo Network Gateway is accessed through load balancers check box, specify the internal IP addresses of your Duo Network Gateway portal server load balancer, which you can locate in the Outputs section of the Quick Start. This setting makes the Duo Network Gateway aware of the load balancer IP addresses, which allows the source client IP addresses to log information, apply allowed IP restrictions, and pass IP addresses to protected applications.

  • Be sure to provide complete and accurate information on this page to avoid errors with the initial configuration. If an error occurs, you will need to re-enter the information again before proceeding, including selecting the certificate and key.

  • When you choose Save and Continue, you are redirected to the Duo Network Gateway admin console, where you can add a SAML authentication source and configure Duo Network Gateway to proxy the applications for adding Duo policies.

welcome

For additional information, access the Duo documentation.

Security

The Quick Start exposes two user-configurable security group access parameters: 'AdminServerRemoteAccessCIDR' and 'PortalServerRemoteAccessCIDR'. Be sure that the 'AdminServerRemoteAccessCIDR' parameter 'is accessible only on authorized network ranges for both ports 22 and 8443, not widely accessible on the internet.

FAQ

Q. How do I output Duo Network Gateway docker logs to a file?

A. To export the logs, connect via SSH to the Duo Network Gateway server and run the following command. You may need to replace the example Duo Network Gateway YML name with the name of your current file:

docker-compose -p network-gateway -f network-gateway-1.5.5.yml logs > Dng.log

After running the command, a Dng.log file is exported outside of your docker container. After exporting your logs, you can cancel the log by pressing Ctrl + C.

Q. Can I create web applications for Duo Network Gateway in bulk?

A. Yes. You can use a configuration file to create web applications in bulk, store your settings locally in source control, automatically deploy the applications, and make changes to Duo Network Gateway without having to access the admin console.

Q. How do I determine the current version number of Duo Network Gateway?

A. To determine the current version number of Duo Network Gateway, log in to the Duo Network Gateway admin console and check the footer:

faq_answer

Q. How do I interpret and troubleshoot Duo Network Gateway issues?

A. For a list of common error messages with descriptions and resolutions, see the official Duo Security Knowledge Base.

Q. I encountered a CREATE_FAILED error when I launched the Quick Start. What should I do?

A. If AWS CloudFormation fails to create the stack, relaunch the template with the Rollback on failure option set to No. (This setting is under Advanced in the AWS CloudFormation console on the Options page.) With this setting, the stack’s state is retained, and the instance is left running, so you can troubleshoot the issue. (For Windows, look at the log files in %ProgramFiles%\Amazon\EC2ConfigService and C:\cfn\log.)

When you set Rollback on failure to Disabled, you continue to incur AWS charges for this stack. Be sure to delete the stack when you finish troubleshooting.

For additional information, see Troubleshooting AWS CloudFormation on the AWS website.

Q. I encountered a size limitation error when I deployed the AWS CloudFormation templates.

A. Launch the Quick Start templates from the links in this guide or from another Amazon S3 bucket. If you deploy the templates from a local copy on your computer or from a location other than an S3 bucket, you might encounter template size limitations. For more information about AWS CloudFormation quotas, see AWS CloudFormation quotas.

Send us feedback

To post feedback, submit feature ideas, or report bugs, use the Issues section of the GitHub repository for this Quick Start. To submit code, see the Quick Start Contributor’s Guide.

Quick Start reference deployments

GitHub repository

Visit our GitHub repository to download the templates and scripts for this Quick Start, to post your comments, and to share your customizations with others.


Notices

This document is provided for informational purposes only. It represents AWS’s current product offerings and practices as of the date of issue of this document, which are subject to change without notice. Customers are responsible for making their own independent assessment of the information in this document and any use of AWS’s products or services, each of which is provided “as is” without warranty of any kind, whether expressed or implied. This document does not create any warranties, representations, contractual commitments, conditions, or assurances from AWS, its affiliates, suppliers, or licensors. The responsibilities and liabilities of AWS to its customers are controlled by AWS agreements, and this document is not part of, nor does it modify, any agreement between AWS and its customers.

The software included with this paper is licensed under the Apache License, version 2.0 (the "License"). You may not use this file except in compliance with the License. A copy of the License is located at http://aws.amazon.com/apache2.0/ or in the accompanying "license" file. This code is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either expressed or implied. See the License for specific language governing permissions and limitations.