SIOS DataKeeper Cluster Edition on the AWS Cloud

Quick Start Reference Deployment

QS

August 2021
AWS Infrastructure & Automation team

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 SIOS Technology Corp. 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 step-by-step instructions for deploying SIOS DataKeeper Cluster Edition on the AWS Cloud. Quick Starts are automated reference deployments that use AWS CloudFormation templates to launch, configure, and run the AWS compute, network, storage, and other services required to deploy a specific workload on AWS.

This Quick Start is for enterprise users who want to deploy SIOS DataKeeper Cluster Edition on AWS into their test or production environment.

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

SIOS DataKeeper Cluster Edition on AWS

This Quick Start sets up an Amazon Web Services (AWS) architecture for SIOS DataKeeper Cluster Edition and deploys it into your AWS account.

SIOS DataKeeper Cluster Edition provides high availability cluster protection in a cloud environment. Fully integrated with Windows Server Failover Cluster (WSFC), it enables storage-agnostic clusters in WSFC environments where shared storage is impossible or impractical. SIOS DataKeeper extends WSFC with automatic failover of application instances across Availability Zones or Regions for disaster protection. This Quick Start uses AWS CloudFormation templates to deploy a two-node Microsoft SQL Server cluster with SIOS DataKeeper Cluster Edition across two Availability Zones. It also supports a data replication node outside the cluster with all nodes in the AWS Cloud.

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 uses Amazon Machine Images (AMIs) from the AWS Marketplace. It supports two licensing options:

  • Pay as you go (PAYG) — Use this consumption-based option to pay an hourly fee determined by usage. Current prices are listed on the AWS Marketplace page and billed to your AWS account. This option doesn’t require a license for SIOS DataKeeper.

  • Bring your own license (BYOL) — Use this option if you have a current license for SIOS DataKeeper Cluster Edition (which requires a run-time license for each server). You can deploy the Quick Start without first signing up for a license, but you must have a license to start and run SIOS DataKeeper Cluster Edition. You can contact SIOS to request a run-time license or a 14-day, free, trial license.

Architecture

Deploying this Quick Start for a new virtual private cloud (VPC) with default parameters builds the following DataKeeper environment in the AWS Cloud.

Architecture
Figure 1. Quick Start architecture for DataKeeper 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.*

    • Remote Desktop Gateway instances in an Amazon Elastic Compute Cloud (Amazon EC2) Auto Scaling group for remote administration.*

  • In the private subnets:

    • Two Active Directory domain controllers.

    • Two Microsoft SQL Server cluster nodes featuring SIOS DataKeeper replication software.

    • AWS Secrets Manager to store credentials.

    • An AWS Systems Manager runbook to automate the 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.

Technical specifications for the architecture:

Component Details

VPC

One AWS Region with two Availability Zones.

Instance type

Minimum recommended instance type: m3.xlarge.

Operating system

See DKCE Support Matrix.

Elastic IP

An Elastic IP address connected to the RD Gateway server.

Instances

Four instances: Two DNS / Active Directory domain controllers and two SIOS DataKeeper / SQL Server cluster nodes.

SQL Server

Elastic network interface (ENI) with three IPs for each SQL Server instance.

Volumes

Two volumes, Amazon Elastic Block Storage (Amazon EBS) and NTFS only: One primary volume (C drive) and one volume for replicated data storage.

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.

Before you deploy this Quick Start, we recommend that you become familiar with the following AWS services.

If you are new to AWS, see Getting Started with AWS. We also recommend that you review Deploying DataKeeper Cluster Edition in AWS Quick Start Guide.

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 need to request increases if your existing deployment currently uses these resources and if this Quick Start deployment could result in exceeding the default quotas. 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

1

Security groups

5

AWS Identity and Access Management (IAM) roles

2

Auto Scaling groups

1

Network Load Balancers

1

EC2 instances

Supported AWS Regions

For any Quick Start to work in a Region other than its default Region, all the services it deploys must be supported in that Region. You can launch a Quick Start in any Region and see if it works. If you get an error such as “Unrecognized resource type,” the Quick Start is not supported in that Region.

For an up-to-date list of AWS Regions and the AWS services they support, see AWS Regional Services.

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

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.

