Management of database security groups

From EN Ikoula wiki
Revision as of 16:44, 18 November 2015 by Ikbot (talk | contribs)
⧼vector-jumptonavigation⧽ ⧼vector-jumptosearch⧽

ar:إدارة مجموعات الأمان في قاعدة البيانات zh:数据库安全组管理 ro:Gestionarea grupurilor de date de securitate pl:Zarządzanie grupami zabezpieczeń bazy danych de:Verwaltung der Datenbank-Sicherheitsgruppen nl:Beheer van database-beveiligingsgroepen it:Gestione di gruppi di sicurezza del database pt:Gestão de grupos de segurança do banco de dados es:Gestión de grupos de seguridad de base de datos fr:Gestion de base des groupes de sécurité

This article has been created by an automatic translation software. You can view the article source here.



Introduction

You will find here information on simplified management of openings in ports in the area of basic routing with CloudInstance

Place

By default, no Security rule allows traffic inbound to your instance at a basic zone creation (Area 3) in CloudStack.
In order to communicate with your instance, it is necessary to open the corresponding ports to your use.

Some common examples of opening port (We will use the CIDR 0.0.0.0/0 to allow all IP ranges to suit your Security needs ) :

Allow the "Ping " (More info on http://www.nthelp.com/icmp.html)
Protocol ICMP Type 8, Code 0, CIDR 0.0.0.0/0
SSH
TCP protocol, start port 22, end port 22, CIDR 0.0.0.0/0
RDP (Remote desktop )
TCP protocol, start port 3389, end port 3389, CIDR 0.0.0.0/0
Web service (IIS, Apache, nginx... | |)
TCP protocol, start port 80, end port 80, CIDR 0.0.0.0/0
Web service SSL (IIS, Apache, nginx... | |)
TCP protocol, start port 443, end port 443, CIDR 0.0.0.0/0
MySQL
TCP protocol, start port 3306, end port 3306, CIDR 0.0.0.0/0
SQLServer
TCP protocol, start port 1433, end port 1433, CIDR 0.0.0.0/0
DNS service
UDP protocol, start port 53, end port 53, CIDR 0.0.0.0/0



This article seemed you to be useful ?

0


You are not allowed to post comments.