Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 27 Next »

Create A New Connector

  1. In the Armor Management Portal (AMP), in the left-side navigation, click Reports under Compliance.

  2. Click Connectors.

  3. Click the New Connector button.

    1. The New Connector form will slide into view from the right side of the screen.

  4. Click the icon of the appropriate Cloud provider.

    1. Amazon Web Services

    2. Google

    3. Microsoft Azure

  5. Complete the form by providing the required information.

    1. The New Connector form is dynamic. Form fields will change relative to the Cloud provider chosen. See below for specifics on how to configure the connection in the relevant provider.

    2. Add Run Frequency Value. Run Frequency for a connector decides the rate at which the connector should poll the cloud provider and fetch the data, specified in minutes. Recommended value is 240 minutes. The minimum value it can take is 60 minutes.

  6. Click the Add Connector button.


Create a Connector in AWS, GCP, or Azure

 Amazon Web Services


 Google Cloud Platform


 Microsoft Azure



Offline Connectors

If a connector is showing offline, please follow troubleshooting steps in the Troubleshooting section of this documentation, and do not delete the connector and add it back in an attempt to get it to connect.

Refreshing reports can be done from the Overview tab as documented here.


Troubleshooting A Connector

Connectors have four states they can be in:

  • Offline

  • Online

  • Pending

  • Refreshing

If a connector is in the offline or pending state (if it's a new connector allow up to 15 minutes for it to become online) the following can be done:

  1. Go to the Connectors tab of the Compliance page.

  2. Find the connector that is offline or pending.

  3. Click on the three dots.

  4. Select Refresh.

  5. The state will update to show Refreshing.

  6. If after refreshing the connector the state is still showing offline:

    1. Open a ticket with support for further troubleshooting.

If a connector is in a Regions Discovered state and not fetching information about a VM, make sure you have at least 1 VM in your cloud account.

  • If your account has at least one EC2 instance, CSPM will authenticate and complete region discovery.
  • State will turn to Success only after fetching information for at least one VM from any of the regions discovered.




Was this helpful?


  • No labels