Merge pull request #280384 from MicrosoftDocs/main

7/9/2024 AM Publish

Author: Taojunshen

articles/aks/artifact-streaming.md

@@ -5,7 +5,7 @@ author: schaffererin
 ms.author: schaffererin
 ms.service: azure-kubernetes-service
 ms.custom: devx-track-azurecli
-ms.topic: article
+ms.topic: how-to
 ms.date: 11/16/2023
 ms.subservice: aks-nodes
 ---

articles/aks/auto-upgrade-cluster.md

@@ -1,7 +1,7 @@
 ---
 title: Automatically upgrade an Azure Kubernetes Service (AKS) cluster
 description: Learn how to automatically upgrade an Azure Kubernetes Service (AKS) cluster to get the latest features and security updates.
-ms.topic: article
+ms.topic: how-to
 ms.author: nickoman
 author: nickomang
 ms.subservice: aks-upgrade

articles/aks/auto-upgrade-node-os-image.md

@@ -1,7 +1,7 @@
 ---
 title: Auto-upgrade Node OS Images 
 description: Learn how to choose an upgrade channel that best supports your needs for cluster's node OS security and maintenance. 
-ms.topic: article
+ms.topic: how-to
 ms.custom: build-2023, devx-track-azurecli
 ms.author: kaarthis
 author: kaarthis

articles/aks/cluster-extensions.md

@@ -2,7 +2,7 @@
 title: Cluster extensions for Azure Kubernetes Service (AKS)
 description: Learn how to deploy and manage the lifecycle of extensions on Azure Kubernetes Service (AKS)
 ms.date: 06/30/2023
-ms.topic: article
+ms.topic: overview
 author: nickomang
 ms.author: nickoman
 ---

articles/aks/csi-secrets-store-identity-access.md

@@ -3,7 +3,7 @@ title: Access Azure Key Vault with the CSI Driver Identity Provider
 description: Learn how to integrate the Azure Key Vault Provider for Secrets Store CSI Driver with your Azure credentials and user identities.
 author: nickomang
 ms.author: nickoman
-ms.topic: article
+ms.topic: how-to
 ms.subservice: aks-security
 ms.date: 12/19/2023
 ms.custom: devx-track-azurecli

articles/aks/dapr-overview.md

@@ -2,7 +2,7 @@
 title: Dapr extension for Azure Kubernetes Service (AKS) overview
 description: Learn more about using Dapr on your Azure Kubernetes Service (AKS) cluster to develop applications.
 ms.author: nickoman
-ms.topic: article
+ms.topic: overview
 ms.date: 04/22/2024
 ---
 

articles/aks/deploy-extensions-az-cli.md

@@ -2,7 +2,7 @@
 title: Deploy and manage cluster extensions by using the Azure CLI
 description: Learn how to use Azure CLI to deploy and manage extensions for Azure Kubernetes Service clusters.
 ms.date: 05/15/2023
-ms.topic: article
+ms.topic: how-to
 ms.custom: devx-track-azurecli
 author: JnHs
 ms.author: jenhayes

articles/aks/draft-devx-extension-aks.md

@@ -2,7 +2,7 @@
 title: Use Draft and the DevX extension for Visual Studio Code with Azure Kubernetes Service (AKS)
 description: Learn how to use Draft and the DevX extension for Visual Studio Code with Azure Kubernetes Service (AKS)
 author: schaffererin
-ms.topic: article
+ms.topic: how-to
 ms.date: 12/27/2023
 ms.author: schaffererin
 ---

articles/aks/eks-edw-rearchitect.md

@@ -17,7 +17,7 @@ The AWS workload is a basic example of the [competing consumers design pattern][
 
 A producer app generates load through sending messages to a queue, and a consumer app running in a Kubernetes pod processes the messages and writes the results to a database. KEDA manages pod autoscaling through a declarative binding to the producer queue, and Karpenter manages node autoscaling with just enough compute to optimize for cost. Authentication to the queue and the database uses OAuth-based [service account token volume projection][service-account-volume-projection].
 
-The workload consists of an AWS EKS cluster to orchestrate consumers reading messages from an Amazon Simple Queue Service (SQS) and saving processed messages to an AWS DynamoDB table. A producer app generates messages and queues them in the AWS SQS queue. KEDA and Karpenter dynamically scale the number of EKS nodes and pods used for the consumers.
+The workload consists of an AWS EKS cluster to orchestrate consumers reading messages from an Amazon Simple Queue Service (SQS) and saving processed messages to an Amazon DynamoDB table. A producer app generates messages and queues them in the Amazon SQS queue. KEDA and Karpenter dynamically scale the number of EKS nodes and pods used for the consumers.
 
 The following diagram represents the architecture of the EDW workload in AWS:
 

articles/aks/eks-edw-refactor.md

@@ -116,7 +116,7 @@ To see a working example, refer to the `deploy.sh` script in our [GitHub reposit
 
 ### AWS implementation
 
-The AWS workload uses the AWS boto3 Python library to interact with AWS SQS queues to configure storage queue access. The AWS IAM `AssumeRole` capability authenticates to the SQS endpoint using the IAM identity associated with the EKS pod hosting the application.
+The AWS workload uses the AWS boto3 Python library to interact with Amazon SQS queues to configure storage queue access. The AWS IAM `AssumeRole` capability authenticates to the SQS endpoint using the IAM identity associated with the EKS pod hosting the application.
 
 ```python
 import boto3
@@ -155,7 +155,7 @@ You can review the code for the queue producer (`aqs-producer.py`) in our [GitHu
 
 ### AWS implementation
 
-The original AWS code for DynamoDB access uses the AWS boto3 Python library to interact with AWS SQS queues. The consumer part of the workload uses the same code as the producer for connecting to the AWS SQS queue to read messages. The consumer also contains Python code to connect to DynamoDB using the AWS IAM `AssumeRole` capability to authenticate to the DynamoDB endpoint using the IAM identity associated with the EKS pod hosting the application.
+The original AWS code for DynamoDB access uses the AWS boto3 Python library to interact with Amazon SQS queues. The consumer part of the workload uses the same code as the producer for connecting to the Amazon SQS queue to read messages. The consumer also contains Python code to connect to DynamoDB using the AWS IAM `AssumeRole` capability to authenticate to the DynamoDB endpoint using the IAM identity associated with the EKS pod hosting the application.
 
 ```python
 # presumes policy deployment ahead of time such as: aws iam create-policy --policy-name <policy_name> --policy-document <policy_document.json>