Deploy Gigamon Insights on AWS
This section provides the steps for deploying Gigamon Insights on AWS.
To subscribe to Gigamon Insights, perform the following steps:
|
1.
|
Log in to your AWS account. |
|
3.
|
In the AWS Marketplace console, go to AWS Marketplace > Discover products. |
|
4.
|
In the Search field, type "Gigamon" and select Gigamon Insights product. |
|
5.
|
Select View Purchase Options. The terms and conditions page is displayed. |
|
6.
|
Review the Terms and Conditions and select Accept Terms. |
|
7.
|
Review the summary and then select Launch your software. |
|
8.
|
In the Launch Gigamon Insights page, enter the following details for your deployment: |
|
a.
|
Select Launch method as Launch from EC2 console. |
|
b.
|
Auto-populates the latest version in the Software Version field. |
|
c.
|
Choose your deployment Region. |
|
d.
|
Click Launch from EC2 to launch. |
|
9.
|
In the Launch an instance page, perform the following: |
|
b.
|
Select your preferred Key Pair for secure access to the instance. |
|
c.
|
From the VPC Settings drop-down list, select the VPC for deploying Gigamon Insights. |
|
d.
|
[Optional] Enable the Auto-assign Public IP if you plan to access Gigamon Insights over the internet. |
|
e.
|
In the Subnet Settings, select your desired Subnet. |
|
f.
|
In the Configure Storage, ensure that it is: |
|
•
|
100GB gp2 Root volume, Not encrypted |
|
•
|
40GB gp2 EBS volume, Not encrypted |
|
g.
|
In the Security Group Settings, configure the security group to match your access and permissions needs. For details, refer to Security Group. |
In Inbound security group rules, add the following:
|
•
|
SSH access: Select Type as SSH to allow traffic using SSH. This is required to generate the API key. |
|
•
|
HTTPS access: Select Type as HTTPS, Port range: 443 and Source as Anywhere. This is to allow HTTPS traffic from the internet which is used for communication between GigaVUE‑FM and Gigamon Insights). |
|
•
|
HTTP access: Select Type as HTTP, Port Range as 80 and Source as Anywhere. GigaVUE‑FM sends http request to Gigamon Insights for verification. |
|
h.
|
In the user data, you can upload the YAML file or copy the following format to create your own YAML file: |
Copy
#cloud-config
write_files:
- path: /etc/fm.conf
permissions: '0600'
owner: root:root
content: |
FM_IP=<IP address of the GigaVUE-FM>
FM_BEARER_TOKEN=<API token generated in GigaVUE‑FM>
PREFER_PUBLIC_IP=true
|
i.
|
Enter the following mandatory deployment properties: |
|
•
|
FM_IP: IP address or FQDN of the GigaVUE‑FM instance. |
|
•
|
PREFER_PUBLIC_IP: Set to true only if Gigamon Insights must register with GigaVUE‑FM using its public or elastic IP address (retrieved through the instance metadata service). If omitted, Gigamon Insights uses its private IP address by default. |
|
j.
|
Upload the YAML file and the YAML template populate values in the User Defaults. |
|
k.
|
Review the pre-populated default values for Gigamon Insights configuration. |
|
l.
|
If there are multiple LLM models defined in the YAML file, use the dropdown to select the appropriate service or model. |
|
m.
|
Click Save to apply the configuration. |
What to do next
Refer to Gigamon Insights Post Deployment Configurations in GigaVUE‑FM.