From the way the scanning target gets set up, it appears that only 1 instance of each region will be scanned, due to it using the first credentials it finds that will work. Azure, on the other hand, can have multiple subscriptions added, allowing scanning multiple accounts.
Single AWS accounts are unrealistic, whether you manage client accounts or have separate dev and prod accounts. Can this get updated to support multiple AWS accounts?