aws-quickstart · andrew-glenn · Dec 12, 2022
diff --git a/docs/deployment_guide/partner_editable/architecture.adoc b/docs/deployment_guide/partner_editable/architecture.adoc
@@ -1,12 +1,12 @@
-Deploying this Quick Start for a new virtual private cloud (VPC) with
+Deploying this Partner Solution for a new virtual private cloud (VPC) with
 default parameters builds the following {partner-product-short-name} environment in the AWS Cloud.
 
 :xrefstyle: short
 [#architecture1]
-.Quick Start architecture for {partner-product-short-name} on AWS
+.Partner Solution architecture for {partner-product-short-name} on AWS
 image::../docs/deployment_guide/images/architecture_diagram.png[Architecture]
 
-As shown in <<architecture1>>, this Quick Start sets up the following:
+As shown in <<architecture1>>, this Partner Solution sets up the following:
 
 * A highly available architecture that spans two Availability Zones.*
 * A VPC configured with public and private subnets, according to AWS
@@ -27,4 +27,4 @@ best practices, to provide you with your own virtual network on AWS.*
 ** After the Fargate containers stabilize, a CloudWatch event initiates a second Lambda function. This function updates the Duo MFA settings in AWS Systems Manager Parameter Store, which stores the latest Fargate container IP addresses. Specifically, this Lambda function finds the IP address of the Fargate task and updates the Systems Manager parameter `DuoServiceIps`.
 ** Finally, a CloudWatch event initiates a third Lambda function. This function either updates the RADIUS IP address in AWS Directory Service or, if the update fails, sends Duo administrators an SNS notification.
 
-[.small]#*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.#
+[.small]#*The template that deploys the Partner Solution into an existing VPC skips the components marked by asterisks and prompts you for your existing VPC configuration.#
diff --git a/docs/deployment_guide/partner_editable/deployment_options.adoc b/docs/deployment_guide/partner_editable/deployment_options.adoc
@@ -1,8 +1,8 @@
 // Edit this placeholder text as necessary to describe the deployment options.
 
-This Quick Start provides the following deployment options:
+This Partner Solution provides the following deployment options:
 
 * https://fwd.aws/nXE9E?[Deploy {partner-product-short-name} into a new VPC^]. This option builds a new AWS environment that consists of the VPC, subnets, NAT gateways, security groups, bastion hosts, and other infrastructure components. It then deploys {partner-product-short-name} into this new VPC.
 * https://fwd.aws/qAMMk?[Deploy {partner-product-short-name} into an existing VPC^]. This option provisions {partner-product-short-name} in your existing AWS infrastructure.
 
-This Quick Start provides separate templates for these options. It also lets you configure Classless Inter-Domain Routing (CIDR) blocks, instance types, and {partner-product-short-name} settings.
+This Partner Solution provides separate templates for these options. It also lets you configure Classless Inter-Domain Routing (CIDR) blocks, instance types, and {partner-product-short-name} settings.
diff --git a/docs/deployment_guide/partner_editable/licenses.adoc b/docs/deployment_guide/partner_editable/licenses.adoc
@@ -1,3 +1,3 @@
 // Include details about any licenses and how to sign up. Provide links as appropriate.
 
-There is no cost to use this Quick Start, but you will be billed for any AWS services or resources that this Quick Start deploys. For more information, refer to the https://fwd.aws/rA69w?[AWS Quick Start General Information Guide^]. Additionally, this Quick Start requires a license for Duo MFA. For more information, see https://duo.com/editions-and-pricing[Duo Editions & Pricing^].
+There is no cost to use this Partner Solution, but you will be billed for any AWS services or resources that this Partner Solution deploys. For more information, refer to the https://fwd.aws/rA69w?[AWS Partner Solution General Information Guide^]. Additionally, this Partner Solution requires a license for Duo MFA. For more information, see https://duo.com/editions-and-pricing[Duo Editions & Pricing^].
diff --git a/docs/deployment_guide/partner_editable/overview.adoc b/docs/deployment_guide/partner_editable/overview.adoc
@@ -1,4 +1,4 @@
-This Quick Start deploys {partner-product-name} to the AWS Cloud. If you are unfamiliar with AWS Quick Starts, refer to the https://fwd.aws/rA69w?[AWS Quick Start General Information Guide^].
+This Partner Solution deploys {partner-product-name} to the AWS Cloud. If you are unfamiliar with AWS Partner Solutions, refer to the https://fwd.aws/rA69w?[AWS Partner Solution General Information Guide^].
 
 === Security
 

diff --git a/docs/deployment_guide/partner_editable/post_deployment.adoc b/docs/deployment_guide/partner_editable/post_deployment.adoc
@@ -35,7 +35,7 @@ After you launch the stack, verify your deployment and, if desired, modify your
 
 === Modify your implementation
 
-If you want to increase or decrease the number of RADIUS tasks after deploying the Quick Start, update the AWS CloudFormation stack and specify the desired number of servers. Then perform a stack update. If you increase the number of tasks, the Amazon ECS service starts up that number of new tasks and installs and configures the Duo Authentication Proxy service for each. 
+If you want to increase or decrease the number of RADIUS tasks after deploying the Partner Solution, update the AWS CloudFormation stack and specify the desired number of servers. Then perform a stack update. If you increase the number of tasks, the Amazon ECS service starts up that number of new tasks and installs and configures the Duo Authentication Proxy service for each. 
 
 . Open the AWS CloudFormation console.
 

diff --git a/docs/deployment_guide/partner_editable/pre_deployment.adoc b/docs/deployment_guide/partner_editable/pre_deployment.adoc
@@ -11,10 +11,10 @@ You must set up at least one Duo user whose email address is associated with at
 * Accounts other than federal: https://admin.duosecurity.com/login[https://admin.duosecurity.com/login^] 
 * Federal accounts: https://admin.duofederal.com[https://admin.duofederal.com^]
 . Navigate to *Applications*.
-. Obtain the integration key, secret key, and API hostname. You will enter these three items as template parameter values when you deploy this Quick Start. 
+. Obtain the integration key, secret key, and API hostname. You will enter these three items as template parameter values when you deploy this Partner Solution. 
 * If directory synchronization is not required, do the following:
 .. Choose *Protect an Application*.
-.. In the applications list, locate the entry for *AWS Directory Services* by searching for *AWS Quick Start*. On the far right, choose *Protect*.
+.. In the applications list, locate the entry for *AWS Directory Services* by searching for *AWS Partner Solution*. On the far right, choose *Protect*.
 .. Configure the application, and get your integration key, secret key, and API hostname. Write down these three items. For details, see https://duo.com/docs/protecting-applications[Protecting Applications^]. 
 * If directory synchronization is required, do the following:
 .. Set up directory synchronization by following the steps in https://duo.com/docs/adsync[Synchronizing Users from Active Directory^].

diff --git a/docs/deployment_guide/partner_editable/troubleshooting.adoc b/docs/deployment_guide/partner_editable/troubleshooting.adoc
@@ -1,11 +1,11 @@
 // Add any unique troubleshooting steps here.
 
-For troubleshooting common Quick Start issues, refer to the https://fwd.aws/rA69w?[AWS Quick Start General Information Guide^] and https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/troubleshooting.html[Troubleshooting CloudFormation^].
+For troubleshooting common Partner Solution issues, refer to the https://fwd.aws/rA69w?[AWS Partner Solution General Information Guide^] and https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/troubleshooting.html[Troubleshooting CloudFormation^].
 
 If your Directory Service's MFA status is in a *Failed* status, check the following:
 
-. Ensure that the RADIUS ECS tasks have access to the internet. This Quick Start launches the RADIUS ECS tasks in the same subnet as the DNS servers in Directory Service. The subnet must have a route to the internet (typically through a NAT gateway) to install the Duo Authentication Proxy and other required tools used to configure Directory Service.
-. Ensure that the security group associated with the Directory Service DNS servers have a rule that allows output traffic on port 1812 to the security group created by this Quick Start.
+. Ensure that the RADIUS ECS tasks have access to the internet. This Partner Solution launches the RADIUS ECS tasks in the same subnet as the DNS servers in Directory Service. The subnet must have a route to the internet (typically through a NAT gateway) to install the Duo Authentication Proxy and other required tools used to configure Directory Service.
+. Ensure that the security group associated with the Directory Service DNS servers have a rule that allows output traffic on port 1812 to the security group created by this Partner Solution.
 .. To find the security group associated with your DNS servers, open the Directory Service console, and note the IP addresses under *DNS address*.
 .. Open the EC2 console, and choose *Network Interfaces* link from the menu.
 .. In the search field, enter one of the DNS IP addresses you found in the previous step.