Troubleshooting Your AWS Connection

FlexNet Manager Suite 2021 R1 (On-Premises)

If the results imported from your AWS connection are not what you expect, the following technique may help your troubleshooting efforts. It is a relatively easy way to expose the messages that may be returned by AWS when connection is attempted. These messages may help you identify problems in your configuration. For example, an error of this kind:

The remote server returned an error: (403) Forbidden.
User: arn:aws:iam::65158732158:user/accountName is not authorized to perform:
   iam:ListAttachedGroupPolicies on resource: resourceName

might alert you to check the permissions you have attached to the account that has been blocked.

Remember: Inline policies are not supported. If you used the Add inline policy link when configuring your connection, no inventory can be collected. If this is the case, return to your process for configuring the connection, and follow the instructions carefully about which button to click.

To investigate AWS messages:

1. Take note of the name of the AWS connection that you want to investigate.
   Tip: You can check names of all your existing connections, and their associated inventory beacons, in the Data Inputs page, accessible through the system menu in the top-right corner of the web interface for FlexNet Manager Suite.
2. On the inventory beacon making the connection to AWS, log in using an account with administrator privileges.
3. For convenience, navigate to the installation folder for the FlexNet Beacon software, where you can see ComplianceReader.exe.
   The default location is C:\Program Files (x86)\Flexera Software\Inventory Beacon\DotNet\bin.
4. Run the compliance reader for that connection in verbose mode (-v):

   ComplianceReader.exe -v -s "My AWS Connection Name"

5. Inspect the resulting ouput.