Page tree

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

Compare with Current View Page History

« Previous Version 21 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 account 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 

    While all instances from your public cloud account will appear in the Virtual Machines screen, you should only focus on the security status for the instances that contained the Armor agent.

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, the Cloud Connections screen 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.

Error rendering macro 'excerpt-include'

No link could be created for 'Add AWS account via Cloud Connections (snippet)'.


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 their 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 public cloud 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 that the agent is installed, but has not properly communicated (heartbeated) with Armor.
  • OK indicates that the agent is installed and has communicated (hearbeated) with Armor.
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