AP Profiles

AP Profiles refers to Auto-Provision Profiles!

You can enable Auto-Provisioning of WorkSpaces by adding users to an Active Directory group and configuring WorkSpaces Manager to read users from that group. To start, select Add Profile.

When Auto-Provision is enabled, the service will poll the Active Directory groups every 15 minutes for new members.

The following information is required to create and configure an Auto-Provision (AP) Profile:

• AD Group Name – Specify the Active Directory group used for provisioning.

• Account – Select the AWS account where the WorkSpaces will be created (if multiple accounts are configured).

• Region – Select the AWS Region for the WorkSpaces.

• Directory – Select the WorkSpaces directory (AWS Directory Services or AD Connector).

• Bundle – Select the WorkSpaces bundle.

• Running Mode – Select the desired running mode.

• Encryption – Enable or disable root and user volume encryption.

• Directories – Enable or Disable the use of multiple directories. When enabled, Auto-Provision selects the directory with the highest available IP capacity when creating a WorkSpace.

• Termination – Enable or disable termination on group removal.

• Tags – Select the profile tags to be automatically applied.

• Temporary Provisioning: Define how many days the WorkSpace remains active before automatic termination, and how many days prior to termination users are notified.

Removing a user from an AD group does not automatically terminate the WorkSpace by default. Termination on group removal will only occur if the Terminate on Group Removal option is enabled and the WorkSpace has the Automation - Managed tag applied.

You will only be allowed to add "Fixed Tags" in Profile Tags once you’ve saved the Auto-Provision profile. If you go back to edit this profile, you can then add the Fixed Tags.

WSM uses Directory Selection Behaviour, where when Use Multiple Directories is enabled, you can select one or more directories for provisioning. The service then evaluates the selected directories based on available IP capacity and chooses the most suitable option. If provisioning fails due to capacity constraints, it automatically retries using the next best directory, and all attempts are logged for audit and troubleshooting purposes.