Which statement is true regarding AWS account requirements?
To create a CloudFormation stack, the AWSCloudFormationFullAccess role is required.
This role grants the necessary permissions to create, update, and delete CloudFormation stacks, which are essential for deploying and managing AWS infrastructure using CloudFormation templates.
CloudFormation stacks are often used to automate the deployment of complex infrastructures, including those required for NC2 on AWS.
Proper permissions ensure that the deployment process is seamless and adheres to the security and operational policies of the organization.
Reference: Refer to the AWS IAM documentation for details on the AWSCloudFormationFullAccess role and Nutanix documentation on prerequisites for deploying NC2 on AWS.
Which entity should be contacted for cloud hardware supported (EC2 instances, VPC, etc) related to NC2?
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.
What is the purpose of an organization in the NC2 console?
In the NC2 console, an organization is used to segregate clusters based on specific requirements. This segregation allows administrators to manage clusters more effectively by grouping them according to business units, projects, or other criteria. This organizational structure helps in maintaining clear boundaries and applying specific policies or permissions to different clusters within the same NC2 environment.
An administrator has deployed an NC2 cluster in AWS.
The following configuration decisions were made:
Created a new VPC from the NC2 console as part of the deployment
Selected the Public option for prism access policy
Host type selected was i13en,metal
The administrator now has a goal of provision public internet access to a user VM (UVM),web-1, on the Nutanix cluster. The admin can access Prism Element via the public DNS of the Auto-created load balancer.
The administrator tries to create another network load balancer for the web server access. After creating the load balancer and registering web-1's IP address as a target, the administrator finds that the health check for the VM target is failing and the DNS returns as NOT Found message in the browser.
Why is the issue happening?
For a VM to be accessible over the internet through a load balancer, the VM itself must have a public IP address.
In this case, the health check for the VM target is failing and the DNS returns a 'NOT Found' message because web-1 does not have a public IP assigned.
Without a public IP, the load balancer cannot route traffic to web-1 from the internet.
Assigning a public IP to web-1 ensures that the VM can be accessed via the load balancer, resolving the connectivity issue.
Reference: Refer to the AWS documentation on network load balancers and public IP assignments, and Nutanix documentation on VM network configurations.
An administrator planned to create a new NC2 cluster and chose the existing AWS VPC infrastructure in the workflow. The administrator need two private subnets to complete the configuration.
What are these two private subnets used for..
The requirement for two private subnets in the NC2 cluster configuration workflow serves the same purposes:
One subnet is designated for user VMs, ensuring user workloads are separated from management operations.
The other subnet is designated for cluster management, maintaining the integrity and security of management processes and internal communications.
