Nutanix NCP-CI-AWS Dumps

To SSH into a Controller VM (CVM) in an NC2 on AWS cluster without on-premises connectivity, the administrator needs to ensure that the security settings allow SSH access from the Jump Host. This involves editing the User Management Network Security Group to permit SSH traffic from the Jump Host IP.

Deploy Jump Host:

Ensure the Jump Host is deployed in a public subnet with an Elastic IP (EIP) assigned for external access.

Edit User Management Network Security Group:

Locate the security group associated with the user management network.

Modify the inbound rules to allow SSH (port 22) from the Jump Host ' s IP address. This ensures that the Jump Host can establish an SSH connection to the CVM.

Steps to Edit Security Group:

Navigate to the EC2 dashboard in the AWS Management Console.

Select " Security Groups " under the " Network and Security " section.

Find and select the appropriate security group.

Edit the inbound rules to add a new rule:

Type: SSH

Protocol: TCP

Port Range: 22

Source: Custom IP (enter the Jump Host ' s public IP address)

Additional Configuration:

Ensure that the CVM itself allows SSH connections and that no internal firewall rules block the traffic.

Nutanix Cloud Clusters on AWS Administration Guide

AWS Security Group Documentation

Nutanix Best Practices for Secure Access

To correctly route traffic in a hybrid environment using Flow Virtual Networking, administrators must distinguish between internal private traffic and external internet traffic. Internal traffic usingRFC 1918address ranges (10.0.0.0/8, 172.16.0.0/12, and 192.168.0.0/16) should be routed to theoverlay-external-subnet-no-nat. This ensures that traffic directed to the on-premises data center retains its original IP address for auditing and security purposes. Conversely, all other traffic (0.0.0.0/0), typically destined for the internet, should be routed to theoverlay-external-subnet-nat. This configuration allows the NAT Gateway to handle internet-bound requests while maintaining a transparent, non-NAT path for corporate internal communication.

Synchronous replication in Nutanix Cloud Clusters (NC2) on AWS requires extremely low latency, typically less than 5ms round-trip time (RTT). To achieve this, clusters must be located within the same AWS region, often within different Availability Zones or the same VPC.

Supported networking configurations for this high-speed data exchange include using standard native AWS networking on both clusters to ensure direct, low-latency communication. Additionally, a hybrid setup where one cluster utilizes native networking and the remote cluster uses Flow Virtual Networking (FVN) is supported, provided the underlying network infrastructure satisfies the latency requirements for synchronous operations. This ensures that data is written to both clusters simultaneously before an acknowledgment is sent to the application, providing zero recovery point objective (RPO).