Currently the tool assumes all known AWS Regions. Which is great as it makes the validate analysis complete!
However, if my organization has limited ourselves to specific regions the tool does not take that into consideration. It wastes a TON of time looking at regions that are not interesting.
Provide a means where the user can provide an argument to limit the regions that are validated.
PS. This issue/suggestion would probably never occurred if some form of proc forks were used. In that the main regions we are using take a lot of time to process and the unused could have easily just been done in the background and never resulted in any useful information.
Currently the tool assumes all known AWS Regions. Which is great as it makes the validate analysis complete!
However, if my organization has limited ourselves to specific regions the tool does not take that into consideration. It wastes a TON of time looking at regions that are not interesting.
Provide a means where the user can provide an argument to limit the regions that are validated.
PS. This issue/suggestion would probably never occurred if some form of proc forks were used. In that the main regions we are using take a lot of time to process and the unused could have easily just been done in the background and never resulted in any useful information.