You can set up vRealize Network Insight collector for AWS by importing Amazon Machine Image (AMI) to your AWS environment.
Note: Currently, vRealize Network Insight supports the collector deployment in AWS using AMI only for VMware SD-WAN.
The procedure and task related to EC2 instances are documented in https://docs.aws.amazon.com/efs/index.html.
- Launch your EC2 instance using the VMware provided AMI in the Amazon EC2 console. For procedure details, see Create Your EC2 Resources and Launch Your EC2 Instance topic in the Amazon Elastic File System documentation.
Note: When you Launch your EC2 instance in AWS, you must select the following:
Option Action Instance type m4.xlarge (MEDIUM BRICK) Network Select an appropriate network and subnet. Storage Default Storage. Tags As per customer Policies. Security Group Allow Outbound to 0.0.0.0/0 for port 443 (or for restricted rules, allow outbound for NI SaaS Prod FQDN for port 443). Key Select appropriate Key (SSH Login is enabled for the AMI).
- When your EC2 instance is in the running state, log in to your EC2 instance.
- Log in with the given console credentials. Run the
- Create the password for the
supportlogin. Change the password for the
consoleuser.Note: After you change the password, the network options will be skipped during setup CLI.Proxy AMI does not support the following:
- IP change
- Web Proxy Configuration.
- Enter the NTP Server and ensure that it can be reached from the VM. The services fail to start if the NTP time is out of sync.
Note: For multiple NTP servers, ensure that they are separated by commas.
- A check is made to see if the shared secret key has been configured. The collector is paired with the corresponding platform. This process can take few minutes.
- All the services are verified.
What to do next
- Make the collector you deployed in AWS as a Non-VeloCloud Site. For details, contact VMware support.