Deployment options

This Quick Start provides two deployment options:

  • Deploy DataKeeper into a new VPC. 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 DataKeeper into this new VPC.

  • Deploy DataKeeper into an existing VPC. This option provisions DataKeeper 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 DataKeeper settings, as discussed later in this guide.

Prepare your AWS account

  1. If you don’t already have an AWS account, create one at https://aws.amazon.com by following the on-screen instructions.

  2. Use the Region selector in the navigation bar to choose the AWS Region where you want to deploy SIOS DataKeeper Cluster Edition on AWS.

  3. Create a key pair in your preferred Region.

  4. If necessary, request a service limit increase for the Amazon EC2 r3.xlarge instance type. You might need to do this if you already have an existing deployment that uses this instance type, and you think you might exceed the default limit with this reference deployment.

Subscribe to the SIOS DataKeeper Cluster Edition AMI

This Quick Start uses Amazon Machine Images (AMIs) from the AWS Marketplace. Before you launch the Quick Start, you must subscribe to one of the SIOS DataKeeper Cluster Edition AMIs.

Two licensing options are available: Bring Your Own License (BYOL) and pay as you go (PAYG), as described previously in the Costs and Licenses section.

  1. If you’re planning to use the BYOL licensing option, obtain a permanent license by contacting SIOS directly. You can also sign up for a free, 14-day, trial license.

  2. Log in to the AWS Marketplace at https://aws.amazon.com/marketplace.

  3. Open the page for the licensing option you’d like to use:

  4. Choose Continue.

  5. Choose Manual Launch, and then choose Accept Software Terms. For more information about AWS Marketplace, see Getting started.

Deployment steps

Confirm your AWS account configuration

  1. Sign in to your AWS account at https://aws.amazon.com with an 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

If you’re deploying DataKeeper 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 as explained in DHCP options sets. You provide your VPC settings when you launch the Quick Start.

Each deployment takes about 45 minutes to complete.

  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 DataKeeper into a new VPC on AWS

    View template

    Deploy DataKeeper into an existing VPC on AWS

    View template

  2. 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 you build the network infrastructure. The template is launched in the us-east-1 Region by default. For other choices, see Supported Regions earlier in this guide.

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

  4. 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. For details on each parameter, see the Parameter reference section of this guide. When you finish reviewing and customizing the parameters, choose Next.

  5. On the Configure stack options page, you can specify tags (key-value pairs) for resources in your stack and set advanced options. When you finish, choose Next.

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

  7. Choose Create stack to deploy the stack.

  8. Monitor the status of the stack. When the status is CREATE_COMPLETE, the DataKeeper deployment is ready.

  9. To view the created resources, see the values displayed in the Outputs tab for the stack.

Test the deployment

The easiest way to determine whether SIOS DataKeeper Cluster Edition has been correctly deployed and configured is to launch Failover Cluster Manager on one of the replication nodes, and switch over resources.

  1. Connect to the Remote Desktop Gateway instance.

  2. From that node, connect to the replication node using Remote Desktop Protocol (RDP).

  3. Launch Failover Cluster Manager.

  4. In the left pane, choose Roles, and verify that the MSSQLSERVER role is online.

  5. In the Roles pane, open the context (right-click) menu for MSSQLSERVER, and then choose Move, Select Node, and the other replication node as the destination node. The role should come online within two minutes.

  6. Move the role back to the primary replication node. If the role comes online without any issues on either node, the deployment was successful and can be used as desired.

For more configuration details, see SIOS technical documentation.

Best practices for using DataKeeper on AWS

AWS services

SIOS recommends following AWS best practices for creating and using IAM roles and policies, IAM user credentials and roles, and access key rotation. For more information, see the following links.

SIOS DataKeeper Cluster Edition

SIOS also has some recommendations for customers seeking optimal performance. These recommendations include considerations specific to both the Windows operating system and the AWS Cloud configurations.

