If you successfully connected the AWS integration and noticed you have resources that show up in AWS but not on Vanta's inventory page, please follow the steps in this article.
Scoping & Bulk Tags
First, confirm the resource has not been manually marked out of scope on the integrations page. See, Frequently Asked Questions: How do I Mark Resources out of Scope?, for details on this.
Administrators can also mark resources out of scope with Bulk Tags, please also confirm there are no tags applied to the missing resource. Vanta may show a message saying this is controlled via tags in your cloud provider.
These tags are VantaNonProd and VantaNoAlert tags and they can prevent resources from being pulled in scope. Some administrators may have custom inventory tags set up which do match the default standard tags, but achieve the same effect.
If you are not sure how to check for tags in AWS, see this article for more details.
If you have a VantaNoAlert tag applied to the resource, please remove it to bring it into scope. It does not matter what the value is set to, if the VantaNonProd value is detected as a key the instance will be marked out of scope.
If you have VantaNonProd set with a value of true, please either remove it or set it to false.
If none of these tags are applied to the instance, and it has not been toggled out of scope manually on the integrations page, please move on to the next step.
The next step is to confirm that the region the resource exists in is selected in Vanta. See, How to edit the region selected for AWS accounts/organizations, for more details about this. If the region
If you confirmed the region is in scope, please submit a ticket to Vanta Support with a screenshot of the resource, or one of the resources showing the name, ID, status, and region in view:
Feel free to remove sensitive information such as IP Addresses.