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
|[Simple API Management][infra-simple-apim]| Just the basics with a publicly accessible API Management instance fronting your APIs. This is the innermost way to experience and experiment with the APIM policies. |
25
-
|[API Management & Container Apps][infra-apim-aca]| APIs are often implemented in containers running in Azure Container Apps. This architecture accesses the container apps publicly. It's beneficial to test both APIM and container app URLs to contrast and compare experiences of API calls through and bypassing APIM. It is not intended to be a security baseline. |
26
-
|[Front Door & API Management & Container Apps][infra-afd-apim-pe]| A secure implementation of Azure Front Door connecting to APIM via the new private link integration. This traffic, once it traverses through Front Door, rides entirely on Microsoft-owned and operated networks. The connection from APIM to Container Apps is secured but through a VNet configuration (it is also entirely possible to do this via private link). APIM Standard V2 is used here to accept a private link from Front Door. |
27
-
|[Application Gateway (Private Endpoint) & API Management & Container Apps][infra-appgw-apim-pe]| A secure implementation of Azure Application Gateway connecting to APIM via the new private link integration. This traffic, once it traverses through App Gateway, uses a private endpoint set up in the VNet's private endpoint subnet. The connection from APIM to Container Apps is secured but through a VNet configuration (it is also entirely possible to do this via private link). APIM Standard V2 is used here to accept a private link from App Gateway. |
26
+
|[Simple API Management][infra-simple-apim]|**Just the basics with a publicly accessible API Management instance** fronting your APIs. This is the innermost way to experience and experiment with the APIM policies. |
27
+
|[API Management & Container Apps][infra-apim-aca]| APIs are often implemented in containers running in **Azure Container Apps**. This architecture accesses the container apps publicly. It's beneficial to test both APIM and container app URLs to contrast and compare experiences of API calls through and bypassing APIM. It is not intended to be a security baseline. |
28
+
|[Front Door & API Management & Container Apps][infra-afd-apim-pe]|**A secure implementation of Azure Front Door connecting to APIM via the new private link integration!** This traffic, once it traverses through Front Door, rides entirely on Microsoft-owned and operated networks. The connection from APIM to Container Apps is secured but through a VNet configuration (it is also entirely possible to do this via private link). **APIM Standard V2** is used here to accept a private link from Front Door. |
29
+
|[Application Gateway (Private Endpoint) & API Management & Container Apps][infra-appgw-apim-pe]|**A secure implementation of Azure Application Gateway connecting to APIM via the new private link integration!** This traffic, once it traverses through App Gateway, uses a private endpoint set up in the VNet's private endpoint subnet. The connection from APIM to Container Apps is secured but through a VNet configuration (it is also entirely possible to do this via private link). APIM Standard V2 is used here to accept a private link from App Gateway. |
28
30
|[Application Gateway (VNet) & API Management & Container Apps][infra-appgw-apim]| Full VNet injection of APIM and ACA! APIM is shielded from any type of traffic unless it comes through App Gateway. This offers maximum isolation for instances in which customers seek VNet injection. |
29
31
30
32
## 📁 List of Samples
@@ -47,9 +49,11 @@ _Try it out, learn from it, apply it in your setups._
47
49
48
50
#### Option 1: GitHub Codespaces / Dev Container (Recommended)
49
51
50
-
The fastest way to get started is using our pre-configured development environment:
52
+
The fastest way to get started is using our pre-configured development environment. Each supported Python version has its own dev container,
53
+
providing you with a more tailored environment that hopefully more closely resembles your own workloads.
51
54
52
-
-**GitHub Codespaces**: Click the green "Code" button → "Codespaces" → "Create codespace on main"
55
+
-**GitHub Codespaces**: Click the green "Code" button → "Codespaces" → "..." → "New with options..." → "Dev container configuration" (select Python version but ignore *Default project configuration*) → "Create codespace"
56
+
<imgsrc="./assets/codespaces-python-configurations.png"alt="Codespaces configuration selector for various supposed Python versions"title="Codespaces configuration selector" />
53
57
-**VS Code Dev Containers**: Install the [Dev Containers extension][vscode-devcontainers], then "Reopen in Container"
54
58
55
59
All prerequisites are automatically installed and configured.
@@ -478,6 +482,7 @@ The original author of this project is [Simon Kurtz][simon-kurtz].
0 commit comments