Additional attach network interfaces not displayed and no gateway found - CAS > AWS Deployment

Products

• Content Analysis Software

Issue/Introduction

null(config)# show full-configuration interface
interface 0:0
  enable
 speed  auto
 duplex auto
 mtu-size 1500
!

null(config)# show full-configuration ip default-gateway
% No entries found.

Environment

Release : 3.1.3.0

Resolution

Having investigated the technical guidance for deploying Symantec CAS on AWS, with the link to the Tech. Article added below,  from "completing the prerequisite tasks" to "importing and registering an AMI", to "deploying and verifying the instance", to "installing the license", and "disassociating user data from the instance", none of these steps involve setting up/configuring the network interfaces and gateway.

https://techdocs.broadcom.com/us/en/symantec-security-software/web-and-network-security/content-analysis/3-1/about-cas-aws.html

Howbeit, when creating the Content Analysis AWS Instance, step 3 requires that the "virtual private cloud  (VPC) be selected, for network, and the "public subnet" be selected, for subnet.

Ref. doc.: https://techdocs.broadcom.com/us/en/symantec-security-software/web-and-network-security/content-analysis/3-1/aws-requirements/aws-create-instance.html

Going through the AWS "Best practices for configuring network interfaces" guide, in one of the lines, it's stated that a warm or hot attach of an additional network interface might require you to manually bring up the second interface, configure the private IPv4 address, and modify the route table accordingly. Instances running Amazon Linux or Windows Server automatically recognize the warm or hot attach and configure themselves.

Consequently, we recommend to go through the AWS best practices guide for configuring network interfaces and execute as guided, to have the additional network interfaces properly setup. 

Ref. doc.: https://docs.aws.amazon.com/AWSEC2/latest/WindowsGuide/best-practices-for-configuring-network-interfaces.html