Skip to content

Commit 99eb369

Browse files
ktoliverktoliver
authored
Merge pull request #77724 from kummanish/master
Adding new content for the connectivity architecture
2 parents c82e866 + 534e1bb commit 99eb369

File tree

9 files changed

+207
-3
lines changed

9 files changed

+207
-3
lines changed

‎articles/mariadb/TOC.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -50,7 +50,9 @@
5050
- name: Configuring SSL
5151
href: concepts-ssl-connection-security.md
5252
- name: VNet
53-
href: concepts-data-access-security-vnet.md
53+
href: concepts-data-access-security-vnet.md
54+
- name: Connectivity architecture
55+
href: concepts-connectivity-architecture.md
5456
- name: Business continuity
5557
items:
5658
- name: Overview

‎articles/mariadb/concepts-connectivity-architecture.md

Lines changed: 67 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,67 @@
1+
---
2+
title: Connectivity architecture in Azure Database for MariaDB
3+
description: Describes the connectivity architecture for your Azure Database for MariaDB server.
4+
author: kummanish
5+
ms.author: manishku
6+
ms.service: mariaDB
7+
ms.topic: conceptual
8+
ms.date: 05/23/2019
9+
---
10+
11+
# Connectivity architecture in Azure Database for MariaDB
12+
This article explains the Azure Database for MariaDB connectivity architecture as well as how the traffic is directed to your Azure Database for MariaDB instance from clients both within and outside Azure.
13+
14+
## Connectivity architecture
15+
16+
Connection to your Azure Database for MariaDB is established through a gateway that is responsible for routing incoming connections to the physical location of your server in our clusters. The following diagram illustrates the traffic flow.
17+
18+
![Overview of the connectivity architecture](./media/concepts-connectivity-architecture/connectivity-architecture-overview-proxy.png)
19+
20+
As client connect to the database, they get a connection string which connects to the gateway. This gateway has a public IP address that listens to port 3306. Inside the database cluster, traffic is forwarded to appropriate Azure Database for MariaDB. Therefore, in order to connect to your server, such as from corporate networks, it is necessary to open up the client side firewall to allow outbound traffic to be able to reach our gateways. Below you can find a complete list of the IP addresses used by our gateways per region.
21+
22+
## Azure Database for MariaDB gateway IP addresses
23+
24+
The following table lists the primary and secondary IPs of the Azure Database for MariaDB gateway for all data regions. The primary IP address is the current IP address of the gateway and the second IP address is a failover IP address in case of failure of the primary. As mentioned, customers should allow outbound to both the IP addresses. The second IP address does not listen in on any services until it is activated by Azure Database for MariaDB to accept connections.
25+
26+
| **Region Name** | **Primary IP Address** | **Secondary IP Address** |
27+
|:----------------|:-------------|:------------------------|
28+
| Australia East | 13.75.149.87 | 40.79.161.1 |
29+
| Australia South East | 191.239.192.109 | 13.73.109.251 |
30+
| Brazil South | 104.41.11.5 | |
31+
| Canada Central | 40.85.224.249 | |
32+
| Canada East | 40.86.226.166 | |
33+
| Central US | 23.99.160.139 | 13.67.215.62 |
34+
| China East 1 | 139.219.130.35 | |
35+
| China East 2 | 40.73.82.1 | |
36+
| China North 1 | 139.219.15.17 | |
37+
| China North 2 | 40.73.50.0 | |
38+
| East Asia | 191.234.2.139 | 52.175.33.150 |
39+
| East US 1 | 191.238.6.43 | 40.121.158.30 |
40+
| East US 2 | 191.239.224.107 | 40.79.84.180 * |
41+
| France Central | 40.79.137.0 | 40.79.129.1 |
42+
| Germany Central | 51.4.144.100 | |
43+
| India Central | 104.211.96.159 | |
44+
| India South | 104.211.224.146 | |
45+
| India West | 104.211.160.80 | |
46+
| Japan East | 191.237.240.43 | 13.78.61.196 |
47+
| Japan West | 191.238.68.11 | 104.214.148.156 |
48+
| Korea Central | 52.231.32.42 | |
49+
| Korea South | 52.231.200.86 | |
50+
| North Central US | 23.98.55.75 | 23.96.178.199 |
51+
| North Europe | 191.235.193.75 | 40.113.93.91 |
52+
| South Central US | 23.98.162.75 | 13.66.62.124 |
53+
| South East Asia | 23.100.117.95 | 104.43.15.0 |
54+
| UK South | 51.140.184.11 | |
55+
| UK West | 51.141.8.11| |
56+
| West Europe | 191.237.232.75 | 40.68.37.158 |
57+
| West US 1 | 23.99.34.75 | 104.42.238.205 |
58+
| West US 2 | 13.66.226.202 | |
59+
||||
60+
61+
> [!NOTE]
62+
> *East US 2* has also a tertiary IP address of `52.167.104.0`.
63+
64+
## Next steps
65+
66+
* [Create and manage Azure Database for MariaDB firewall rules using the Azure portal](./howto-manage-firewall-portal.md)
67+
* [Create and manage Azure Database for MariaDB firewall rules using Azure CLI](./howto-manage-firewall-cli.md)

