Page tree

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

Compare with Current View Page History

« Previous Version 17 Next »




In This Document 


Was this document useful? 
Your Rating:
Results:
1 Star2 Star3 Star4 Star5 Star
1 rates


Have a suggestion for the Armor Knowledge Base? Send a message to kb@armor.com.



Overview

You can use the Cloud Connections screen to sync your public cloud environment into the Armor Management Portal (AMP). Afterwards, you can use AMP to:

  • Collect and store logs with the Log Depot add-on product
  • View the security status of your instance in the Virtual Machines screen

The Cloud Connections screen displays the public cloud accounts you have synced. 

ColumnDescription
Account NameA descriptive name for your account
ProviderThe public cloud provider
Account ID

The ID for your public cloud account

Currently, this version only supports Amazon Web Services (AWS).

You can use this screen to collect CloudTrail logs and EC2 instance logs.


Add an AWS public cloud account 

Before you begin, to collect CloudTrail logs, you must have the Log Depot add-on product enabled.

To learn how to enable Log Depot, see Log Depot.

You can use the Cloud Connections screen to sync your public cloud environment into the Armor Management Portal (AMP).

In this section, you will need to access your AWS console to complete the configuration process. 

Armor will generate an External ID for every new Cloud Connection account. As result, an incomplete cloud connection account will be listed in the table as (Pending Connection). You can click this entry in order to continue with the cloud connection creation process.

  1. In the Armor Management Portal (AMP), in the left-side navigation, click Account.
  2. Click Cloud Connections.
  3. Click the green plus ( + ) icon. 
  4. In Account Name, enter a descriptive name. 
  5. In Description, enter a short description. 
  6. In Services, select the data type to collect. 
    • To collect CloudTrail logs, you must have the Log Depot add-on product enabled. To learn how to enable Log Depot, see Log Depot.
  7. In IAM Role, the External ID and Armor's AWS Account Number fields are pre-populated. 
  8. Copy the External ID. You will need this information at a later step. 
    • Armor will generate an External ID for every new Cloud Connection. 
    • Although the previous fields were already populated, you need to set up an AWS IAM Role for Armor. 
  9. Access the IAM console for AWS. 
  10. In the left-side navigation, click Roles
  11. Click Create new role
  12. Mark Role for Cross-Account Access
  13. Click Select for Allow IAM users from a 3rd party AWS account to access this account
  14. In Account ID, enter 242113071096
  15. In External ID, paste the External ID you copied earlier from the Armor Management Portal (AMP). 
  16. Make sure Require MFA is not marked. 
  17. Click Next Step
  18. Mark the SecurityAudit policy. 
  19. Click Next Step
  20. In Role name, enter a descriptive name. 
  21. In Role description, enter a useful description. 
  22. Click Create role
  23. Click the newly created role. 
  24. Copy the Role ARN information. 
  25. Return to the Cloud Connections screen in AMP. 
  26. Paste the Role ARN information into the IAM Role ARN field. 
  27. Click Save
    • Once the newly added cloud connections begins to gather data, the instance will appear in the Virtual Machines screen. 

View your public cloud instances

After you add your public cloud account into the Armor Management Portal (AMP), you can view the corresponding instances (and security status) in the Virtual Machines screen. 

The Cloud Connection screen simply lists the synced public cloud account; the Virtual Machines screen lists all the instances listed in that account. 
  1. In the Armor Management Portal (AMP), in the left-side navigation, click Infrastructure.
  2. Click Virtual Machines
ColumnDescription
NameThe name of the instance from your public cloud account
TypeThe type of instance, specific to the offerings offered by your public cloud provider, such as en EC2 instance for AWS
ProviderThe public cloud provider for the instance
OS

The operating system associated with the instance

(For AWS, the associated AMI is listed)

Date CreatedThe date the instance was created in your public cloud account
Security GroupFor AWS instances only
KeypairFor AWS instances only
State

The security status of the instance, in relation to the installed agent. There are three states:

  • Unprotected indicates the agent is not installed in the instance
  • Needs Attention indicates the agent is installed, but has not properly communicated (heartbeated) with Armor.
  • OK indicates the agent is installed and has communicated (hearbeated) with Armor.

Was previously known as the power status.

PowerThe power status of the instance, either powered on (green) or powered off (red)



Troubleshooting Cloud Connections screen

If you do not see any data in the Cloud Connections screen, consider that:

  • The selected date range does not contain any data.
    • Select a difference date range. 
  • You do not have permission to view log data.
    • You must have the            permission enabled to view log data. Contact your account administrator to enable this permission. To learn how to update you permissions, see Roles and Permissions



  • You did not order the Log Depot add-on product. 
  • You did not properly sync Log Depot to collect your log files. 
  • The selected date range does not contain any data.
  • You do not have permission to view log data.
    • You must have the Write LogManagement permission enabled to access the Log Search section. Contact your account administrator to enable this permission. To learn how to update you permissions, see Roles and Permissions


update the virtual machine screen for new colums


This is in the VM page,

Date created “ when your AWS feature was created inAWS

Security groups from AWS

 

Update VM page; new columns for both complete and anywhere

Ellipses includes AWS name