How to remediate reported vulnerabilities? Is there an practical example somewhere?
@muthugowthams9205 Жыл бұрын
@awssupport why the amazon inspector focus only on the ec2 and ecr and lambda
@eakokel Жыл бұрын
You didnt cover export findings to s3 bucket :(
@mohammedmustafaali10492 жыл бұрын
How to Solve "Unmanaged by inspector"?
@letsCelebrateWisdom Жыл бұрын
Can it b Indian English tone ?
@ericanthony40512 жыл бұрын
very informative
@swagatkulkarni92372 жыл бұрын
Great content!
@hungdohoangminh2064 Жыл бұрын
Very poor content! It is not usefull at all ! Inspector v1 is easy to use.
@awssupport Жыл бұрын
We're sorry to hear this, Hung. We've forwarded your feedback directly to our service teams for review. You're welcome to send us your detailed thoughts around how we can improve this experience, via any of the following available options, here: go.aws/feedback. ^BG
@hungdohoangminh2064 Жыл бұрын
@@awssupport How i can run a simple cev scan with inspector v2 like i do with inspector v1 ? I just enable it and it show nothing.
@awssupport Жыл бұрын
This article may be useful: go.aws/3WhL7cK. For more technical assistance with your resources, there are a few ways to get help: go.aws/get-help. ^RC
@hungdohoangminh2064 Жыл бұрын
@@awssupport i have all InspectorDistributor-do-not-delete, InspectorInventoryCollection-do-not-delete , InvokeInspectorSsmPlugin-do-not-delete and InspectorResourceDataSync-do-not-delete in my AWS System manager already, all status is Success. But my inspector v2 give nothing. There is only Network Reachability. I can easy make a report with v1, but can do that with v2. My instance is place in region ap-southeast-1 which is not support v1.
@awssupport Жыл бұрын
Sorry to hear of this continued frustration, Hung. I recommend reviewing the supported systems and languages, here: go.aws/3uUVAzb. 📚 This will ensure Inspector scans your resources successfully. If you need additional help, please reach out to our community of experts in re:Post: go.aws/aws-repost. 👨💻 ^RS