‎articles/mariadb/media/concepts-connectivity-architecture/connectivity-architecture-overview-proxy.png

46.1 KB
Loading

‎articles/mysql/TOC.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,9 @@
8080
- name: Advanced Threat Protection
8181
href: concepts-data-access-and-security-threat-protection.md
8282
- name: VNet
83-
href: concepts-data-access-and-security-vnet.md
83+
href: concepts-data-access-and-security-vnet.md
84+
- name: Connectivity architecture
85+
href: concepts-connectivity-architecture.md
8486
- name: Business continuity
8587
items:
8688
- name: Overview

‎articles/mysql/concepts-connectivity-architecture.md

Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,66 @@
1+
---
2+
title: Connectivity architecture in Azure Database for MySQL
3+
description: Describes the connectivity architecture for your Azure Database for MySQL server.
4+
author: kummanish
5+
ms.author: manishku
6+
ms.service: mysql
7+
ms.topic: conceptual
8+
ms.date: 05/22/2019
9+
---
10+
11+
# Connectivity architecture in Azure Database for MySQL
12+
This article explains the Azure Database for MySQL connectivity architecture as well as how the traffic is directed to your Azure Database for MySQL instance from clients both within and outside Azure.
13+
14+
## Connectivity architecture
15+
Connection to your Azure Database for MySQL SQL is established through a gateway that is responsible for routing incoming connections to the physical location of your server in our clusters. The following diagram illustrates the traffic flow.
16+
17+
![Overview of the connectivity architecture](./media/concepts-connectivity-architecture/connectivity-architecture-overview-proxy.png)
18+
19+
As client connect to the database, they get a connection string which connects to the gateway. This gateway has a public IP address that listens to port 3306. Inside the database cluster, traffic is forwarded to appropriate Azure Database for MySQL. Therefore, in order to connect to your server, such as from corporate networks, it is necessary to open up the client side firewall to allow outbound traffic to be able to reach our gateways. Below you can find a complete list of the IP addresses used by our gateways per region.
20+
21+
## Azure Database for MySQL gateway IP addresses
22+
The following table lists the primary and secondary IPs of the Azure Database for MySQL gateway for all data regions. The primary IP address is the current IP address of the gateway and the second IP address is a failover IP address in case of failure of the primary. As mentioned, customers should allow outbound to both the IP addresses. The second IP address does not listen in on any services until it is activated by Azure Database for MySQL to accept connections.
23+
24+
| **Region Name** | **Primary IP Address** | **Secondary IP Address** |
25+
|:----------------|:-------------|:------------------------|
26+
| Australia East | 13.75.149.87 | 40.79.161.1 |
27+
| Australia South East | 191.239.192.109 | 13.73.109.251 |
28+
| Brazil South | 104.41.11.5 | |
29+
| Canada Central | 40.85.224.249 | |
30+
| Canada East | 40.86.226.166 | |
31+
| Central US | 23.99.160.139 | 13.67.215.62 |
32+
| China East 1 | 139.219.130.35 | |
33+
| China East 2 | 40.73.82.1 | |
34+
| China North 1 | 139.219.15.17 | |
35+
| China North 2 | 40.73.50.0 | |
36+
| East Asia | 191.234.2.139 | 52.175.33.150 |
37+
| East US 1 | 191.238.6.43 | 40.121.158.30 |
38+
| East US 2 | 191.239.224.107 | 40.79.84.180 * |
39+
| France Central | 40.79.137.0 | 40.79.129.1 |
40+
| Germany Central | 51.4.144.100 | |
41+
| India Central | 104.211.96.159 | |
42+
| India South | 104.211.224.146 | |
43+
| India West | 104.211.160.80 | |
44+
| Japan East | 191.237.240.43 | 13.78.61.196 |
45+
| Japan West | 191.238.68.11 | 104.214.148.156 |
46+
| Korea Central | 52.231.32.42 | |
47+
| Korea South | 52.231.200.86 | |
48+
| North Central US | 23.98.55.75 | 23.96.178.199 |
49+
| North Europe | 191.235.193.75 | 40.113.93.91 |
50+
| South Central US | 23.98.162.75 | 13.66.62.124 |
51+
| South East Asia | 23.100.117.95 | 104.43.15.0 |
52+
| UK South | 51.140.184.11 | |
53+
| UK West | 51.141.8.11| |
54+
| West Europe | 191.237.232.75 | 40.68.37.158 |
55+
| West US 1 | 23.99.34.75 | 104.42.238.205 |
56+
| West US 2 | 13.66.226.202 | |
57+
||||
58+
59+
> [!NOTE]
60+
> *East US 2* has also a tertiary IP address of `52.167.104.0`.
61+
62+
## Next steps
63+
64+
* [Create and manage Azure Database for MySQL firewall rules using the Azure portal](./howto-manage-firewall-using-portal.md)
65+
* [Create and manage Azure Database for MySQL firewall rules using Azure CLI](./howto-manage-firewall-using-cli.md)
66+

