For invited users:

Before your account was created, your account administrator decided the proper roles and permissions for your account.

Consult with your account administrator to understand what permissions you have and how you should configure your account.

You can use this document to complete the account signup process and review high-level action items to complete.

This topic only applies to users who run:

  • Windows 2008 R2 Datacenter
  • Windows 2008 R2 Standard
  • Windows 2008 R2 Web

Before you begin, Armor recommends that you pre-installation information, including firewall rules.

To learn more, see ANYWHERE Pre-Installation.

Before you install the Armor Anywhere agent, you must remove any previously installed anti-virus software, such as Trend Micro, McAfee, etc. Afterwards, you must reboot your system. 


Step 1: Open the Account Signup email

  1. In the email from Armor, click the link.


Step 
2: Complete your security information

In this step, you will add your phone number to your account. This phone number will be used for multi-factor authentication. To complete the account signup process and to log into AMP, you must be near this phone number.

  1. Note your Armor username. 
  2. In Password and Confirm Password, create and enter an account password.
  3. Complete the Challenge Phrase and Challenge Response
  4. In Phone Number, select your country code / flag, and then enter your phone number.
  5. Click Validate to validate the phone number entered.
  6. Click Continue.

If you already coordinated with Armor to pay with a check, then you will be redirected to Armor Management Portal (AMP) login screen..


Step 3: Complete your payment information

  1. In Currency, select your currency.
  2. (Optional) If your business is tax exempt, select I'm tax exempt.
  3. For Payment Method, mark the desired payment (credit card or bank account):

Option 1: Credit Card 

Cardholder Name, Address, City, State, and Postal Code will be pre-populated with the name and contact information for the Primary Contact on the account.

  1. In Card Number, enter the credit card number.
  2. In Expiration Date, select the appropriate month and year.
  3. In CVV, enter the verification number for the credit card
  4. In Country, select the corresponding country.
  5. Click Submit.

You will be redirected to Armor Management Portal (AMP) login screen.

Option 2: ACH Bank Debit

  1. In ABA / Routing Number, enter the corresponding banking number.
  2. In Bank Account Number, enter the account number.
  3. Select the appropriate Account Type.
  4. In Bank Name, enter the name of the banking institution.
  5. In Account Holder Name, enter the name of the account holder.
  6. Click Submit.

You will be redirected to Armor Management Portal (AMP) login screen.


Step 
4: Locate the Armor Anywhere agent

For Amazon Web Services users who:

  • Use Elastic Beanstalk to run their instance's applications, and
  • Run Windows 2012 R2,

Review the following example to understand how to install the Anywhere agent. Afterwards, you can skip to the Test your connection step.

files:
  "c:\\Windows\\Temp\\armor-setup.exe":
    source: https://get.core.armor.com/latest/armor-setup.exe
commands:
  armoragentinstall:
    test: if not exist 'c:\\.armor\\opt\\armor.exe' exit 0
    command: c:\\Windows\\Temp\\armor-setup.exe /verysilent /license=AAAA1-A11AA-AA1AA-AAAAA-1AAAA
    ignoreErrors: false
    waitAfterCompletion: 5

You must replace AAAA1-A11AA-AA1AA-AAAAA-1AAA with your specific license key.


Step 5: Download and install the Armor Anywhere agent

There are three types of scripts that you can use to install the agent. 

Script type

Description

Pre-installation

You can use these scripts to verify that your environment is compatible with Armor Anywhere. These scripts will not install the agent. 

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12; Import-Module bitstransfer; start-bitstransfer -source https://get.core.armor.com/latest/armor_agent.ps1 -destination . ; .\armor_agent.ps1
Pre-installation and installation

You can use these scripts to:

  • Verify that your environment is compatible with Armor Anywhere
  • Install the agent
[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12; Import-Module bitstransfer; start-bitstransfer -source https://get.core.armor.com/latest/armor_agent.ps1 -destination . ; .\armor_agent.ps1 -license AAAA1-A11AA-AA1AA-AAAAA-1AAA




Installation

You can use these scripts to install the agent. These scripts will not verify your environment for compatibility. 

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12; Import-Module bitstransfer; start-bitstransfer -source https://get.core.armor.com/latest/armor_agent.ps1 -destination . ; .\armor_agent.ps1 -license AAAA1-A11AA-AA1AA-AAAAA-1AAA -silent

In the above scripts, replace AAAA1-A11AA-AA1AA-AAAAA-1AAA with your specific license key.


Step 6: Test your connection

After you install the agent, Armor recommends that you test the connection for each configured firewall rule.

To verify connectivity to an Armor service endpoint, use the telnet command.

The following example tests connectivity to api.armor.com over 443/tcp:

telnet 146.88.106.210 443


For Windows systems without the telnet feature installed, you can also use PowerShell:

new-object System.Net.Sockets.TcpClient('146.88.106.210', 443)


Step 
7: Review the status of the Armor Anywhere agent 


Step 8: Configure your notification preferences

Armor recommends that you configure your account to receive notifications for Account, Billing, and Technical events.

These notification preferences do not relate to support tickets.

To update your notification preferences for support tickets, see Support Tickets.

Account

You will receive a notification when:

  • A password expires in 14 days.
  • A password expires in 7 days.
  • A password expires in 24 hours.
  • A password has expired.
Billing

You will receive a notification when:

  • An invoice has posted. 
  • An invoice is past due (2, 10, 15, 25, and 30 days).
  • A payment method will soon expire (1, 15, and 30 days).

You can configure a user to become the primary billing contact for an account. This user will receive billing notifications. Additionally, this user will be listed in the Bill to field in an invoice. 

  1. In the Armor Management Portal (AMP), in the left-side navigation, click Account.
  2. Click Users
  3. Locate and hover over the desired user. 
  4. Click the vertical ellipses. 
  5. Select Set as Primary Billing Contact
  6. Click OK
Technical

You will receive a notification when:

  • A virtual machine will be deleted or downgraded.
  • CPU, disk, and memory utilization is at more than 90% for 5 minutes.
  • Ping, SSH (Linux), or RDP (Windows) fails for 5 minutes.

You can only change the notification preferences for your own account. You cannot change the notification preferences for other user accounts.

  1. In the Armor Management Portal (AMP), in the top, right corner, click the vertical ellipses.
  2. Click Settings
  3. Click Notification Preferences.
  4. Use the slider to make your desired changes. 
  5. Click Update Notification Preference to save your changes. 


Step 9: Create a role and add permissions

For Account Administrators only.

In the Armor Management Portal (AMP), roles are similar to job titles that you can create and assign to your users. You can populate these roles with certain permissions. For example, you can create an Audit role, and then you can add specific permissions that will give the assigned user permission to access audit-related features.

By default, a new administrator account contains an Admin role with all the available permissions selected. 

When you create a new user account, you must assign that user a role. You can assign a default role or create a new role. 

There are three default permissions in AMP: 

  • Admin contains every permission in AMP.
  • Technical contains mostly write-only permissions. 
  • Billing contains mostly read-only permissions.

If you want to use a default role, then you can skip to Step 8: Create a user and assign a role


Step 10: (For Account Administrators) Create a user and assign a role

Repeat Step 10: Create a user and assign a role for every user you want to invite.




Was this helpful?