Prerequisites and Setting Up

FlexNet Manager Suite 2020 R1 (On-Premises)

The AWS EC2 connector 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.
• The FlexNet Beacon software installed on the inventory beacon must be release 13.1.1 (shipped with FlexNet Manager Suite 2018 R2) or later.
• 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 Windows 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:

  1. As administrator, run AWS Tools for Windows PowerShell.
  2. Execute the Get-AWSPowerShellVersion cmdlet.

  New versions are available for download from https://aws.amazon.com/powershell/.
  Note: The permissible values for Instance region are currently hard coded in the AWS Tools for Windows 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 Windows PowerShell at that time.

On the AWS side, you must first create:

• Within AWS, you must create a policy allowing access to your EC2 service
• Similarly, you must create 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 (Configuring Connections to AWS EC2 using IAM Roles without FlexNet Beacon installed on EC2 instance only)
• Finally, on the inventory beacon that is to make the connection to AWS, you must specify the connection (which is automatically scheduled for you).

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 on the online help at FlexNet Manager Suite Online Help > Inventory Beacon Help > Inventory Systems Page > Connecting to External Inventory Systems > Managing PowerShell Connections > Managing AWS EC2 Connections.