How Cloud Firewall Protects Your Instance<\/h2>\nPrevents Unauthorized Access<\/h3>\n
Not every service on your instance needs to be publicly accessible. For example, SSH or Remote Desktop should typically be available only to administrators.<\/p>\n
By creating a firewall rule that allows access only from your office or home IP address, you prevent unauthorized users from even attempting to connect.<\/p>\n
Reduces Port Scanning<\/h3>\n
One of the first things attackers do is scan servers to identify open ports and running services.<\/p>\n
Cloud Firewall helps reduce your server’s visibility by blocking ports that aren’t meant to be publicly accessible. If a port is blocked, it won’t respond to scan requests, making your instance a less attractive target.<\/p>\n
Helps Stop Brute-Force Attacks<\/h3>\n
Services such as SSH, RDP, FTP, and database servers are common targets for automated password-guessing attacks.<\/p>\n
Restricting these services to trusted IP addresses greatly reduces the number of login attempts your server receives.<\/p>\n
Protects Databases and Internal Services<\/h3>\n
Database services like MySQL, PostgreSQL, and Redis are designed to communicate with applications, not with the public internet.<\/p>\n
Instead of exposing these services to everyone, you can configure firewall rules so they are accessible only from your application server or private network.<\/p>\n
Gives You Better Control Over Network Traffic<\/h3>\n
Firewall rules allow you to decide exactly what traffic is permitted.<\/p>\n
For example, a web server might only require:<\/p>\n
- \n
- HTTP (Port 80)<\/li>\n
- HTTPS (Port 443)<\/li>\n<\/ul>\n
Everything else can remain blocked unless there’s a specific need for it.<\/p>\n
This approach keeps your instance more secure while reducing unnecessary exposure.<\/p>\n
Common Firewall Rules<\/h2>\n
\n\n
\n Service<\/b><\/th>\n Protocol<\/b><\/th>\n Port<\/b><\/th>\n Recommendation<\/b><\/th>\n<\/tr>\n \n HTTP<\/th>\n TCP<\/th>\n 80<\/th>\n Allow<\/th>\n<\/tr>\n \n HTTPS<\/th>\n TCP<\/th>\n 443<\/th>\n Allow<\/th>\n<\/tr>\n \n SSH<\/th>\n TCP<\/th>\n 22<\/th>\n Allow only from trusted IPs<\/th>\n<\/tr>\n \n RDP<\/th>\n TCP<\/th>\n 3389<\/th>\n Allow only from trusted IPs<\/th>\n<\/tr>\n \n MySQL<\/th>\n TCP<\/th>\n 3306<\/th>\n Allow only on private networks or trusted IPs<\/th>\n<\/tr>\n<\/thead>\n<\/table>\n Example<\/h3>\n
Imagine you’re hosting a WordPress website on your instance.<\/p>\n
A good firewall configuration would be:<\/p>\n
- \n
- Allow HTTP (80) for website visitors.<\/li>\n
- Allow HTTPS (443) for secure browsing.<\/li>\n
- Allow SSH (22) only from your personal IP address.<\/li>\n
- Block direct access to the MySQL database (3306) from the internet.<\/li>\n
- Deny all other unnecessary inbound traffic.<\/li>\n<\/ul>\n
This setup keeps your website publicly accessible while protecting administrative and backend services.<\/p>\n
How to Configure Cloud Firewall in AccuWeb.Cloud<\/h2>\n
Step 1: Log in to AccuWeb.Cloud<\/h3>\n
Go to https:\/\/manage.accuweb.cloud\/<\/a> and log in using your registered credentials.<\/p>\n
![\"\"](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2026\/07\/s-blob-v1-IMAGE-B8W7TFCQSX0.png\")
<\/p>\nStep 2: Select Your instance<\/h3>\n
Open the instance you want to protect.<\/p>\n
![\"\"](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2026\/07\/Step-2-Select-Your-instance.png\")
<\/a><\/p>\nStep 3: Open the Firewall Settings<\/h3>\n
Navigate to the instance Settings <\/b>and then Firewall<\/b> section from the instance management page.<\/p>\n
![\"\"](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2026\/07\/Step-3-Open-the-Firewall-Settings.png\")
<\/a><\/p>\n
![\"\"](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2026\/07\/Step-3-Open-the-Firewall-Settings-1.png\")
<\/a><\/p>\n![\"\"](\"https:\/\/accuweb.cloud\/resource\/wp-content\/uploads\/2026\/07\/Start-Port-End-Port.png\")
<\/a><\/p>\n