The following differences exist between the commercial VMware Aria Operations for Logs offering and the VMware Aria Operations for Logs in VMware Aria Suite Cloud for US Public Sector version of the offering.
For information about user tasks, see Using VMware Aria Operations for Logs (SaaS).
The following tasks in the user guide behave differently for VMware Aria Operations for Logs in VMware Aria Suite Cloud for US Public Sector.
Deploy a Cloud Proxy
You must have an active VMware Cloud Proxy before you can use VMware Aria Operations for Logs.
- Prerequisites
-
- Verify that you have an IP address, a DNS entry, and permissions to deploy OVF templates vSphere
- Log in to vSphere and verify that you are connected to a vCenter Server system.
- Ensure that outgoing HTTPS traffic is allowed for the Cloud Proxy.
- When you use a web browser to connect to VMware Cloud Services, ensure that the computer that runs the web browser has HTTPS port 443 open to outgoing traffic with access through the firewall to:
- *.vmwareidentity.com gaz.csp-vidm-prod.com
- *.vmware.com
- When you connect to VMware Cloud Services from a data collector, ensure that the computer that the data collector is on has HTTPS port 443 open to outgoing traffic with access through the firewall to:
- Log in to VMware Aria Operations for Logs and enter your login credentials.
- Procedure
-
- Navigate to
The Install Cloud Proxy dialog box appears. Leave this dialog box open, as you will need it later.
and click . - To deploy the Cloud Proxy, click Download OVA.
- Navigate to your VMware vSphere Web Client data center and click the name of your vCenter cluster. In the drop-down menu, select Deploy OVF Template.
- In the Deploy OVF Template form, perform the following actions.
- Click Select template, then Local File. Paste in the path to the OVA Cloud Proxy file you downloaded. Click Next.
- Click Select name and location, then enter the name of your OVA file. Select the cluster where you want to install the Cloud Proxy, and click Next.
- Click Select a resource and the cluster where you want to run the Cloud Proxy, and then click Next.
- Review the details of your Cloud Proxy deployment. Notice the Size on disk text box. The location where you deploy the Cloud Proxy in the following steps must have enough space available. Click Next.
- Accept the License Agreement. Click Next.
- Click Select storage and select a datastore from the list with enough free space for the OVA file. Click Next.
- Click Select networks and select a destination network, and then click Next.
- Click Customize template and enter the required information. Do not click Next.
Note: For Root User Password, choose a unique password. It does not need to match the vCenter password.
- Return to VMware Aria Operations for Logs and collect the token key provided on the Install Cloud Proxy dialog box. Click Copy to copy the One Time Key (OTK). Use the Copy control to ensure you are copying the entire key.
Note: Token keys must be used within 24 hours and must be used for only one Cloud Proxy.
- Return to the template form and click Networking Properties. If you use DHCP in your vCenter network, do not enter any information. If you do not use DHCP, then you must provide information for each setting. Click Next.
- Click Ready to complete and review your configuration data. Click Finish.
The Cloud Proxy is installed.
- After deploying a Cloud Proxy, you must approve it to ensure that it is functional. Approving the Cloud Proxy triggers the download and installation of the required service proxies.
To approve the Cloud Proxy, do the following.
- In the Cloud Proxies page, click the Cloud Proxy.
- In the upper-right corner of the page, click Approve.
- In the Approve Cloud Proxy dialog box, the Enable Auto Upgrade for Service Proxies check box is selected, which indicates that auto-upgrade for service proxies is enabled by default. To deactivate auto-upgrade, clear the check box.
- Click Confirm.
You can modify the auto-upgrade setting later by doing the following.- In the Cloud Proxies page, click the Cloud Proxy.
- Under the Cloud Proxy details, click Manage Service Proxies Upgrade.
- If auto-upgrade is enabled, clear the Enable Auto Upgrade for Service Proxies check box to deactivate it.
- If auto-upgrade is deactivated:
- Select the Enable Auto Upgrade for Service Proxies check box to enable it.
- Select Install Upgrades Now to start installing the upgrades immediately.
Note: If you decline the Cloud Proxy, the service proxies are not downloaded. This action is not reversible and your Cloud Proxy will no longer be functional. However, declining the Cloud Proxy does not remove the Cloud Proxy VM from your vCenter Server. - Click the green arrow at the top of your page to run the Cloud Proxy.
- To verify that your Cloud Proxy is running, look under the VMs tab at the list of your virtual machines to ensure its state is Powered On.
- Return to the VMware Aria Operations for Logs Install Cloud Proxy dialog box. Wait for a success message saying a connection has been made. The installation may take several minutes.
- Navigate to
Upgrade a Cloud Proxy
- Download the upgrade bundle from downloads.vmware.com.
- Connect to the Cloud Proxy through SSH.
- Copy the upgrade bundle to the /tmp/ directory in the Cloud Proxy VM.
- Run the following command to set up an offline repository.
sh /proxy-upgrade.sh offline-repo /tmp/<update-bundle-name.tar.gz>
- Verify the offline repository setup using the following command.
sh /proxy-upgrade.sh update --check
The command takes up to five minutes to execute. If updates are available, the following output appears.Available Updates - <Version> Build <Build No.>
- Upgrade the Cloud Proxy using the following command.
sh /proxy-upgrade.sh
When the upgrade is done, the following output appears.<Date and Time> *********System updated successfully*********
Support for Public Cloud Accounts
To support the creation and use of public cloud accounts and integrations such as Amazon Web Services (AWS), Microsoft Azure, GitHub, GitLab, and so on, you must first contact VMware Support to enable additional and required security compliance criteria.