Prerequisites and Setting Up
IT Asset Management
(Cloud)
The AWS adapter is configured on a convenient inventory beacon, for which there are the following prerequisites:
- PowerShell 3.0 or later is running on Windows Server 2008 R2 SP1 or later,
or Windows 7 SP1 or later; with the PowerShell execution policy set
to RemoteSigned.Note: If you choose to install
AWS.Tools.Common
, which is the modular collection where you can install individual AWS Tools for PowerShell, the minimum version is increased to PowerShell 5.1 or later. - .NET Framework 4.7.2 or newer is required.
- The FlexNet Beacon software installed on the inventory beacon must be release 13.1.1 (shipped with IT Asset Management 2018 R2) or later.
- The inventory beacon must have Internet access to the central application server for IT Asset Management, so that it can upload inventories and download policies.
- A web browser is installed and enabled on the inventory beacon.
- You must log onto the inventory beacon, and run FlexNet Beacon, using an account with administrator privileges.
- You must have downloaded AWS Tools for PowerShell from https://aws.amazon.com/powershell/, and installed them on the
inventory beacon. The minimum required version of these tools is
3.3.283.0. Tip: To check the version installed on your inventory beacon:
- As administrator, run PowerShell.
- Execute the
Get-AWSPowerShellVersion
cmdlet.
Note: The permissible values for Instance region are currently hard coded in the AWS Tools for PowerShell. This means that if AWS create additional regions, and you want to have instances in one of the new regions, you will need to update AWS Tools for PowerShell at that time.From release 2.0.0 of thePowerShellGet
cmdlet (which allows you toInstall-Module
), theScope
option defaults toCurrentUser
. Unless you are installing the modules using the account that normally runs your FlexNet Beacon and triggers the AWS connector, you must specify the non-default value ofAllUsers
, such that the inventory beacon's operating account (typicallySYSTEM
) can run the connector. Example command lines for installation are:- For the modular AWS Tools for PowerShell (requires PowerShell 5.1 or
later), run this sample script that encompasses all the required
modules needed to run the connector:
Install-Module -Name AWS.Tools.Common -Scope AllUsersInstall-Module -Name AWS.Tools.ConfigService -Scope AllUsersInstall-Module -Name AWS.Tools.EC2 -Scope AllUsersInstall-Module -Name AWS.Tools.IdentityManagement -Scope AllUsersInstall-Module -Name AWS.Tools.Organizations -Scope AllUsersInstall-Module -Name AWS.Tools.RDS -Scope AllUsersInstall-Module -Name AWS.Tools.S3 -Scope AllUsersInstall-Module -Name AWS.Tools.SecurityToken -Scope AllUsers
- For the bundled, legacy AWS Tools for PowerShell (requires
PowerShell 3.0 or later), run this sample script:
Install-Module -Name AWSPowerShell -Scope AllUsers
PSModulePath
, such as C:\Program Files\WindowsPowerShell\Modules (check the preference value on your inventory beacon).
- A policy allowing access to your EC2 service
- A policy allowing access to an Identity and Access Management (IAM) entity
- The IAM roles to grant access to AWS resources (not required when using the Configuring Connections to AWS EC2 using IAM Users method)
- The IAM user account (still within AWS) with minimum privileges that makes the connection to AWS APIs and imports the available data (only required for the Configuring Connections to AWS EC2 using IAM Roles without FlexNet Beacon installed on EC2 instance only).
Using Proxy Connections
The connection to AWS supports optional use of a proxy for connections that do not connect using a locally installed FlexNet Beacon.
Step-by-step instructions for creating these, and then configuring the connection to AWS ECS, are available in the online help at
.IT Asset Management (Cloud)
Current