AWS systems-manager-automation-runbooks documentation change
Summary
Updated documentation links by adding double slashes in AWS documentation URLs
Security assessment
The changes are purely URL formatting corrections (adding double slashes after domain) without any modifications to security-related content, permissions, or vulnerability disclosures. No security implications are introduced or addressed by these link changes.
Diff
diff --git a/systems-manager-automation-runbooks/latest/userguide/automation-troubleshoot-opensearch-red-yellow-cluster.md b/systems-manager-automation-runbooks/latest/userguide/automation-troubleshoot-opensearch-red-yellow-cluster.md index ceb625761..228c7b07d 100644 --- a//systems-manager-automation-runbooks/latest/userguide/automation-troubleshoot-opensearch-red-yellow-cluster.md +++ b//systems-manager-automation-runbooks/latest/userguide/automation-troubleshoot-opensearch-red-yellow-cluster.md @@ -9 +9 @@ -`AWSSupport-TroubleshootOpenSearchRedYellowCluster` automation runbook is used to identify the cause for [red](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/handling-errors.html#handling-errors-red-cluster-status) or [yellow](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/handling-errors.html#handling-errors-yellow-cluster-status) cluster health status and guide you through changing the cluster back to green. +`AWSSupport-TroubleshootOpenSearchRedYellowCluster` automation runbook is used to identify the cause for [red](https://docs.aws.amazon.com//opensearch-service/latest/developerguide/handling-errors.html#handling-errors-red-cluster-status) or [yellow](https://docs.aws.amazon.com//opensearch-service/latest/developerguide/handling-errors.html#handling-errors-yellow-cluster-status) cluster health status and guide you through changing the cluster back to green. @@ -17 +17 @@ The runbook performs the following steps: - * Calls the [DescribeDomain](https://docs.aws.amazon.com/opensearch-service/latest/APIReference/API_DescribeDomain.html) API against the target domain to get the cluster configuration. + * Calls the [DescribeDomain](https://docs.aws.amazon.com//opensearch-service/latest/APIReference/API_DescribeDomain.html) API against the target domain to get the cluster configuration. @@ -19 +19 @@ The runbook performs the following steps: - * Checks if the OpenSearch Service domain is internet-based (public) or [Amazon Virtual Private Cloud (VPC)-based](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/vpc.html). + * Checks if the OpenSearch Service domain is internet-based (public) or [Amazon Virtual Private Cloud (VPC)-based](https://docs.aws.amazon.com//opensearch-service/latest/developerguide/vpc.html). @@ -21 +21 @@ The runbook performs the following steps: - * Creates a public or [Amazon VPC-based](https://docs.aws.amazon.com/lambda/latest/dg/foundation-networking.html) AWS Lambda function depending on the cluster configuration. Note: The Lambda function contains the troubleshooting code that run the OpenSearch Service APIs against the cluster to determine why the cluster is in red or yellow state. + * Creates a public or [Amazon VPC-based](https://docs.aws.amazon.com//lambda/latest/dg/foundation-networking.html) AWS Lambda function depending on the cluster configuration. Note: The Lambda function contains the troubleshooting code that run the OpenSearch Service APIs against the cluster to determine why the cluster is in red or yellow state. @@ -106 +106 @@ Overview of `LambdaExecutionRole` policy: -The following is an example of a Lambda function's execution role (AWS Identity and Access Management (IAM) role) that grants the function permission to access AWS services and resources required by this runbook. For more information, see [Lambda execution role](https://docs.aws.amazon.com/lambda/latest/dg/lambda-intro-execution-role.html). +The following is an example of a Lambda function's execution role (AWS Identity and Access Management (IAM) role) that grants the function permission to access AWS services and resources required by this runbook. For more information, see [Lambda execution role](https://docs.aws.amazon.com//lambda/latest/dg/lambda-intro-execution-role.html). @@ -110 +110 @@ The following is an example of a Lambda function's execution role (AWS Identity -The `ec2:DescribeNetworkInterfaces`, `ec2:CreateNetworkInterface`, and `ec2:DeleteNetworkInterface` are only required if your OpenSearch Service cluster is [Amazon VPC-based](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/vpc.html) to allow the Lambda function to create and manage the Amazon VPC network interfaces. For more information, see [Connecting outbound networking to resources in a Amazon VPC](https://docs.aws.amazon.com/lambda/latest/dg/configuration-vpc.html#vpc-permissions) and [Lambda execution role](https://docs.aws.amazon.com/lambda/latest/dg/lambda-intro-execution-role.html). +The `ec2:DescribeNetworkInterfaces`, `ec2:CreateNetworkInterface`, and `ec2:DeleteNetworkInterface` are only required if your OpenSearch Service cluster is [Amazon VPC-based](https://docs.aws.amazon.com//opensearch-service/latest/developerguide/vpc.html) to allow the Lambda function to create and manage the Amazon VPC network interfaces. For more information, see [Connecting outbound networking to resources in a Amazon VPC](https://docs.aws.amazon.com//lambda/latest/dg/configuration-vpc.html#vpc-permissions) and [Lambda execution role](https://docs.aws.amazon.com//lambda/latest/dg/lambda-intro-execution-role.html). @@ -181 +181 @@ The utilization threshold percentage used to compare the CPUUtilization and JVMM - 4. If you have enabled [fine-grained access control](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/fgac.html) on an OpenSearch Service cluster, make sure that the `LambdaExecutionRole` role arn is mapped to a role with at least `cluster_monitor` permission. + 4. If you have enabled [fine-grained access control](https://docs.aws.amazon.com//opensearch-service/latest/developerguide/fgac.html) on an OpenSearch Service cluster, make sure that the `LambdaExecutionRole` role arn is mapped to a role with at least `cluster_monitor` permission. @@ -236 +236 @@ Systems Manager Automation - * [Run an automation](https://docs.aws.amazon.com/systems-manager/latest/userguide/automation-working-executing.html) + * [Run an automation](https://docs.aws.amazon.com//systems-manager/latest/userguide/automation-working-executing.html) @@ -238 +238 @@ Systems Manager Automation - * [Setting up an Automation](https://docs.aws.amazon.com/systems-manager/latest/userguide/automation-setup.html) + * [Setting up an Automation](https://docs.aws.amazon.com//systems-manager/latest/userguide/automation-setup.html) @@ -247 +247 @@ AWS service documentation - * Refer to[Troubleshooting Amazon OpenSearch Service](https://docs.aws.amazon.com/opensearch-service/latest/developerguide/handling-errors.html) for more information + * Refer to[Troubleshooting Amazon OpenSearch Service](https://docs.aws.amazon.com//opensearch-service/latest/developerguide/handling-errors.html) for more information