Manual Setup
Manual setup is required if you want to integrate Active Directory (AD) with Ansys Gateway powered by AWS.
Although users must sign in to Ansys Gateway powered by AWS using their Ansys ID, integrating Active Directory with Ansys Gateway powered by AWS enables users to sign in to virtual machines using the credentials associated with their Active Directory user account.
Prerequisites
AWS account
Secure server to host Active Directory (AD). The server can be hosted locally (on-premises) or in a cloud (for example, Amazon or Microsoft Azure) provided that it can reached by the AD Connector.
Secure server to host the Ansys Gateway powered by AWS AD Connector service. The server can be hosted locally (on-premises) or in an AWS Virtual Private Cloud (VPC).
License server with Ansys application licenses
Established network connectivity between the license server and the AWS VPC
To avoid latency in communication, Ansys recommends that the server hosting AD and the server hosting the AD Connector service have close physical proximity to each other.
Manual Setup Process
An IT administrator with an Ansys ID and AWS Administration privileges must complete the following steps:
Go to https://aws.amazon.com/marketplace and find Ansys Gateway powered by AWS. When you subscribe to Ansys Gateway powered by AWS, a setup wizard is launched.
Click Show more installation options, then select the Manual setup with Active Directory integration (Not recommended) option.
Follow the guided setup (summarized below). Specific details, diagrams, and IT requirements are provided directly in the onscreen setup.
On your AD server, create an Organizational Unit (OU) to be used for Ansys Gateway powered by AWS operations. During the setup process, two security groups will be automatically created in this OU.
Prepare a server to host the Ansys Gateway powered by AWS AD Connector service.
In AWS, set up a Virtual Private Cloud (VPC) with at least one subnet. Refer to Requirements for Virtual Private Clouds (VPCs).
Create a secure and private connection between your local network and the VPC. Also, ensure that the license server to be used for Ansys application licenses is reachable by the VPC.
When prompted, specify company and domain information to allow Ansys Gateway powered by AWS to communicate with your local environment. Once submitted, a custom configuration file is generated for your company (to be used in the next step).
Install and configure the Ansys Gateway powered by AWS AD Connector service. This includes applying the custom configuration file generated in the previous step and creating a domain join user for Ansys Gateway powered by AWS to use. Once the service is running, your company's Active Directory starts synchronizing with the Ansys Gateway powered by AWS backend.
On the AD server, add administrator and standard user accounts to the security groups created within the Organizational Unit (OU).
For each user that you add, specify the user's Ansys ID email address in the mail attribute of their Active Directory account.
Launch Ansys Gateway powered by AWS and sign in with your Ansys ID.
If at any time you have trouble accessing Ansys Gateway powered by AWS, you can use the Ansys Service Dashboard to check whether Ansys services are currently running. See Checking the Status of Ansys Services.
If users are unable to sign in to Ansys Gateway powered by AWS, see Can't sign in to Ansys Gateway powered by AWS in the Troubleshooting Guide.
Post-Setup Steps
To prepare Ansys Gateway powered by AWS for your company's use, refer to the following topics:
- To provide Ansys Gateway powered by AWS with access to your AWS resources and prepare the Ansys Gateway powered by AWS environment for use, see Post-Setup Steps in Ansys Gateway powered by AWS.
- If your Ansys application license server is on a local network, see Connecting an Ansys Application License Server.