To establish full connectivity between the company's on-premises datacenter and the AWS cloud, the following AWS offerings will satisfy this requirement:
AWS VPN: This service allows you to create a secure connection between your on-premises network or other remote network and your AWS VPC using an IPsec VPN tunnel. It is suitable for low to moderate bandwidth requirements and provides secure, encrypted connections.
Direct Connect: AWS Direct Connect is a dedicated network connection from your premises to AWS. It provides a private, high-bandwidth, low-latency connection which is ideal for high-throughput applications and workloads that need consistent network performance.
Reference:
AWS VPN Documentation
AWS Direct Connect Documentation

When creating a new NC2 cluster using an existing AWS VPC infrastructure, two private subnets are needed.
These subnets are used as follows:
* One private subnet for user VMs, which houses the virtual machines that users interact with.
* Another private subnet for cluster management, which is used for internal cluster operations and management tasks, ensuring that management traffic is isolated from user traffic for security and performance reasons.
Nutanix Support and Insights
Nutanix Cloud Clusters on AWS Administration

For issues related to cloud hardware support such as EC2 instances, VPC, etc., the public cloud vendor (AWS in this case) should be contacted. AWS provides support and documentation for their infrastructure and services, ensuring that users can get assistance for any hardware or cloud-specific queries.
Nutanix Support and Insights

The maximum number of nodes supported in an NC2 cluster on AWS is 24 nodes. This limit ensures optimal performance and manageability within the AWS infrastructure while leveraging the benefits of the Nutanix architecture.
Reference:
Nutanix Clusters on AWS Deployment Guide
Nutanix Support & Insights

To ensure that NC2 VMs can access AWS resources without traversing the internet, the administrator can use AWS VPC Peering and Interface Endpoints. Both methods ensure that traffic stays within the AWS network, maintaining security and efficiency.
* Interface Endpoint:
* Interface Endpoints allow you to privately connect your VPC to supported AWS services. They use AWS PrivateLink to route traffic directly to services within the AWS network, bypassing the public internet.
* Steps:
* Create an interface endpoint for the required service in the AWS VPC console.
* Ensure the security groups and route tables are configured to allow traffic to the interface endpoint.
* VPC Peering:
* VPC Peering allows the routing of traffic between VPCs using private IP addresses, without the need for internet gateways, NAT devices, or VPN connections.
* Steps:
* Create a VPC peering connection between the VPCs.
* Update the route tables to direct traffic between the peered VPCs.
* Ensure security group rules allow the necessary traffic between VPCs.
AWS VPC Peering Documentation
AWS Interface Endpoint Documentation
Nutanix Cloud Clusters on AWS Administration Guide