We only show up to four recent versions or revisions of AMI images for each SQL version. We don't allow installation from an AMI image that is older than the latest four versions.

Deployment with a custom AMI assumes that install media is present in the image. This is needed for FCI configuration for the following reasons:

As part of deployment, workload factory doesn't install a custom AMI with multiple Microsoft SQL Server instances. Only the default Microsoft SQL Server instance is selected and configured as part of deployment.

Rollback and retry for failed deployments aren't supported in workload factory. You can roll back or retry a failed stack from the CloudFormation console in AWS.

The following DNS resources aren't removed from Active Directory and DNS when you roll back a test or failed deployment from the CloudFormation console in AWS:

You'll need to cleanup these up manually or wait for the domain to purge stale entries.

Managing Always On availability groups configurations isn't supported in workload factory.

If you select “user-managed Active Directory” during Microsoft SQL Server deployment in workload factory, you must provide a security group that allows traffic between the EC2 instances to the directory service for deployment. Workload factory doesn't automatically attach the security group for user-managed Active Directory like it does for AWS Managed Microsoft AD.

Custom encryption keys for FSx for ONTAP aren't listed based on service applicability. You must choose the appropriate key. AWS managed keys are filtered based on applicability to service.

A downloaded or copied Codebox-generated CloudFormation template (YAML file) has a limited retention period of seven days.

The maximum number of sandbox clones that can be created from a database server is 90.

Microsoft SQL Server detection isn't saved. Each time you access Databases in workload factory, Microsoft SQL Server detection runs again to identify SQL installations in the region.

In the Inventory tab, the estimated cost shown for each Microsoft SQL instance is calculated at the FSx for ONTAP file system level and not for volumes hosting the SQL instance.

Workload Factory doesn't support creating or saving configurations for Microsoft SQL Server with multiple FSx for ONTAP file systems. Only one FSx for ONTAP file system configuration deployment is supported.

Microsoft SQL Server deployment in a private network with no outbound connectivity using Terraform is only supported in us-east-1 (N. Virginia) region.