Skip to main content

Register instances in workload factory for Databases

Contributors netapp-rlithman
PDFs

Register instances so that you can monitor instance and database status, resource utilization, protection, and storage performance in workload factory for Databases.

Databases can only register instances with FSx for ONTAP file system storage.

About the task

Registering an instance includes two steps - authenticating the instance and preparing the instance by making sure all AWS, NetApp, and PowerShell modules are installed on the instance.

You can authentic links using SQL Server credentials or with Windows credentials.

Note Workload factory supports only Microsoft SQL Server instance registration and management. Depending on the AWS account credentials you select in workload factory, PostgreSQL and Oracle hosts might appear in the Inventory. Currently, workload factory supports unregistered PostgreSQL instances running only on Amazon Linux operating systems and Oracle instances running only on Red Hat Enterprise Linux.
Registering an instance in a private network

To register an instance in a private network with no external connectivity, the following endpoints need to be available in the VPC with association to the subnets where SQL servers are present. Ensure the interface endpoints allow port 443 in the attached Security Group.

  • S3 Gateway/endpoint

  • ssm

  • ssmmessages

  • fsx

    If you use a proxy server for all outbound connections from EC2 instances, you must allow access to the following domains so that management operations work:

  • .microsoft.com

  • .powershellgallery.com

  • .aws.amazon.com

  • .amazonaws.com

Before you begin

Consider the following before registering an instance:

  • The host for the instance must appear in the Inventory tab. For hosts to appear in the inventory, you must add AWS account credentials and read-only or read/write mode permissions.

  • When using Windows domain user credentials to authenticate for SQL Server management operations, workload factory enables CredSSP delegation on the SQL nodes. If the CredSSP delegation is blocked for all domain computers with the group policy, authenticating with Windows user credentials doesn't work.

Register an instance

Registering an instance includes instance authentication and preparation.

Steps

  1. Log in using one of the console experiences.

  2. In the Databases tile, select Go to Databases inventory.

  3. In Databases, select the Inventory tab.

  4. In the Inventory tab, select the Instances tab.

  5. Select to register a single instance or register multiple instances.

    1. Single instance registration: Navigate to the instance to manage and select Register instance.

    2. Multiple instance registration: Select the Register multiple instances button.

      Two options are available for registering multiple instances. In both cases, the instances must share the same authentication status (unauthenticated or authenticated).

      • Unauthenticated instances: Select multiple unauthenticated instances to register. These instances must share the same authentication credentials and FSx for ONTAP credentials. Select Apply and then Next.

      • Authenticated instances: Select multiple authenticated instances to register and then select Next.

  6. In step 2 on the Register instances page, select the instance authentication mode, enter the following details, and select Next. If instances are already authenticated, select Next.

    • SQL Server authentication: Enter the SQL Server user name and password, and the FSx for ONTAP file system user name and password.

    • Windows authentication: Enter the Windows user name and password, and the FSx for ONTAP file system user name and password.

  7. In step 3, prepare the instance by making sure the instance meets required prerequisites. If all required modules are installed and prerequisites are met, select Next to register the instance. If you need to take action, follow these steps.

    1. If missing, select workload factory to Install missing AWS and NetApp PowerShell modules.

    2. If missing, select workload factory to Install missing PowerShell 7. Installing missing PowerShell module 7 requires a system reboot.

    3. Review the prerequisites list for the following capabilities. One prerequisite must be complete to register the instance.

      • Review well-architected issues and recommendations

      • Fix well-architected issues

      • Create database

      • Create database copies (sandbox)

        Completing prerequisites includes updating your AWS IAM policy permissions, EC2 IAM instance profile permissions, SQL Server permissions, and PowerShell modules.

    4. Complete at least one missing prerequisite to continue.

    5. When one or more prerequisites are complete and checks are Ready, you can select to Register the instance.

Result

The request to register the instance initiates. Select the Job monitoring tab to to track progress.