You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: content/en/docs/deployment/mendix-cloud-deploy/connecting-external-resources.md
+62-15Lines changed: 62 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,37 +14,84 @@ This feature is in Public Beta. For more information, see [Release Status](/rele
14
14
15
15
## Introduction
16
16
17
-
[Mendix Cloud Private Connectivity](/control-center/private-connectivity/) enables your Mendix applications to securely and privately connect to internal resources, whether they are on-premises or in the cloud. This ensures that the connection bypasses the public internet and instead goes through a private tunnel, enhancing security and compliance.
17
+
[Mendix Cloud Private Connectivity](/control-center/private-connectivity/) enables your Mendix applications to securely and privately connect to internal resources, whether they are on-premises or in the cloud. This ensures that connection bypasses the public internet and instead goes through a private tunnel, improving security and compliance.
18
18
19
-
This document guides [Technical Contacts](/developerportal/general/app-roles/#technical-contact)through the process of requesting and managing connections to external resources using Mendix Cloud Private Connectivity.
19
+
This page describes how [Technical Contacts](/developerportal/general/app-roles/#technical-contact)can request and manage connections to external resources using Mendix Cloud Private Connectivity.
20
20
21
21
## Prerequisites {#prerequisites}
22
22
23
23
Before requesting a connection, the following conditions must be met:
24
24
25
25
* You are the [Technical Contact](/developerportal/general/app-roles/#technical-contact) for the Mendix application.
26
-
* A Mendix Admin has created and configured the necessary private network in the [Control Center](/control-center/configure-private-connectivity/). This includes installing agents and exposing the specific external resource you want to connect to.
26
+
* A Mendix Admin has created and configured the necessary private network in the [Control Center](/control-center/configure-private-connectivity/). This includes installing agents and exposing the specific external resource you want to access.
27
27
28
28
## Connections {#connections}
29
29
30
-
Mendix Cloud Connect Connections allow applications on Mendix Cloud to connect to Mendix Cloud Connect Resources over Mendix Cloud Connect Networks.
30
+
Mendix Cloud Connect Connections allow applications on Mendix Cloud to connect to Mendix Cloud Connect Resources over Mendix Cloud Connect Networks. Each connection request must be initiated by a Technical Contact and approved by a Mendix Admin before the application on Mendix Cloud can connect to the resource.
31
31
32
-
Each connection request must be initiated by a Technical Contact through the [Mendix Support Portal](https://support.mendix.com/) before the application on Mendix Cloud can connect to the Resource. An application on Mendix Cloud can establish multiple connections to various resources.
32
+
An application on Mendix Cloud can establish multiple connections to various resources. You can view and manage all connections and their statuses within the [Connections](/developerportal/deploy/environments-details/#connections) section on the application's **Network** tab.
33
+
{{% alert color="info" %}} An application environment can only connect to a single private network at a time. This means that all external resources you connect to from an application environment must be on the same private network.{{% /alert %}}
33
34
35
+
### Requesting a New Connection {#connection-request}
36
+
37
+
As a Technical Contact, follow these steps to request a new connection from your application environment to an approved external resource:
38
+
39
+
1. From [Apps](https://sprintr.home.mendix.com), go to the app's **Environments** page.
40
+
2. Click **Details** ({{% icon name="notes-paper-edit" %}}) on the preferred environment.
41
+
3. Go to the **Network** tab.
42
+
4. In the **Connections** section, click **Add** to initiate a new connection request.
34
43
{{% alert color="info" %}}
35
-
An application environment can only be connected to a single private network at a time. This means that all external resources you connect to from an application environment must be on the same private network.
44
+
Contact your Mendix Admin if the resource you want is not on the list.
36
45
{{% /alert %}}
46
+
5. In the **Add Connection** dialog, select an available network. This action displays the resources exposed on that network.
### Requesting a New Connection {#connection-request}
49
+
* If your application environment already has an active connection, the network associated with that connection will be automatically selected and cannot be changed unless all existing connections are deleted.
50
+
* If only one private network is available for your application, it will be automatically selected.
51
+
{{% /alert %}}
39
52
40
-
As a Technical Contact, follow these steps to request a new connection from your application environment to an approved external resource:
53
+
1. Select the specific resource you want your application environment to connect to.
54
+
1. Click **Save** to submit your connection request for approval. All submitted connection requests appear in the [Control Center](/control-center/configure-private-connectivity/) for the Mendix Admin review.
55
+
1.[Track and manage](#manage-connection-requests) your connection requests from the [Change Requests](/developerportal/deploy/environments/#change-requests) tab on your app's environment's page.
56
+
{{% alert color="info" %}}
57
+
If this is the first connection approved for an application environment, you must redeploy that environment for the connection to become active and usable.
58
+
{{% /alert %}}
59
+
60
+
### Connection Request Status
61
+
62
+
This diagram shows the progress of the request status from when the connection request is submitted to when it is completed (approved or rejected):
63
+
64
+
{{< figure src="/attachments/deployment/mendix-cloud-deploy/connecting-to-external-services/connection-request-status-flow.png" alt="Flowchart illustrating the lifecycle of a Mendix Cloud Private Connectivity request, showing stages like 'Pending Approval', 'Mendix Admin Review', 'Approved', and 'Rejected'." >}}
41
65
42
-
1. Create a [support ticket](https://support.mendix.com/) with the following specifications:
43
-
***Ticket title** – Must contain the words "Mendix Cloud Private Connectivity Connection Request".
44
-
***Environment ID** – Found in the [General Tab](/developerportal/deploy/environments-details/#application-status) of the **Environments Details** page.
45
-
***Resource ID** – Found on the **Resource Details** dialog on the [Private Connectivity](/control-center/configure-private-connectivity/#private-connectivity-resources) page in Control Center. Request this from your application's Mendix Admin.
46
-
***Restart timestamp** – Specify your preferred time for environment restart (or indicate "ASAP"). The scheduled time must be during the EMEA office hours (08:00 – 18:00 CET, Monday through Friday).
47
-
2. Submit the ticket and await confirmation from the support team.
66
+
Once a Technical Contact submits a connection request, it enters a **Pending Approval** status. The request is then sent to a Mendix Admin for review:
48
67
49
-
Mendix Support will notify you when the connection request is added and ready to use.
68
+
* If the Mendix Admin rejects the request, its status becomes **Rejected**.
69
+
* If the Mendix Admin approves the request, the connection status will reflect as follows:
70
+
* In the **Change Requests** tab of the Environments page, the status changes to **Completed**,
71
+
* In the **Connections** section of the **Network** tab, the status shows as **Approved**.
50
72
73
+
A Mendix Admin can also revoke an already approved connection, which will change its status back to **Rejected**.
The [Connections](/developerportal/deploy/environments-details/#connections) section on the application's **Network** tab allows Technical Contacts to view all connections for the environment and track pending request statuses
78
+
79
+
Additionally, depending on the connection's status, you can perform the following actions:
80
+
81
+
### Cancelling a Connection Request {#cancel-connection}
82
+
83
+
As a Technical Contact, you can cancel a connection request if its status is **Pending Approval**.
84
+
To cancel a pending connection request:
85
+
86
+
1. On the [Connections](/developerportal/deploy/environments-details/#connections) section of the Network tab, locate the connection request with the status **Pending Approval**.
87
+
2. Click **Cancel Request** next to that connection.
88
+
89
+
### Deleting an Established Connection
90
+
91
+
After a connection request is approved, you can delete the connection at any time by following these steps:
92
+
93
+
1. On the [Connections](/developerportal/deploy/environments-details/#connections) section of the **Network** tab, locate the approved connection you want to remove.
94
+
2. Click **Delete** next to that connection.
95
+
{{% alert color="info" %}}
96
+
Deleting a connection immediately breaks the connection between your application environment and the resource.
Copy file name to clipboardExpand all lines: content/en/docs/deployment/mendix-cloud-deploy/environments.md
+1-3Lines changed: 1 addition & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -175,14 +175,12 @@ If you are the [Technical Contact](/developerportal/general/app-roles/#technical
175
175
176
176
### Change Requests Tab {#change-requests}
177
177
178
-
On the **Change Requests** tab, the Technical Contact can view details of all past and current [Plan](/developerportal/deploy/change-plan/) requests and perform certain actions based on their current status.
178
+
On the **Change Requests** tab, the Technical Contact can view details of all past and current requests for either the [Plan](/developerportal/deploy/change-plan/) or [Connection](/developerportal/deploy/connecting-to-external-resource/) requests and perform certain actions based on their current status.
179
179
180
180
For each submitted request, the following information is available:
181
181
182
182
***Request Type** – Type of change requested
183
183
***Environment** – The environment the change was requested for (such as, acceptance or production)
184
-
***Current Plan** – The environment's existing plan
185
-
***Requested Plan** – The plan requested for change
186
184
***Submitted on** – Request submission date
187
185
***Status** – Current request state
188
186
***Action** – Shows more details of each request and provides options based on the request status
Copy file name to clipboardExpand all lines: content/en/docs/releasenotes/deployment/mendix-cloud.md
+9Lines changed: 9 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,15 @@ There are separate release notes for other deployment targets; for more informat
14
14
15
15
For information on the current status of deployment to Mendix Cloud and any planned releases, see [Mendix Status](https://status.mendix.com/).
16
16
17
+
## 2026
18
+
19
+
### January 5, 2026
20
+
21
+
#### New Features
22
+
23
+
* We have added a new feature in the **Network tab** of the **Environment Details** page that enables Technical Contacts to securely [connect Mendix applications to external resources](/developerportal/deploy/connecting-to-external-resource/) through [Mendix Cloud Private Connectivity](/control-center/private-connectivity/).
24
+
* From the [Connections](/developerportal/deploy/environments-details/#connections) section of the **Network** tab, Technical Contacts can now request new private connections, track the status of their pending connection requests, connect to external resources, and delete existing connections.
0 commit comments