Would it be possible to add feature, to proceed on some errors, for example if no serv

Hi <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="

Also, <a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-ur

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

[SecurityHub] InvalidAccessException when account is not subscribed about aws-recon HOT 4 CLOSED

joshlarsen commented on July 28, 2024

[SecurityHub] InvalidAccessException when account is not subscribed

from aws-recon.

Comments (4)

joshlarsen commented on July 28, 2024

Hi @thejazzid, yes this is planned. This will likely have two components:

for errors that are related to service availability, silently ignore and continue. This is what we currently do, but it looks like we missed EMR.
for errors that are due to lack of permissions, ignore by default, with a command line option to raise the error.

from aws-recon.

joshlarsen commented on July 28, 2024

Also, @thejazzid, what region were you getting that EMR error from?

from aws-recon.

thejazzid commented on July 28, 2024

@joshlarsen Thanks for info. will be looking forward for new releases. I would love to contribute, but I'm not ruby guy.

As for region - according to last successful commands it was ap-east-1

t7.ap-east-1.EC2.describe_vpc_peering_connections.0
t3.ap-east-1.RDS.describe_db_engine_versions.0
t3.ap-east-1.RDS.describe_db_engine_versions.1
t3.ap-east-1.RDS.describe_db_engine_versions.2
t3.ap-east-1.RDS.describe_db_engine_versions.3

Finished in 240 seconds. Saving resources to.....

from aws-recon.

joshlarsen commented on July 28, 2024

Splitting this into two issues. The EMR issue is now #67.

from aws-recon.

Recommend Projects