Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Prerequisites:

  • One of the following

    Oses

    OSes (https://support.cloudamize.com/kb/supported-operating-systems-and-chipsets#SupportedOperatingSystemsandChipsets-ListofSupportedLinuxOSs):

    • Red Hat Enterprise Linux Server release 7.0 or higher

    • Oracle Linux 6.5 or higher

    • Ubuntu 16.04 or higher

    • CentOS release 7 or higher

    • Debian GNU/Linux 8.0 or higher

    • Amazon Linux AMI release 2013.03 or higher

    • Fedora release 12 or higher

    • Suse Linux 11 or higher

  • supported version of OpenSSL

  • Root and/or Wheel Group access

  • 350 MB persistent storage

  • The Install script requires wget to retrieve content

    ,

    and curl to test/verify access to our data collection servers.

  • Open firewall port TCP 443 to our data collection

    servers in the US at IP address 104.197.11.97 or in the EU at 35.198.133.35 over port 443,

    servers at am.cloudamize.com for US infrastructure, am-de.cloudamize.com for EU infrastructure, or am-ae.cloudamize.com for UAE infrastructure either directly or through a corporate proxy.

    • If your system locally caches DNS resolution, you may need to resolve am.cloudamize.com to 35.171.170.26 or am-de.cloudamize.com to 18.194.12.63 to allow egress traffic. This will not be the address traffic will return from, so this cannot be used as a firewall exception alone. This feature is not currently available for our UAE collection endpoint.

Note: The Linux agent/agentless approach requires a user with root permissions to get PID-to-network mapping, certain hardware details, and data on logical/physical disk volumes. Become a root user either through "sudo -s" or "su", ; most systems use sudo.  

Procedure:

Launch Login to your Cloudamize console here, or launch the application from your Partner Dashboard or login directly here. Open if you have one.

Navigate to the Settings page by clicking the Edit Configuration button. If your assessment is already running, click your username in the upper right-hand corner and select select Settings from the dropdown menu. Navigate to Agent Setup > Assess and select the Linux tab. 

Note: the commands below represent our US infrastructure. If you are using use our EU infrastructure, copy and paste the commands directly from your assessment. 

Step 1:  Export your customer key.

Code Block
export CLOUDAMIZE_CUSTOMER_KEY=<YOUR CUSTOMER KEY>

Step 2:  Execute the following command to install an agent.command listed in the assessment portal, eg:

Code Block
$ sh <(curl 

...

'https://

...

am.cloudamize.com/cxf/

...

downloadFileV3?custkey=<YOUR CUSTOMER KEY>&filename=installCloudamizeAgentV2.sh

...

If FQDN resolution is not permitted use the command below.

sh <(curl -s -k https://104.197.11.97/cxf/downloadFile/installCloudamizeAgentV2.sh)

...

' -L)

...

If you want to route the data through your own proxy server, click the checkbox as shown in the image below

...

and use the following commands listed in console.cloudamize.com assessments have the command listed in the portal.

...

Linux Install with Proxy

...

Linux Install with Authenticated Proxy

...

Deploy from Central Repository:

Installation of Agent

The customer should decide whether to use rpm or deb, but in general, rpms are used by Red Hat, CentOS, SUSE, and Oracle Linux, and deb is used by Debian and Ubuntu.

Download:

  • US:

    • %> sh <(curl

...

    • -

...

    • X POST https://

...

    • am.

...

    • cloudamize.com

...

    • /cxf/downloadFileV3 -H 'content-type: multipart/form-data' -F custkey=<custkey> -F filename=installCloudamizeAgentV2.sh)

  • EU:

    • %> sh <(curl -X POST https://

...

    • am-de.cloudamize.com/cxf/

...

    • downloadFileV3 -H 'content-type: multipart/form-data' -F custkey=<custkey> -F filename=installCloudamizeAgentV2.sh)

...

linux-proxy.pngImage Removed

If you want to use your own proxy server and the server requires authentication, click the designated checkbox and use the following, updated command.

...

  • UAE:

    • %> sh <(curl

...

    • -

...

    • X POST https://

...

    • am-ae.

...

    • cloudamize.com

...

    • /cxf/downloadFileV3 -H 'content-type: multipart/form-data' -F custkey=<custkey> -F filename=installCloudamizeAgentV2.sh)

Install:

  • US:

    • RPM:

      • curl -X POST https://

...

      • am.cloudamize.com/cxf/

...

linux-authentication.PNGImage Removed

Deploy from Central Repository:

Installation of Agent

The customer should decide rpm/deb, but in general, rpms are used by Red Hat, CentOS, SuSE, Oracle Linux and deb is used by Debian and Ubuntu.

  • RPM URL: 
    • https://agentmanager1
      • downloadFileV3 -H 'content-type: multipart/form-data' -F custkey=<custkey> -F filename=cloudamize_agent.rpm -o cloudamize_agent.rpm

    • DEB:

      • curl -X POST https://am.cloudamize.com/cxf/downloadFileV3 -H 'content-type: multipart/form-data' -F custkey=<custkey> -F filename=cloudamize_agent.deb -o cloudamize_agent.deb

    • TGZ:

      • curl -X POST https://am.cloudamize.com/cxf/

      downloadFile/
      • downloadFileV3 -H 'content-type: multipart/form-data' -F custkey=<custkey> -F filename=cloudamize_agent.tgz -o cloudamize_agent.

      rpm (US)
      • tgz

  • EU:

    • RPM:

      • curl -X POST https://

      agentmanager
      • am-de.cloudamize.com/cxf/

      downloadFile/
      • downloadFileV3 -H 'content-type: multipart/form-data' -F custkey=<custkey> -F filename=cloudamize_agent.rpm

      (EU)
    RPM Install: CLOUDAMIZE_CUSTOMER_KEY=xxxx rpm -i
      • -o cloudamize_agent.rpm

    • DEB

    URL
    • :

      • curl -X POST https://

      agentmanager1
      • am-de.cloudamize.com/cxf/

      downloadFile/
      • downloadFileV3 -H 'content-type: multipart/form-data' -F custkey=<custkey> -F filename=cloudamize_agent.deb -o cloudamize_agent.deb

    • TGZ:

      • curl -X POST https://

      agentmanager
      • am-de.cloudamize.com/cxf/

      downloadFile/
      • downloadFileV3 -H 'content-type: multipart/form-data' -F custkey=<custkey> -F filename=cloudamize_agent.

      deb (EU)
    DEB Install: CLOUDAMIZE_CUSTOMER_KEY=xxxx dpkg -i
      • tgz -o cloudamize_agent.

    debTGZ URL
      • tgz

  • UAE:

    • RPM:

      • curl -X POST https://

      agentmanager1
      • am-ae.cloudamize.com/cxf/

      downloadFile/
      • downloadFileV3 -H 'content-type: multipart/form-data' -F custkey=<custkey> -F filename=cloudamize_agent.rpm -o cloudamize_agent.

      tgz (US)
      • rpm

    • DEB:

      • curl -X POST https://

      agentmanager
      • am-

      de
      • ae.cloudamize.com/cxf/

      downloadFile/
      • downloadFileV3 -H 'content-type: multipart/form-data' -F custkey=<custkey> -F filename=cloudamize_agent.

      tgz (EU)

TGZ Install:

...

      • deb -o cloudamize_agent.

...

      • deb

    • TGZ:

      • curl -X POST https://am-ae.cloudamize.com/cxf/downloadFileV3 -H 'content-type: multipart/form-data' -F custkey=<custkey> -F filename=cloudamize_agent.tgz -o cloudamize_agent.tgz

Note: If for some reason environment variables cannot be used during the installinstallation, the customer can configure later by running /usr/local/cloudamize/bin/configure.sh

...

The agent can be configured while installed or after it is installed. The following environment variables are can be used to configure. If they the variables are set during install, installation they will be used to configure. Otherwise, the customer must run /usr/local/cloudamize/bin/configure.sh

Environment variables can be set using the “export” command in bash, or when running a command. Placement of env set is important when running during command. Note, sudo usually clears env variables.

  • export CLOUDAMIZE_CUSTOMER_KEY=xxxx
    dpkg -i cloudamize_agent.deb

  • CLOUDAMIZE_CUSTOMER_KEY=xxxx dpkg -i cloudamize_agent.deb

  • sudo CLOUDAMIZE_CUSTOMER_KEY=xxxx dpkg -i cloudamize_agent.deb

  • curl https://

    agentmanager1

    am.cloudamize.com/cxf/downloadFile/installCloudamizeAgentV2.sh | sudo CLOUDAMIZE_CUSTOMER_KEY=xxxx bash

  • CLOUDAMIZE_CUSTOMER_KEY=xxxx /usr/local/cloudamize/bin/configure.sh

Available options are:

Env Variable

Parameter*

Description

CLOUDAMIZE_CUSTOMER_KEY

--customer-key

REQUIRED. The customer key to register with.

PROXY_SERVER

--proxy-server

Customer proxy server address to use with curl.

PROXY_PORT

--proxy-port

Customer proxy port.

PROXY_UNAME

--proxy-user

Customer proxy user name.

PROXY_PSWD

--proxy-pass

Customer proxy user password.

 

Click here for steps to troubleshoot installation issues. 

Click here for instructions on how to uninstall the linux Linux agents.