Merge pull request #292296 from dlepow/awsc

[APIC] AWS API sync

Author: denrea

.github/workflows/stale.yml

@@ -38,8 +38,12 @@
         href: manage-apis-azure-cli.md
       - name: Import APIs from API Management
         href: import-api-management-apis.md
-      - name: Synchronize APIs from API Management
-        href: synchronize-api-management-apis.md
+      - name: Integrate API sources
+        items:    
+        - name: Synchronize APIs from API Management
+          href: synchronize-api-management-apis.md
+        - name: Synchronize APIs from Amazon API Gateway
+          href: synchronize-aws-gateway-apis.md
       - name: Build and register APIs - VS Code extension
         href: build-register-apis-vscode-extension.md
       - name: Register APIs - GitHub Actions

articles/api-center/TOC.yml

@@ -7,7 +7,7 @@ author: dlepow
 
 ms.service: azure-api-center
 ms.topic: include
-ms.date: 11/07/2024
+ms.date: 01/09/2025
 ms.author: danlep
 ms.custom: Include file
 ---

articles/api-center/includes/api-center-service-limits.md

@@ -19,9 +19,9 @@ To allow import of APIs, assign your API center's managed identity the **API Man
 1. In the left menu, select **Access control (IAM)**.
 1. Select **+ Add role assignment**.
 1. On the **Add role assignment** page, set the values as follows: 
-    1. On the **Role** tab - Select **API Management Service Reader**.
+    1. On the **Role** tab, select **API Management Service Reader**.
     1. On the **Members** tab, in **Assign access to** - Select **Managed identity** > **+ Select members**.
-    1. On the **Select managed identities** page - Select the system-assigned managed identity of your API center that you added in the previous section. Click **Select**.
+    1. On the **Select managed identities** page, select the system-assigned managed identity of your API center that you added in the previous section. Click **Select**.
     1. Select **Review + assign**.
 
 #### [Azure CLI](#tab/cli)

articles/api-center/includes/configure-managed-identity-apim-reader.md

