نشر Wallarm OOB من صورة أمازون¶

توفر هذه المقالة التعليمات لنشر Wallarm OOB على AWS باستخدام الصورة الرسمية لآلة أمازون (AMI). الحل الموصوف هنا مصمم لتحليل حركة المرور المعكوسة بواسطة الويب أو خادم الوكيل.

حالات الاستخدام¶

Among all supported Wallarm deployment options, AMI is recommended for Wallarm deployment in these use cases:

Your existing infrastructure resides on AWS.
You aim to deploy a security solution as a separate cloud instance, rather than installing it directly on frontend systems like NGINX.

Requirements¶

An AWS account
Understanding of AWS EC2, Security Groups
Any AWS region of your choice, there are no specific restrictions on the region for the Wallarm node deployment

Wallarm supports both single availability zone (AZ) and multi availability zone deployments. In multi-AZ setups, Wallarm Nodes can be launched in separate availability zones and placed behind a Load Balancer for high availability.
Access to the account with the Administrator role in Wallarm Console for the US Cloud or EU Cloud
Access to https://us1.api.wallarm.com:444 for working with US Wallarm Cloud or to https://api.wallarm.com:444 for working with EU Wallarm Cloud. If access can be configured only via the proxy server, then use the instructions
Access to the IP addresses below for downloading updates to attack detection rules and [API specifications][api-spec-enforcement-docs], as well as retrieving precise IPs for your [allowlisted, denylisted, or graylisted][ip-lists-docs] countries, regions, or data centers
US CloudEU Cloud
34.96.64.17 34.110.183.149 35.235.66.155 34.102.90.100 34.94.156.115 35.235.115.105
34.160.38.183 34.144.227.90 34.90.110.226
Executing all commands on a Wallarm instance as a superuser (e.g. root)

1. Create a pair of SSH keys in AWS¶

During the deploying process, you will need to connect to the virtual machine via SSH. Amazon EC2 allows creating a named pair of public and private SSH keys that can be used to connect to the instance.

To create a key pair:

Navigate to the Key pairs tab on the Amazon EC2 dashboard.
Click the Create Key Pair button.
Enter a key pair name and click the Create button.

A private SSH key in PEM format will automatically start to download. Save the key to connect to the created instance in the future.

To see detailed information about creating SSH keys, proceed to the AWS documentation.

2. Create a Security Group¶

A Security Group defines allowed and forbidden incoming and outgoing connections for virtual machines. The final list of connections depends on the protected application (e.g., allowing all of the incoming connections to the TCP/80 and TCP/443 ports).

The Wallarm AMI is designed to operate with a minimal set of permissions. When deploying the instance, we recommend assigning an IAM role and configuring security groups based on the principle of least privilege, granting only the access required for the node's operation to align with AWS security best practices.

To create a security group for the filtering node:

Navigate to the Security Groups tab on the Amazon EC2 dashboard and click the Create Security Group button.
Enter a security group name and an optional description into the dialog window that appears.
Select the required VPC.
Configure incoming and outgoing connections rules on the Inbound and Outbound tabs.
Click the Create button to create the security group.

Rules for outgoing connections from the security group

When creating a security group, all of the outgoing connections are allowed by default. If you restrict outgoing connections from the filtering node, make sure that it is granted access to a Wallarm API server. The choice of a Wallarm API server depends on the Wallarm Cloud you are using:

If you are using the US Cloud, your node needs to be granted access to us1.api.wallarm.com.
If you are using the EU Cloud, your node needs to be granted access to api.wallarm.com.

The filtering node requires access to a Wallarm API server for proper operation.

To see detailed information about creating a security group, proceed to the AWS documentation.

3. Launch a Wallarm node instance¶

To launch an instance with the Wallarm filtering node, proceed to this link and subscribe to the filtering node.

When creating an instance, you need to specify the previously created security group as follows:

While working with the Launch Instance Wizard, proceed to the 6. Configure Security Group instance launch step by clicking the corresponding tab.
Choose the Select an existing security group option in the Assign a security group setting.
Select the security group from the list that appears.

After specifying all of the required instance settings, click the Review and Launch button, make sure that instance is configured correctly, and click the Launch button.

In the window that appears, specify the previously created key pair by performing the following actions:

In the first drop-down list, select the Choose an existing key pair option.
In the second drop-down list, select the name of the key pair.
Make sure you have access to the private key in PEM format from the key pair you specified in the second drop-down list and tick the checkbox to confirm this.
Click the Launch Instances button.

The instance will launch with the preinstalled filtering node.

To see detailed information about launching instances in AWS, proceed to the AWS documentation.

4. Connect to the filtering node instance via SSH¶

To see detailed information about ways to connect to an instance via SSH, proceed to the AWS documentation.

You need to use the admin username to connect to the instance.

Using the key to connect via SSH

Use the private key in PEM format that you created earlier to connect to the instance via SSH. This must be the private key from the SSH key pair that you specified when creating an instance.

