...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
Note |
---|
This topic only applies to Armor's private cloud users who are account administrators and new to the Armor Management Portal (AMP). |
...
Expand | ||||
---|---|---|---|---|
| ||||
|
...
Expand | ||
---|---|---|
| ||
Option 1: Credit card
Option 2: ACH Bank Debit
|
...
Expand | ||
---|---|---|
| ||
|
...
Expand | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Step 1: Create an IP GroupIn the Firewall screen, each entry in the table represents a single firewall rule; however, each firewall rule can contain several IP addresses or just a single IP address. You can combine related IP addresses into a single IP Group. For example, if you want to block traffic from three separate IP address, you do not have to create three separate firewall rules. Instead, you can combine the three separate IP addresses into a single, configurable IP Group. Then, when you create a firewall rule, you can pick the newly created IP Group as your Source or Destination IP addresses.
Step 2: Create a Service GroupIn the Firewall screen, each entry in the table represents a single firewall rule; however, each firewall rule can contain several protocols (and ports). You can combine related protocols (and ports)into a Service Group. For example, if you want to create a firewall rule to block three types of traffic, you do not have to create three separate firewall rules. Instead, you can combine the three types of traffic (protocols and ports) into a single, configurable Service Group. Then, when you create a firewall rule, you can pick the newly created Service Group.
For a complete list of supported services and sub-protocol, seeReview supported services and sub-protocols. Step 3: Create a Firewall Rule
After you create a rule, Armor recommends that you place the rule in the correct order.
|
...
Expand | |||||
---|---|---|---|---|---|
| |||||
Insert excerpt | ESLP:Invite a new user (snippet) | ESLP:Invite a new user (snippet) | |||
nopanel | true |
Note |
---|
Repeat Step 8: Create An User and Assign A Role for every user you want to invite. |
title | Step 9: Enable SSL/VPN Access for Your Users |
---|
title | Step 10: Subscribe to Data Center Notifications |
---|
- In the Armor Management Portal (AMP), in the left-side navigation, click Account.
- Click Users.
- Click the plus ( + ) icon.
- Complete the First Name, Last Name, and Email Address fields.
- The email address you enter will be the username.
- Select a role for this user.
- You must assign a role to the user.
- You can assign multiple roles to the user.
- You can assign a default role (Admin, Technical, Billing).
- Admin contains every permission in AMP.
- Technical contains mostly write-only permissions.
- Billing contains mostly read-only permissions
- To learn about Roles and Permissions, see Roles and Permissions.
- Click Create User. An email will be sent to the user. After 96 hours, the sign-up link in the email will expire.
- If the link expires, you can resend the user invitation. In the Users screen, hover over the desired user, click the vertical ellipses, and then select Resend Invitation.
- If you want to remove this newly created / invited user from your account, see Remove a newly created / invited user from your account.
Note |
---|
Repeat Step 8: Create An User and Assign A Role for every user you want to invite. |
Expand | ||
---|---|---|
| ||
Before an invited user can download and install their SSL VPN, the account administrator must add the following permissions to their account:
Additionally, the account administrator must enable the account to access the SSL VPN client:
|
Expand | ||
---|---|---|
| ||
You can use Armor's StatusHub page to review the status of Armor's infrastructure, as well as other Armor services, such as the Armor Management Portal (AMP). Additionally, you can use StatusHub to receive notifications and updates regarding infrastructure outages.
|
Expand | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
Armor recommends that you configure your account to receive notifications forAccount, Billing, and Technical events.
|
...
Expand | ||
---|---|---|
| ||
An organization allows you to specify when a group of users should be added to a specific support ticket, based on the subject matter of the ticket. For instance, for a billing-related ticket, you can indicate that members of the Billing organization should be notified. When a support ticket is shared with an organization, all users within the organization will receive an initial email notification.
|
...