The primary component of SIOS DataKeeper is an upper filter volume driver. This driver tracks and processes every request sent to a source volume, and therefore incurs some overhead for all volume operations. When properly configured in a cloud environment, this overhead should be no more than 10-20 percent.

  • Instance size - Replication performance relies on several factors. While CPU usage is minimal, RAM utilization depends entirely on network performance, peak active workload, volume read/write latency, and the number of concurrent mirrors under load. With these considerations in mind, SIOS recommends using instance sizes that have at least medium network performance, enabling Amazon EBS optimization by default, and providing at least one instance for storage volume. The r3.xlarge instance size is the smallest recommended instance size if performance is a concern. If performance is not an issue, SIOS DataKeeper can be installed on any instance size that is currently available.

  • Amazon EBS optimization - This feature is required for best performance. It is turned on by default in the Quick Start deployment.

  • Instance storage - Several features of SIOS DataKeeper rely on very low latency volume access. Bitmap storage must be configured to reside on an instance storage volume. This is automatically configured during Quick Start deployment, but any nodes added to the cluster afterward will need manual configuration.

  • Volume properties - While a simple volume is all that is required for proper mirror operation, more advanced techniques can be used to minimize read/write latency. SIOS recommends creating identical Storage Pools to support mirror volumes on both source and target systems. This Quick Start does not configure Storage Pools during deployment. Storage Spaces Direct is not compatible with SIOS DataKeeper, and should not be used.

  • Recovery Time Objective (RTO) and Recovery Point Objective (RPO) - SIOS DataKeeper does not add significantly to a typical cluster single-server outage failover RTO. Assuming appropriate instance sizes are utilized, resource contention is not an issue, SIOS DataKeeper is properly configured and in the mirroring state, and assuming trivial application recovery time, an RTO of <1 minute is possible. Realistically, an RTO of 2 –5 minutes should be expected unless the application being protected (Microsoft SQL Server, SAP, etc.) has an unusually large recovery time. Assuming the same conditions, RPO should be only a few milliseconds larger than the current network write latency between the source and target nodes. RPO can be measured with the QueueCurrentAge perfmon counter. In many cases, the RPO will be measured in milliseconds, but factors like network congestion, abnormally high disk write activity, or slow write performance on the target server can impact RPO greatly. SIOS DataKeeper does not conflict with Amazon EBS snapshots, and it can be used in conjunction with them on the source system. However, restoring a source volume from snapshot is not trivial, and will require a full resync of all data protected by the applicable mirror before the above RPO guidelines are applicable again. To optimize RTO and RPO, follow the best practices guide for SIOS DataKeeper Cluster Edition.

FAQ

Q. I encountered a CREATE_FAILED error when I launched the Quick Start.

A. If AWS CloudFormation fails to create the stack, relaunch the template with Rollback on failure set to Disabled. This setting is under Advanced in the AWS CloudFormation console on the Configure stack options page. With this setting, the stack’s state is retained, and the instance keeps running so that 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. Delete the stack when you finish troubleshooting.

For more information, see Troubleshooting AWS CloudFormation.

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 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, see AWS CloudFormation quotas.

Q. I encountered problems using SIOS DataKeeper on AWS. A. See Troubleshooting in the SIOS Technical Documentation, or see SIOS Support. Contact SIOS pre-sales support during an evaluation period.

Customer responsibility

After you successfully deploy this Quick Start, confirm that your resources and services are updated and configured — including any required patches — to meet your security and other needs. For more information, see the AWS Shared Responsibility Model.

Parameter reference

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

Parameters for deploying into a new VPC

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

Availability Zones (AvailabilityZones)

Requires input

Choose two Availability Zones to use for the VPC subnets.

VPC CIDR (VPCCIDR)

10.0.0.0/16

CIDR Block for the VPC.

Private subnet 1 CIDR (PrivateSubnet1CIDR)

10.0.0.0/19

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

Private subnet 2 CIDR (PrivateSubnet2CIDR)

10.0.32.0/19

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

Public subnet 1 CIDR (PublicSubnet1CIDR)

10.0.128.0/20

CIDR Block for the public DMZ subnet 1, located in Availability Zone 1.

Public subnet 2 CIDR (PublicSubnet2CIDR)

10.0.144.0/20

CIDR Block for the public DMZ subnet 2, located in Availability Zone 2.

Table 2. Amazon EC2 configuration
Parameter label (name) Default value Description

Key pair name (KeyPairName)

Requires input

Key pair name. Public/private key pairs allow you to securely connect to your instance after it launches.