‎articles/mysql/media/concepts-connectivity-architecture/connectivity-architecture-overview-proxy.png

44.5 KB
Loading

‎articles/postgresql/TOC.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,9 @@
8989
- name: Advanced Threat Protection
9090
href: concepts-data-access-and-security-threat-protection.md
9191
- name: Virtual network
92-
href: concepts-data-access-and-security-vnet.md
92+
href: concepts-data-access-and-security-vnet.md
93+
- name: Connectivity architecture
94+
href: concepts-connectivity-architecture.md
9395
- name: Business continuity
9496
items:
9597
- name: Overview

‎articles/postgresql/concepts-connectivity-architecture.md

Lines changed: 65 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,65 @@
1+
---
2+
title: Connectivity architecture in Azure Database for PostgreSQL
3+
description: Describes the connectivity architecture for your Azure Database for PostgreSQL server.
4+
author: kummanish
5+
ms.author: manishku
6+
ms.service: PostgreSQL
7+
ms.topic: conceptual
8+
ms.date: 05/23/2019
9+
---
10+
11+
# Connectivity architecture in Azure Database for PostgreSQL
12+
This article explains the Azure Database for PostgreSQL connectivity architecture as well as how the traffic is directed to your Azure Database for PostgreSQL database instance from clients both within and outside Azure.
13+
14+
## Connectivity architecture
15+
Connection to your Azure Database for PostgreSQL is established through a gateway that is responsible for routing incoming connections to the physical location of your server in our clusters. The following diagram illustrates the traffic flow.
16+
17+
![Overview of the connectivity architecture](./media/concepts-connectivity-architecture/connectivity-architecture-overview-proxy.png)
18+
19+
As client connect to the database, they get a connection string which connects to the gateway. This gateway has a public IP address that listens to port 5432. Inside the database clusterz traffic is forwarded to appropriate Azure Database for PostgreSQL. Therefore, in order to connect to your server, such as from corporate networks, it is necessary to open up the client side firewall to allow outbound traffic to be able to reach our gateways. Below you can find a complete list of the IP addresses used by our gateways per region.
20+
21+
## Azure Database for PostgreSQL gateway IP addresses
22+
The following table lists the primary and secondary IPs of the Azure Database for PostgreSQL gateway for all data regions. The primary IP address is the current IP address of the gateway and the second IP address is a failover IP address in case of failure of the primary. As mentioned, customers should allow outbound to both the IP addresses. The second IP address does not listen in on any services until it is activated by Azure Database for PostgreSQL to accept connections.
23+
24+
| **Region Name** | **Primary IP Address** | **Secondary IP Address** |
25+
|:----------------|:-------------|:------------------------|
26+
| Australia East | 13.75.149.87 | 40.79.161.1 |
27+
| Australia South East | 191.239.192.109 | 13.73.109.251 |
28+
| Brazil South | 104.41.11.5 | |
29+
| Canada Central | 40.85.224.249 | |
30+
| Canada East | 40.86.226.166 | |
31+
| Central US | 23.99.160.139 | 13.67.215.62 |
32+
| China East 1 | 139.219.130.35 | |
33+
| China East 2 | 40.73.82.1 | |
34+
| China North 1 | 139.219.15.17 | |
35+
| China North 2 | 40.73.50.0 | |
36+
| East Asia | 191.234.2.139 | 52.175.33.150 |
37+
| East US 1 | 191.238.6.43 | 40.121.158.30 |
38+
| East US 2 | 191.239.224.107 | 40.79.84.180 * |
39+
| France Central | 40.79.137.0 | 40.79.129.1 |
40+
| Germany Central | 51.4.144.100 | |
41+
| India Central | 104.211.96.159 | |
42+
| India South | 104.211.224.146 | |
43+
| India West | 104.211.160.80 | |
44+
| Japan East | 191.237.240.43 | 13.78.61.196 |
45+
| Japan West | 191.238.68.11 | 104.214.148.156 |
46+
| Korea Central | 52.231.32.42 | |
47+
| Korea South | 52.231.200.86 | |
48+
| North Central US | 23.98.55.75 | 23.96.178.199 |
49+
| North Europe | 191.235.193.75 | 40.113.93.91 |
50+
| South Central US | 23.98.162.75 | 13.66.62.124 |
51+
| South East Asia | 23.100.117.95 | 104.43.15.0 |
52+
| UK South | 51.140.184.11 | |
53+
| UK West | 51.141.8.11| |
54+
| West Europe | 191.237.232.75 | 40.68.37.158 |
55+
| West US 1 | 23.99.34.75 | 104.42.238.205 |
56+
| West US 2 | 13.66.226.202 | |
57+
||||
58+
59+
> [!NOTE]
60+
> *East US 2* has also a tertiary IP address of `52.167.104.0`.
61+
62+
## Next steps
63+
64+
* [Create and manage Azure Database for PostgreSQL firewall rules using the Azure portal](./howto-manage-firewall-using-portal.md)
65+
* [Create and manage Azure Database for PostgreSQL firewall rules using Azure CLI](./howto-manage-firewall-using-cli.md)

‎articles/postgresql/media/concepts-connectivity-architecture/connectivity-architecture-overview-proxy.png

47.6 KB
Loading

0 commit comments

Comments
 (0)