To deploy NC2 in AWS using an existing VPC, the following AWS resources should be configured beforehand:
* NAT Gateway: This allows instances in the private subnet to connect to the internet or other AWS services, while preventing the internet from initiating connections with those instances.
* Public and Private Subnets: These are necessary to segregate the network traffic. Public subnets provide a direct route to the internet gateway, while private subnets are used for internal resources that do not need direct access to the internet.
Nutanix Cloud Clusters on AWS Deployment Guide
Nutanix Support and Insights

The exhibit shows two cloud accounts, one for Azure and one for AWS, with their statuses indicated. The AWS cloud account status is marked as "U" (which likely stands for "Unavailable" or "Unreachable"). This indicates that the AWS cloud account configuration is not properly connected or accessible.
Status Check:
The AWS cloud account is marked with an "U" status, meaning it is not active or accessible.
This status prevents the creation of an NC2 cluster because the necessary cloud resources cannot be allocated or managed without a proper connection.
Action:
The best course of action is to create a new cloud account in the organization. This involves setting up the cloud account details correctly and ensuring it is properly configured to communicate with Nutanix and AWS.
Steps to Create a New Cloud Account:
Log in to the Nutanix console.
Navigate to the "Organizations" section.
Select "Add Cloud Account" and provide the required AWS credentials and permissions.
Ensure the new cloud account is active and correctly configured.
Reference:
Nutanix Cloud Clusters on AWS Administration Guide
Nutanix Best Practices for Cloud Account Management

When deploying Nutanix Cloud Clusters (NC2) on AWS, administrators have two primary workflows:
allowing the NC2 portal to automate resource creation or using existing resources. The " Bring Your Own " (BYO) model is characterized by the requirement that the administrator manually prepares the underlying AWS infrastructure before initiating the Nutanix cluster deployment. Specifically, the actions ofcreating an AWS VPCandcreating the required subnets(such as management and User VM subnets) are exclusive to the BYO workflow. In the automated " Nutanix-managed " workflow, the NC2 portal uses CloudFormation to provision these network resources automatically. While setting up IAM users and permissions is necessary for both models to allow the NC2 console to interact with the AWS API, the pre-existence of the VPC and subnet architecture is the defining prerequisite for a BYO deployment.

* When selecting the NC2 subscription plan from the Nutanix Billing portal, the available options include:
* Pay-as-you-Go (PayG): A flexible payment option where users are billed based on their actual usage, providing cost efficiency for variable workloads.
* Bring your own License (BYOL): Allows users to utilize existing Nutanix licenses they have purchased, offering a cost-effective way to leverage existing investments in Nutanix software.
Refer to the Nutanix billing and subscription documentation for detailed descriptions of subscription plans and their benefits.

The alert indicates a potential issue with the VPC/Subnet settings, preventing the cluster nodes from contacting Nutanix services.
To resolve this, the administrator needs to ensure that the subnet 10.0.1.0/24, which is assigned for Bare metal hosts, has an outbound Internet connection.
This connection is necessary for the cluster nodes to communicate with external Nutanix services for updates, license validation, and other essential operations.
Verify that there are appropriate route tables and security group rules allowing outbound traffic to the Internet from the 10.0.1.0/24 subnet.
Ensure that there is either an Internet Gateway (IGW) attached to the VPC or a NAT Gateway configured if using private subnets.
Reference:
Refer to the Nutanix documentation and AWS VPC configuration guides to ensure proper Internet connectivity and routing setups.