Table 3. Microsoft Active Directory configuration
Parameter label (name) Default value Description

Domain Controller 1 instance type (ADServer1InstanceType)

t2.large

Amazon EC2 instance type for the first Active Directory instance.

Domain Controller 1 NetBIOS name (ADServer1NetBIOSName)

DC1

NetBIOS name of the first Active Directory server (up to 15 characters).

Domain Controller 1 private IP address (ADServer1PrivateIP)

10.0.0.10

Fixed private IP for the first Active Directory server, located in Availability Zone 1.

Domain Controller 2 instance type (ADServer2InstanceType)

t2.large

Amazon EC2 instance type for the second Active Directory instance.

Domain Controller 2 NetBIOS name (ADServer2NetBIOSName)

DC2

NetBIOS name of the second Active Directory server (up to 15 characters).

Domain Controller 2 private IP address (ADServer2PrivateIP)

10.0.32.10

Fixed private IP for the second Active Directory server, located in Availability Zone 2.

Domain DNS name (DomainDNSName)

datakeeper.local

Fully qualified domain name (FQDN) of the forest root domain (for example, example.com).

Domain NetBIOS name (DomainNetBIOSName)

DATAKEEPER

NetBIOS name (up to 15 characters) of the domain for users of earlier versions of Windows.

Domain administrator user name (DomainAdminUser)

siosadmin

User name for the domain administrator account. Note: This is separate from the default "Administrator" account.

Domain administrator password (DomainAdminPassword)

Requires input

Password for the domain administrator user. Must be at least 8 characters containing letters, numbers, and symbols.

Table 4. Remote Desktop Gateway configuration
Parameter label (name) Default value Description

Allowed Remote Desktop Gateway external access CIDR (RDGWCIDR)

Requires input

Allowed CIDR block for external access to the Remote Desktop Gateway.

Number of RDGW hosts (NumberOfRDGWHosts)

1

Number of Remote Desktop Gateway hosts to create (0-4).

Remote Desktop Gateway instance type (RDGWInstanceType)

t2.large

Amazon EC2 instance type for the Remote Desktop Gateway instance.

Table 5. Replication configuration
Parameter label (name) Default value Description

SIOS AMI version (AMIType)

PAYG

AMI type for SIOS license purposes.

SIOS license key FTP URL (SIOSLicenseKeyFtpURL)

Blank string

URL to obtain a license key for SIOS DataKeeper software.

SQL Server version (SQLServerVersion)

2014SP1

Microsoft SQL Server version to install. Choose None if you don’t want to install SQL Server.

Service account name (SQLServiceAccount)

sqlsa

User name for the SQL Server service account. This account is a domain user.

Service account password (SQLServiceAccountPassword)

Requires input

Password for the SQL Server account. Must be at least 8 characters containing letters, numbers and symbols. Leave blank if you don’t want SQL Server.

Data volume size (GiB) (Volume1Size)

100

Volume size for the SQL data drive.

Data Volume Type (Volume1Type)

gp2

Volume type for the SQL data drive.

Data volume IOPS (Volume1Iops)

1000

IOPS for the SQL data drive. (Only used when volume type is io1.)

Table 6. Failover cluster configuration
Parameter label (name) Default value Description

Windows Server OS version for cluster nodes (ClusterNodeOSServerVersion)

WS2012R2

Windows Server OS version for cluster nodes.

Instance type for cluster node 1 (WSFCNode1InstanceType)

i3.xlarge

Amazon EC2 instance type for the first WSFC node.

Cluster node 1 NetBIOS name (WSFCNode1NetBIOSName)

WSFCNode1

NetBIOS name of the first WSFC Node (up to 15 characters).

Cluster node 1 private IP address 1 (WSFCNode1PrivateIP1)

10.0.0.100

Primary private IP for the first WSFC node, located in Availability Zone 1.

Cluster node 1 private IP address 2 (WSFCNode1PrivateIP2)

10.0.0.101

Secondary private IP for WSFC cluster on the first WSFC node.

Cluster node 1 private IP address 3 (WSFCNode1PrivateIP3)

10.0.0.102

Third private IP for SQL Server network name on the first WSFC node.

