Active Roles 8.1.4 - Quick Start Guide

Before starting the deployment and configuration of Active Roles to manage AWS Managed Microsoft AD via AWS Directory Service, make sure that the following requirements are met.

NOTE: When setting up a virtual environment, carefully consider the configuration aspects such as CPU, memory availability, I/O subsystem, and network infrastructure to ensure the virtual layer has the necessary resources available. Please consult One Identity's Product Support Policies for more information on environment virtualization.

Connectivity requirements

You must have:

Stable network connectivity to Amazon Web Services (AWS).
Port 1433 open and available for the Amazon Relational Database Service (RDS) service.
Access to the AWS service with the AWSAdministratorAccess permission.

NOTE: Make sure that you have AWSAdministratorAccess permission, as it is required for certain configuration steps. The AWSPowerUserAccess permission is not sufficient for completing the entire configuration procedure.

Infrastructure requirements

To deploy and configure Active Roles for AWS Managed Microsoft AD, you must have access to the following AWS services and resources:

AWS Managed Microsoft AD deployed via AWS Directory Service.
One or more Amazon Elastic Compute Cloud (EC2) instance(s) hosting the Active Roles services and components.

The EC2 instance(s) must have, at minimum:
- 2 vCPUs running at 2.0 GHz.
- 4 GB of RAM.
TIP: One Identity recommends hosting the main Active Roles services and components (the Active Roles Service and Console, and the Active Roles Web Interface) on separate EC2 instances. If you deploy all Active Roles services and components in a single EC2 instance, use a more powerful instance to ensure a better user experience for the product.

NOTE: AWS Managed Microsoft AD support was tested with a single t2.large EC2 instance.
An Amazon Relational Database Service for SQL Server (RDS for SQL Server).

NOTE: AWS Managed Microsoft AD support was tested with an RDS instance running the latest version of Microsoft SQL Server.

Make sure that all these components are discoverable or visible to each other.

Main steps of configuring Active Roles for AWS Managed Microsoft AD

If your organization and environment meet the Deployment requirements for AWS Managed Microsoft AD support, then configuring Active Roles for managing AWS Managed Microsoft AD via AWS Directory Service has the following main steps:

Creating your AWS Managed Microsoft AD environment.
Creating an Amazon Elastic Compute Cloud (EC2) instance for Active Roles.
Joining the EC2 instance to AWS Managed Microsoft AD.
Creating an Amazon Relational Database Service for SQL Server (RDS for SQL Server) instance to host the Active Roles Management History and Configuration databases.
Verifying the connectivity between the EC2 and RDS instances.
Installing and configuring Active Roles on the EC2 instance.
(Optional) Installing and configuring Active Roles Synchronization Service on the EC2 instance. For more information, see Installing and configuring Synchronization Service to manage AWS Managed Microsoft AD resources in the Active Roles Synchronization Service Administration Guide.

Creating the AWS Managed Microsoft AD instance

To deploy and configure Active Roles in Amazon Web Services (AWS) for managing AWS Managed Microsoft AD, first you must create an AWS Directory Service instance hosting your AWS Managed Microsoft AD instance. For more information on configuring the service in the AWS console, see Setting up AWS Directory Service in the AWS Directory Service documentation.

NOTE: Consider the following when creating the AWS Managed Microsoft AD instance:

Make sure that the connectivity requirements listed in Deployment requirements for AWS Managed Microsoft AD support are met.
During the procedure take note of the following values, as they will be required in later procedures:
- Directory DNS name: The fully qualified domain name (FQDN) of your AD service (for example, activeroles.demo).
- Directory NetBIOS name: The NetBIOS name (or shortname) of your AD service (for example, ARDEMO).
- Admin password: The password of the default admin account (named admin).
After specifying all required settings, it takes approximately 30-40 minutes to create the AWS Managed Microsoft AD instance. If you run into any issues when creating the environment, see Troubleshooting AWS Managed Microsoft AD in the AWS Managed Microsoft AD documentation.

Creating the EC2 instance for Active Roles

To deploy and configure Active Roles in Amazon Web Services (AWS) for managing AWS Managed Microsoft AD, you must create an Amazon Elastic Compute Cloud (EC2) instance hosting your Active Roles installation.

Complete the procedure in AWS as described in Set up to use Amazon EC2 in the Amazon EC2 documentation. If you run into any problems when configuring or attempting to connect to the EC2 instance, see Troubleshoot EC2 Windows instances in the Amazon EC2 documentation.

NOTE: Consider the following when creating the EC2 instance:

Make sure that the connectivity requirements listed in Deployment requirements for AWS Managed Microsoft AD support are met.
For the operating system on the EC2 instance, select a Microsoft Windows Server AMI supported by Active Roles. For the list of supported Windows Server operating systems, see System requirements in the Active Roles Release Notes.
Select an EC2 instance type that has, at minimum:
- 2 vCPUs running at 2.0 GHz.
- 4 GB of RAM.
One Identity recommends setting the storage to a minimum of 60 GiB of gp2 root volume.

TIP: For consistency, once you logged in to the EC2 instance, rename the virtual machine to the same name that you originally defined for the EC2 instance in the AWS console.

Please select your product:

To serve you better, please complete the Purpose of your Chat:

Recommended Solutions for Your Problem