To ensure that you can reach the local NSX Manager in the event of a network failure, we recommend configuring a redundant connection such as AWS Direct Connect to with a route-based VPN as the backup, as described in Configure Direct Connect to a Private Virtual Interface for SDDC Management and Compute Network Traffic in the VMware Cloud on AWS Networking and Security guide.
After you have disabled Networking & Security tab access, a connection to the local NSX Manager over a VPN is the only way to manage your SDDC network. See Configure a VPN Connection Between Your SDDC and On-Premises Data Center in the VMware Cloud on AWS Networking and Security guide.
You must have a VPN connection to the SDDC. You must be logged into the VMC console as a user with a VMC service role of Administrator or Administrator (Delete Restricted). If you need to re-enable access to the Networking & Security tab, contact VMware Support. After you verify that you can access NSX Manager, you can proceed to prepare the SDDC for compliance hardening by disabling access to the Networking & Security tab. Access to the Networking & Security tab must be disabled before you begin a compliance audit, and must remain disabled the duration of the audited period.īefore you disable access to the Networking & Security tab, you'll use it to create a VPN connection to your on-premises data center and a management gateway firewall rule that allows you to access the local NSX Manager over that VPN.
To maintain compliance, you must manage your SDDC networks using only the local NSX Manager, which has an authentication framework that meets compliance hardening requirements. Any access to an SDDC using the Networking & Security tab renders the SDDC non-compliant. Access controls on the VMC Console Networking & Security tab are not appropriate for a compliance-hardened SDDC.
0 kommentar(er)