Instance type for cluster node 2 (WSFCNode2InstanceType)

i3.xlarge

Amazon EC2 instance type for the first WSFC node.

Cluster node 2 NetBIOS name (WSFCNode2NetBIOSName)

WSFCNode2

NetBIOS name of the second WSFC node (up to 15 characters).

Cluster node 2 private IP address 1 (WSFCNode2PrivateIP1)

10.0.32.100

Primary private IP for the second WSFC node, located in Availability Zone 2.

Cluster node 2 private IP address 2 (WSFCNode2PrivateIP2)

10.0.32.101

Secondary private IP for the WSFC cluster on the second WSFC node.

Cluster node 2 private IP address 3 (WSFCNode2PrivateIP3)

10.0.32.102

Third private IP for the SQL Server network name on the second WSFC node.

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

Quick Start S3 bucket name (QSS3BucketName)

aws-quickstart

Name of the S3 bucket for your copy of the Quick Start assets. Keep the default name unless you are customizing the template. Changing the name updates code references to point to a new Quick Start location. This name can include numbers, lowercase letters, uppercase letters, and hyphens, but do not start or end with a hyphen (-). See https://aws-quickstart.github.io/option1.html.

Quick Start S3 bucket Region (QSS3BucketRegion)

us-east-1

AWS Region where the Quick Start S3 bucket (QSS3BucketName) is hosted. Keep the default Region unless you are customizing the template. Changing this Region updates code references to point to a new Quick Start location. When using your own bucket, specify the Region. See https://aws-quickstart.github.io/option1.html.

Quick Start S3 key prefix (QSS3KeyPrefix)

quickstart-sios-datakeeper/

S3 key prefix that is used to simulate a directory for your copy of the Quick Start assets. Keep the default prefix unless you are customizing the template. Changing this prefix updates code references to point to a new Quick Start location. This prefix can include numbers, lowercase letters, uppercase letters, hyphens (-), and forward slashes (/). End with a forward slash. See https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingMetadata.html and https://aws-quickstart.github.io/option1.html.

Parameters for deploying into an existing VPC

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

SQL cluster VPC (VPCID)

Requires input

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

Private Subnet 1 ID (PrivateSubnet1ID)

Requires input

ID of private subnet 1 in Availability Zone 1 (for example, subnet-a0246dcd).

Private Subnet 1 CIDR (PrivateSubnet1CIDR)

10.0.0.0/19

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

Private Subnet 2 ID (PrivateSubnet2ID)

Requires input

ID of private subnet 2 in Availability Zone 2 (for example, subnet-a0246dcd).

Private Subnet 2 CIDR (PrivateSubnet2CIDR)

10.0.32.0/19

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

Table 9. Amazon EC2 configuration
Parameter label (name) Default value Description

Key Pair Name (KeyPairName)

Requires input

Key pair name. Public/private key pairs allow you to securely connect to your instance after it launches.

Table 10. Microsoft Active Directory configuration
Parameter label (name) Default value Description

Domain DNS name (DomainDNSName)

datakeeper.local

Fully qualified domain name (FQDN) of the forest root domain (for example, example.com).

Domain NetBIOS name (DomainNetBIOSName)

DATAKEEPER

NetBIOS name (up to 15 characters) of the domain for users of earlier versions of Windows.

Domain administrator user name (DomainAdminUser)

siosadmin

User name for the domain administrator account. Note: This is separate from the default "Administrator" account.

Domain administrator password (DomainAdminPassword)

Requires input

Password for the domain administrator user. Must be at least 8 characters containing letters, numbers, and symbols.

Domain controller 1 NetBIOS name (ADServer1NetBIOSName)

DC1

NetBIOS name of the first Active Directory server (up to 15 characters)

Domain controller 1 private IP address (ADServer1PrivateIP)

10.0.0.10

Fixed private IP for the first Active Directory server, located in Availability Zone 1.

Domain controller 2 NetBIOS name (ADServer2NetBIOSName)

DC2

NetBIOS name of the second Active Directory server (up to 15 characters)

Domain controller 2 private IP address (ADServer2PrivateIP)

10.0.32.10

Fixed private IP for the second Active Directory server, located in Availability Zone 2

Security Group ID for AD domain members (DomainMemberSGID)

