- RDP EC2 Instances 

- SSH EC2 Instances

- Password Manager to manage credentials

(Bug & Fixes)

Looks like Move EC2 is trying to use 2010-05-08 version of EC2, which has been deprecated. This results in the request for IAM roles failing, causing the UI to show there are no IAM roles available.

Log output:
2023/06/18 8:44 PM - AWS-IAM | Cannot Get List of IAM Roles. Error: The requested version (2010-05-08) of service AmazonEC2 does not exist

After a failure when trying to move an EC2 instance (such as insufficient quotas in the destination region), the MoveEC2 tool doesn't seem to clean up all the resources it creates properly, resulting in errors on subsequent move attempts that the ami storage isn't available in the source region (even thought it is).

Log excerpt:
2023/06/18 8:44 PM - AWS-EC2 | Starting the migration of EC2 instance [i-0819*OMITTED*444]....
2023/06/18 8:44 PM - AWS-EC2-TAG | [1] EC2 Tags exported
2023/06/18 8:44 PM - AWS-EC2 | Checking source EC2 Instance state....
2023/06/18 8:44 PM - AWS-EC2 | Instance [i-0819*OMITTED*444] state [stopped]
2023/06/18 8:44 PM - AWS-EC2 | EC2 Instance state: stopped
2023/06/18 8:44 PM - AWS-EC2 | Creating AMI image...
2023/06/18 8:44 PM - AWS-Images | AMI for Instance [i-0819*OMITTED*444] is [ami-030*OMITTED*cdb]
2023/06/18 8:44 PM - AWS-EC2 | Copying AMI image to another AWS Region...
2023/06/18 8:44 PM - AWS-Images | Copying AMI [ami-030*OMITTED*cdb] from Region [US East (Northern Virginia)] to Region [US West (Northern California)]
2023/06/18 8:44 PM - AWS-Images | Cannot copy AMI [ami-030*OMITTED*cdb] from Region [US East (Northern Virginia)] to Region [US West (Northern California)] - Error The storage for the ami is not available in the source region.
2023/06/18 8:44 PM - AWS-EC2 | AMI status failed. Error: Invalid id: "ERROR" (expecting "ami-...")

Add Inventories of EKS, ECS and Fargate to AWS Inventory

Release AWS Inventory for macOS

Any chance you could add support for assumerole auth? That is, have a single account (probably a Orgroot), but then for each addtional account, use a named assumerole to pull data from the other accounts. 

That was, you could have a set of canned roles for running Inventory across a wide number of accounts, but only need the credentials from the Primary account. And let IAM assumerole configuration allow actions for the other account.