5. Generate a token to connect an instance to the Wallarm Cloud¶

The local Wallarm filtering node needs to connect with the Wallarm Cloud using a Wallarm token of the appropriate type. An API token allows you to create a node group in the Wallarm Console UI, which helps in organizing your node instances effectively.

Generate a token as follows:

API tokenNode token

Open Wallarm Console → Settings → API tokens in the US Cloud or EU Cloud.
Find or create API token with the Node deployment/Deployment usage type.
Copy this token.

Open Wallarm Console → Nodes in the US Cloud or EU Cloud.
Do one of the following:
- Create the node of the Wallarm node type and copy the generated token.
- Use existing node group - copy token using node's menu → Copy token.

6. الاتصال بالنسخة السحابية من Wallarm¶

يتصل عقدة النسخة السحابية بالسحابة من Wallarm عبر السكربت cloud-init.py. يقوم هذا السكريبت بتسجيل العقدة مع السحابة من Wallarm باستخدام الرمز المقدم، ويعمل على تحديدها عالميًا إلى وضع المراقبة، ويقوم بتعيين الأوامر wallarm_force في كتلة location / في NGINX لتحليل نسخ حركة المرور المعكوسة فقط. إعادة تشغيل NGINX تنهي الإعداد.

قم بتشغيل السكريبت cloud-init.py على النسخة المنشأة من الصورة السحابية كما يلي:

US CloudEU Cloud

sudo env WALLARM_LABELS='group=<GROUP>' /opt/wallarm/usr/share/wallarm-common/cloud-init.py -t <TOKEN> -m monitoring -p mirror -H us1.api.wallarm.com

sudo env WALLARM_LABELS='group=<GROUP>' /opt/wallarm/usr/share/wallarm-common/cloud-init.py -t <TOKEN> -m monitoring -p mirror

WALLARM_LABELS='group=<GROUP>' يحدد اسم مجموعة العقدة (موجودة، أو، إذا لم تكن موجودة، سيتم إنشاؤها). يتم تطبيقه فقط إذا كان يستخدم رمز API.
<TOKEN> هو القيمة المنسوخة للرمز.

7. تكوين الويب أو خادم الوكيل لعكس حركة المرور إلى عقدة Wallarm¶

قم بتكوين خادم الويب أو الوكيل (مثلاً NGINX، Envoy) لعكس حركة المرور الواردة إلى عقدة Wallarm. للحصول على تفاصيل التكوين، نوصي بالرجوع إلى دليل خادم الويب أو الوكيل.

داخل [الرابط][web-server-mirroring-examples]، ستجد التكوين المثالي لأشهر خوادم الويب والوكلاء (NGINX، Traefik، Envoy).

قم بتعيين التكوين التالي في ملف /etc/nginx/sites-enabled/default على النسخة بالعقدة:
```
location / {
    include /etc/nginx/presets.d/mirror.conf;

    # قم بتغيير 222.222.222.22 إلى عنوان خادم العكس
    set_real_ip_from  222.222.222.22;
    real_ip_header    X-Forwarded-For;
}
```
أوامر set_real_ip_from وreal_ip_header مطلوبة لعرض عناوين IP للمخترقين في وحدة تحكم Wallarm.

8. اختبار تشغيل Wallarm¶

The request with test Path Traversal attack to an address of either the web or proxy server mirroring traffic or the machine with the Wallarm node:
```
curl http://<ADDRESS>/etc/passwd
```
Open Wallarm Console → Attacks section in the US Cloud or EU Cloud and make sure the attack is displayed in the list.

Since Wallarm OOB operates in the monitoring mode, the Wallarm node does not block the attack but registers it.

9. ضبط الحل المنشور¶

The deployment is now complete. The filtering node may require some additional configuration after deployment.

Wallarm settings are defined using the NGINX directives or the Wallarm Console UI. Directives should be set in the following files on the Wallarm instance:

/etc/nginx/sites-enabled/default defines the configuration of NGINX
/etc/nginx/conf.d/wallarm.conf defines the global configuration of Wallarm filtering node
/etc/nginx/conf.d/wallarm-status.conf defines the filtering node monitoring service configuration
/opt/wallarm/wstore/wstore.yaml with the postanalytics service (wstore) settings

You can modify the listed files or create your own configuration files to define the operation of NGINX and Wallarm. It is recommended to create a separate configuration file with the server block for each group of the domains that should be processed in the same way (e.g. example.com.conf). To see detailed information about working with NGINX configuration files, proceed to the official NGINX documentation.

Creating a configuration file

When creating a custom configuration file, make sure that NGINX listens to the incoming connections on the free port.

Below there are a few of the typical settings that you can apply if needed:

To apply the settings, restart NGINX on the Wallarm instance:

sudo systemctl restart nginx

Each configuration file change requires NGINX to be restarted to apply it.