Requires input

ID of the domain member Security Group (for example, sg-7f16e910)

Table 11. Replication configuration
Parameter label (name) Default value Description

SIOS AMI version (AMIType)

PAYG

AMI type for SIOS license purposes.

SIOS license key FTP URL (SIOSLicenseKeyFtpURL)

override

URL to obtain a license key for SIOS DataKeeper software.

SQL Server version (SQLServerVersion)

2014SP1

Microsoft SQL Server version to install. Choose None if you don’t want to install SQL Server.

Service account name (SQLServiceAccount)

sqlsa

User name for the SQL Server service account. This account is a domain user.

Service account password (SQLServiceAccountPassword)

Requires input

Password for the SQL Server account. Must be at least 8 characters containing letters, numbers and symbols. Leave blank if you don’t want SQL Server.

Data volume size (GiB) (Volume1Size)

100

Volume size for the SQL data drive.

Data volume type (Volume1Type)

gp2

Volume type for the SQL data drive.

Data volume IOPS (Volume1Iops)

1000

IOPS for the SQL data drive. (Only used when volume type is io1.)

Table 12. Failover cluster configuration
Parameter label (name) Default value Description

Cluster node OS version (OSVersion)

WS2012R2

Windows Server OS version to use for cluster nodes.

Instance type for cluster node 1 (WSFCNode1InstanceType)

i3.xlarge

Amazon EC2 instance type for the first WSFC node.

Cluster node 1 NetBIOS name (WSFCNode1NetBIOSName)

WSFCNode1

NetBIOS name of the first WSFC Node (up to 15 characters).

Cluster node 1 private IP address 1 (WSFCNode1PrivateIP1)

10.0.0.100

Primary private IP for the first WSFC node, located in Availability Zone 1.

Cluster node 1 private IP address 2 (WSFCNode1PrivateIP2)

10.0.0.101

Secondary private IP for WSFC cluster on the first WSFC node.

Cluster node 1 private IP address 3 (WSFCNode1PrivateIP3)

10.0.0.102

Third private IP for SQL Server network name on the first WSFC node.

Instance type for cluster node 2 (WSFCNode2InstanceType)

i3.xlarge

Amazon EC2 instance type for the first WSFC node.

Cluster node 2 NetBIOS name (WSFCNode2NetBIOSName)

WSFCNode2

NetBIOS name of the second WSFC node (up to 15 characters)

Cluster node 2 private IP address 1 (WSFCNode2PrivateIP1)

10.0.32.100

Primary private IP for the second WSFC node, located in Availability Zone 2.

Cluster node 2 private IP address 2 (WSFCNode2PrivateIP2)

10.0.32.101

Secondary private IP for the WSFC cluster on the second WSFC node

Cluster node 2 private IP address 3 (WSFCNode2PrivateIP3)

10.0.32.102

Third private IP for the SQL Server network name on the second WSFC node.

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

Quick Start S3 bucket name (QSS3BucketName)

aws-quickstart

Name of the S3 bucket for your copy of the Quick Start assets. Keep the default name unless you are customizing the template. Changing the name updates code references to point to a new Quick Start location. This name can include numbers, lowercase letters, uppercase letters, and hyphens, but do not start or end with a hyphen (-). See https://aws-quickstart.github.io/option1.html.

Quick Start S3 bucket Region (QSS3BucketRegion)

us-east-1

AWS Region where the Quick Start S3 bucket (QSS3BucketName) is hosted. Keep the default Region unless you are customizing the template. Changing this Region updates code references to point to a new Quick Start location. When using your own bucket, specify the Region. See https://aws-quickstart.github.io/option1.html.

Quick Start S3 key prefix (QSS3KeyPrefix)

quickstart-sios-datakeeper/

S3 key prefix that is used to simulate a directory for your copy of the Quick Start assets. Keep the default prefix unless you are customizing the template. Changing this prefix updates code references to point to a new Quick Start location. This prefix can include numbers, lowercase letters, uppercase letters, hyphens (-), and forward slashes (/). End with a forward slash. See https://docs.aws.amazon.com/AmazonS3/latest/dev/UsingMetadata.html and https://aws-quickstart.github.io/option1.html.

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.