Insert excerpt
| Note |
|---|
Prerequisites In order to connect EmpowerID to AWS, you must have an AWS domain with an account that EmpowerID can use to connect to AWS. (EmpowerID recommends using a dedicated service account.) At a minimum, this account must have a policy with permission to read the user, group and computer data in AWS. If you plan to use EmpowerID to provision, deprovision and modify this data in AWS, the profile needs to have create, update and delete permissions as well. In addition, you must provide EmpowerID with the following information:
|
After ensuring you have met the prerequisites, you do the following to connect EmpowerID to AWS:
Create an account store in EmpowerID for AWS.
Configure EmpowerID settings for the account store connection, including whether to provision EmpowerID Persons during inventory or in batches using the Account Inbox permanent workflow (recommended).
Review and configure the attribute flow rules for the account store.
Turn on inventory.
Enable the Account Inbox Permanent Workflow when ready—if you are using batch processing to provision Person objects from the inventoried user accounts. This is the recommended method.
Monitor Inventory.
Step 1 – Create an account store for AWS
On the navbar, expand Admin, then Applications and Directories, and click Account Stores and Systems.
On the Account Stores page, click Create Account Store.
Select Amazon AWS from the list of system types and click Submit.
This opens the AWS Settings form, which is where you enter information about your Amazon AWS instance needed to connect EmpowerID to it.
Enter the following information in the AWS Settings form to connect EmpowerID to your Amazon instance:
Site Name — The address of your AWS site
Client API Key — The Access Key ID generated by Amazon for the service account
Client API Secret — The Secret Access Key generated by Amazon for the service account
Tenant ID — Tenant ID for your AWS site
Click Submit.
EmpowerID creates the account store and the associated resource system. The next step is to configure the attribute flow between the account store and EmpowerID.
Step 2 – Configure Attribute Flow
| Tip |
|---|
EmpowerID supports the configuration of attribute synchronization rules for flowing attribute changes between directories and the EmpowerID Identity Warehouse. Attribute Flow rules are visually configured and are always relative to the relationship between an attribute in a directory and the corresponding attribute in the EmpowerID Identity Warehouse. Attribute Flow rules define the specific fields and attributes that are synchronized between the EmpowerID Identity Warehouse person objects and the external user accounts to which they are linked. Additionally, Attribute Flow rules can be weighted by account store. For example, if you have connected EmpowerID to an HR system as well as Active Directory, and you want any changes made to an attribute in the HR system to take priority over changes made in Active Directory or EmpowerID (while allowing changes to be made in any system), you would give a higher score for each CRUD operation originating from the HR account store and correspondingly lower scores for the Active Directory account store. The following flow rules are available:
The following CRUD operations are available:
|
From the Account Stores tab of the Account Stores and Systems page, search for the account store you just created and click the Account Store link for it.
Click the Attribute Flow Rules tab to view the current rules for the account store. Please note that the attributes available depend on the account store.
To change the flow for an attribute, click the Attribute Flow drop-down located between the Person Attribute column and the External Directory Attribute column, and select the desired flow direction from the context menu.
To change the score for any of the available CRUD operations (Create, Update and Delete), enter the new score in the appropriate field. By default, scores are weighted evenly, which means that a change to an attribute originating in one connected external directory has the same authority as a change to an attribute occurring in another connected external directory.
| Info |
|---|
EmpowerID only considers scores for attribute CRUD operations when multiple account stores with the same user records are connected to EmpowerID, such as would be the case if an HR System and this account store were being inventoried by EmpowerID. |
Now that the attribute flow has been set, the next steps include configuring the account store and enabling EmpowerID to inventory it.
Step 3 – Configure account store settings
On the Account Store and Resource System page, select the Account Store tab and then click the pencil icon to put the account store in edit mode.
This opens the edit page for the AWS account store. This page allows you to specify the account proxy used to connect EmpowerID to your AWS account as well as how you want EmpowerID to handle the user information it discovers in AWS during inventory. Settings that can be edited are described in the table below the image.
Insert excerpt IL:Account Store Settings (AWS) V21 IL:Account Store Settings (AWS) V21 nopanel true Edit the account store as needed and then click Save to save your changes.
Next, enable the Account Inbox permanent workflow to allow the Account Inbox to provision or join the user accounts in AWS to EmpowerID Persons as demonstrated below.
| Tip |
|---|
EmpowerID recommends using the Account Inbox for provisioning and joining. |
Step 4 – Enable Account Inbox Permanent Workflow
On the navbar, expand Infrastructure Admin > EmpowerID Server and Settings and select Permanent Workflows.
On the Permanent Workflows page, click the Display Name link for Account Inbox.
On the Permanent Workflow Details page that appears, click the pencil icon to put the workflow in edit mode.
Check Enabled.
Click Save to save your changes.
Step 5 – Monitor Inventory
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
| Div | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
IN THIS ARTICLE
|