SQL Server#

As described in Persistency Layer and Database Servers, an SQL Server database is required for Critical Manufacturing to run.

Depending on your infrastructure configuration, the SQL Server database instances may or may not be part of the AWS deployment. There is no requirement on where the database servers are deployed and running, as long as there is connectivity with the EKS cluster.

The following sections give some guides on how to install SQL Server in AWS if you want to have the database running in the AWS infrastructure as well.

EC2 Instances#

One way to install SQL Server in AWS is using EC2 instances. Amazon Elastic Compute Cloud is a service that allows to create and run virtual machines with resizable capacity.

Using EC2, you will create Windows Server EC2 instances following the software and hardware requirements documented in Persistency Layer. When the instances are running, SQL Server needs to be installed and configured on these instances according to the documentation that you can find in Database Servers.

Keep in mind that, similarly to local on-premises servers, these EC2 instances need to be managed, updated, and maintained manually.

AWS RDS Custom#

An alternative way to have your databases running on AWS infrastructure is using AWS RDS Custom for SQL Server. Managed database services for applications that require operating system and database customization The idea behind RDS Custom is to allow the users to initially setup the machine where the database is running, giving access to the underlying EC2 instance to perform specific configurations or installing any required additional software. After this, RDS Custom service will monitor and manage the SQL Server database inside this EC2 instance.

For more information, see https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/rds-custom.html ⧉.