Amazon Inspector uses AWS Identity and Access Management (IAM) service-linked roles. A service-linked role is a unique type of IAM role that is linked directly to Amazon Inspector. Service-linked roles are predefined by Amazon Inspector and include all the permissions that the service requires to call other AWS services on your behalf.
Amazon Inspector uses the service-linked role named AWSServiceRoleForAmazonInspector2 refer- https://docs.aws.amazon.com/inspector/latest/user/using-service-linked-roles.html
I had a similar problem with Inspector v2 not scanning ECR repos after it was first set up shortly after re:Invent. I opened a support case on it and they found that a race condition could occur back then that is fixed now. There was a workaround to get it going for my account. The workaround was to got to ECR and disable continuous scanning, save it, wait a minute, then re-enable continuous scanning and save that. Shortly after that ECR repos were producing findings. You might want to give that a shot.
Amazon ECR Enhanced scanningasked 9 months ago
AWS Inspector2/Enhanced Scanning Uses Image Tags to Detect OSasked 7 months ago
Amazon Inspector v2 ECR enhanced scans are not finding expected vulnerabilitiesasked 9 months ago
INSTALL_PARSE_FAILED_NO_CERTIFICATES: Scanning Failed.: No signature found in package of version 2 or newer for packageasked 2 months ago
inspector2 scan frequencyAccepted Answer
Inspector2 ecr scanning
Spectrum on Redshift Shift Serverless with Enhanced VPC routingasked 2 months ago
Enhanced fan-out and data analyticsasked 2 years ago
RDS Enhanced Monitoringasked 4 years ago
Timestream queries without scanning all the recordsasked 3 months ago