Netscan AWS Integration (IAM instance roles)
While setting up NetScan Policy and choosing AWS can we instead rely on the IAM instance role of the collector instance (when the collector is an EC2 instance running in AWS) instead of hardcoding AWS AccessKey/SecretKey in the Netscan policy? http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-roles-for-amazon-ec2.html5Views0likes1CommentNetscan Policy new discovery alerting
Hi, We think it would be a good idea whenever a netscan ran it can pickup the devices that were newly discovered in a subnet. It would be a nice addition that those devices get included in the email that is sent out on a completed netscan run. In that case we can monitorwhat lives in a particular subnet. Maybe we can add the devices that went down also to the list. Br, Stijn3Views0likes0Comments
More AWS-centric options for Netscan via AWS (EC2) Method
- Token to name a device based on AWS tag - The ability to exclude devices based on region - All AWS tags should be imported/populated/inherited - Netscan should populate the system.aws.resourceid property instead of system.ec2.resourceid. The former is actually used by the default AWS_EC2 datasource. Probably moot if my third bullet is done.3Views0likes1CommentAbility to ignore some IPs in NetScan Policies, Docker Problem
We have multiple servers running Docker. Docker creates a network interface with the ip 172.17.0.0/16 by default, using 172.17.0.1 for the host. When we run a netscan policy, it finds the first server, and any subsequent servers running docker will be excluded as it detects that they all have the ip of 172.17.0.1 and assumes they are the same server. I want to be able to ignore some ips / ranges so the NSP does not incorrectly assume 2 devices are the same.1View0likes3Comments