@@ -0,0 +1,79 @@
+---
+title: Include file
+description: Include file
+services: api-center
+author: dlepow
+
+ms.service: azure-api-center
+ms.topic: include
+ms.date: 12/20/2024
+ms.author: danlep
+ms.custom: Include file
+---
+
+To allow import of APIs, assign your API center's managed identity the **Key Vault Secrets User** role in your Azure key vault. You can use the [portal](../../role-based-access-control/role-assignments-portal-managed-identity.yml) or the Azure CLI.
+
+#### [Portal](#tab/portal)
+
+1. In the [portal](https://azure.microsoft.com), navigate to your key vault.
+1. In the left menu, select **Access control (IAM)**.
+1. Select **+ Add role assignment**.
+1. On the **Add role assignment** page, set the values as follows: 
+    1. On the **Role** tab, select **Key Vault Secrets User**.
+    1. On the **Members** tab, in **Assign access to** - Select **Managed identity** > **+ Select members**.
+    1. On the **Select managed identities** page, select the system-assigned managed identity of your API center that you added in the previous section. Click **Select**.
+    1. Select **Review + assign**.
+
+#### [Azure CLI](#tab/cli)
+
+1. Get the principal ID of the identity. For a system-assigned identity, use the [az apic show](/cli/azure/apic#az-apic-show) command. 
+
+    ```azurecli
+    #! /bin/bash
+    apicObjID=$(az apic show --name <api-center-name> \
+        --resource-group <resource-group-name> \
+        --query "identity.principalId" --output tsv)
+    ```
+
+    ```azurecli
+    # Formatted for PowerShell
+    $apicObjID=$(az apic show --name <api-center-name> `
+        --resource-group <resource-group-name> `
+        --query "identity.principalId" --output tsv)
+    ```
+
+1. Get the resource ID of your key vault using the [az keyvault show](/cli/azure/keyvault#az-keyvault-show) command.
+ 
+    ```azurecli
+    #! /bin/bash
+    kvID=$(az keyvault show --name <kv-name> --resource-group <resource-group-name> --query "id" --output tsv)
+    ```
+
+    ```azurecli
+    # Formatted for PowerShell
+    $kvID=$(az keyvault show --name <kv-name> --resource-group <resource-group-name> --query "id" --output tsv)
+    ```
+
+1. Assign the managed identity the **Key Vault Secrets User** role in your key vault the [az role assignment create](/cli/azure/role/assignment#az-role-assignment-create) command.
+
+    ```azurecli
+    #! /bin/bash
+    scope="${kvID:1}"
+
+    az role assignment create \
+        --role "Key Vault Secrets User" \
+        --assignee-object-id $apicObjID \
+        --assignee-principal-type ServicePrincipal \
+        --scope $scope 
+    ```
+    
+    ```azurecli
+    # Formatted for PowerShell
+    $scope=$apimID.substring(1)
+
+    az role assignment create `
+        --role "Key Vault Secrets User" `
+        --assignee-object-id $apicObjID `
+        --assignee-principal-type ServicePrincipal `
+        --scope $scope 
+---

articles/api-center/includes/configure-managed-identity-kv-secret-user.md

@@ -0,0 +1,39 @@
+---
+title: Include file
+description: Include file
+services: api-center
+author: dlepow
+
+ms.service: azure-api-center
+ms.topic: include
+ms.date: 01/21/2025
+ms.author: danlep
+ms.custom: Include file
+---
+
+## Delete an integration
+
+While an API source is integrated, you can't delete synchronized APIs from your API center. If you need to, you can delete the integration. When you delete an integration:
+
+* The synchronized APIs in your API center inventory are deleted
+* The environment and deployments associated with the API source are deleted
+
+You can delete an integration using the portal or the Azure CLI. 
+
+#### [Portal](#tab/portal)
+
+1. In the [portal](https://portal.azure.com), navigate to your API center.
+1. Under **Assets**, select **Environments** > **Links (preview)**.
+1. Select the link, and then select **Delete** (trash can icon). 
+
+#### [Azure CLI](#tab/cli)
+
+Run the [az apic integration delete](/cli/azure/apic/integration#az-apic-integration-delete) (preview) command to delete an integration. Provide the names of the resource group, API center, and integration.
+
+```azurecli
+az apic integration delete \
+    --resource-group <resource-group-name> \
+    --service-name <api-center-name> \
+    --integration-name <integration-name> \
+```
+---

articles/api-center/includes/delete-api-integration.md

@@ -6,14 +6,16 @@ author: dlepow
 
 ms.service: azure-api-center
 ms.topic: include
-ms.date: 10/18/2024
+ms.date: 12/20/2024
 ms.author: danlep
 ms.custom: Include file
 ---
 
-For this scenario, your API center uses a [managed identity](/entra/identity/managed-identities-azure-resources/overview) to access APIs in your API Management instance. Depending on your needs, configure either a system-assigned or one or more user-assigned managed identities. 
+## Enable a managed identity in your API center
 
-The following examples show how to configure a system-assigned managed identity by using the Azure portal or the Azure CLI. At a high level, configuration steps are similar for a user-assigned managed identity. 
+For this scenario, your API center uses a [managed identity](/entra/identity/managed-identities-azure-resources/overview) to access Azure resources. Depending on your needs, enable either a system-assigned or one or more user-assigned managed identities. 
+
+The following examples show how to enable a system-assigned managed identity by using the Azure portal or the Azure CLI. At a high level, configuration steps are similar for a user-assigned managed identity. 
 
 #### [Portal](#tab/portal)
 

articles/api-center/includes/enable-managed-identity.md

@@ -14,4 +14,4 @@ ms.custom: Include file
 > [!NOTE]
 > `az apic` commands require the `apic-extension` Azure CLI extension. If you haven't used `az apic` commands, the extension can be installed dynamically when you run your first `az apic` command, or you can install the extension manually. Learn more about [Azure CLI extensions](/cli/azure/azure-cli-extensions-overview).
 >
-> See the [release notes](https://github.com/Azure/azure-cli-extensions/blob/main/src/apic-extension/HISTORY.rst) for the latest changes and updates in the `apic-extension`.
+> See the [release notes](https://github.com/Azure/azure-cli-extensions/blob/main/src/apic-extension/HISTORY.rst) for the latest changes and updates in the `apic-extension`. Certain features may require a preview or specific version of the extension.

articles/api-center/includes/install-apic-extension.md

@@ -0,0 +1,25 @@
+---
+title: Include file
+description: Include file
+services: api-center
+author: dlepow
+
+ms.service: azure-api-center
+ms.topic: include
+ms.date: 01/08/2025
+ms.author: danlep
+ms.custom: Include file
+---
+You can add or update metadata properties and documentation to the synchronized APIs in your API center to help stakeholders discover, understand, and consume the APIs. Learn more about Azure API Center's [built-in and custom metadata properties](../add-metadata-properties.md).
+
+The following table shows entity properties that can be modified in Azure API Center and properties that are set based on their values in the API source. 
+
+| Entity       | Properties configurable in API Center                     | Properties determined in integrated API source                                           |
+|--------------|-----------------------------------------|-----------------|
+| API          | summary<br/>lifecycleStage<br/>termsOfService<br/>license<br/>externalDocumentation<br/>customProperties    | title<br/>description<br/>kind                   |
+| API version  | lifecycleStage      | title<br/>definitions (if synchronized)                            |
+| Environment  | title<br/>description<br/>kind</br>server.managementPortalUri<br/>onboarding<br/>customProperties      | server.type
+| Deployment   |  title<br/>description<br/>server<br/>state<br/>customProperties    |      server.runtimeUri |
+
+> [!NOTE]
+> Resource and system IDs for entities synchronized to Azure API Center are automatically generated and can't be changed.