Updated AWSO v2.12 in docs (#5103)

* Updated AWSO v2.12 in docs

* Removed root-cause-explorer from AWSO

* Updated doc for default scope

* Resized image Default-Scope.png

* Corrected Sumo Logic Access ID and Key section

* Updated mapping image

* Updated Doc for RCE

* Update about.md

* Updated release date and removed minor references

* Update index.md

---------

Co-authored-by: Amee Lepcha <[email protected]>

Author: akhil-sumologic

docs/observability/aws/about.md

@@ -11,7 +11,7 @@ AWS provides over 150 discrete services including compute, network, storage, dat
 
 Despite all of these services being a part of AWS, troubleshooting across different services can be problematic when you use separate AWS accounts to manage costs and give teams independent administrative control. Different AWS accounts often have different settings across Availability Zones or Regions, which makes it difficult to get a clear picture of overall application health.
 
-The Sumo Logic AWS Observability solution and Root Cause Explorer pull and analyze data across key AWS services and accounts, establish activity baselines, and determine causes for application incidents and high deviation events.
+The Sumo Logic AWS Observability solution analyze data across key AWS services and accounts, establish activity baselines, and determine causes for application incidents and high deviation events.
 
 :::sumo Micro Lesson
 Watch the following micro lesson to learn about our AWS Observability solution.
@@ -50,7 +50,6 @@ The **AWS Observability Solution** can be deployed across multiple accounts and
 * Minimize the time it takes to get operational insights across your AWS infrastructure.
 * Identify elements that are subject to specific operational issues across your AWS infrastructure.
 * Minimize the time it takes to assign operational to the correct business units and functional teams in your AWS infrastructure.
-* Expedite troubleshooting and root cause isolation for incidents in their apps and microservices running on AWS infrastructure using the Root Cause Explorer.
 
 The unified platform collects and provides logs, metrics, traces, and metadata for the Application, Microservices, Cloud, Orchestrator, and Container layers. The solution understands how the different datasets and services are connected, and stitches those relationships into an entity workflow that makes it more intuitive for users to get a holistic view of their service.
 

docs/observability/aws/deploy-use-aws-observability/before-you-deploy.md

@@ -30,7 +30,11 @@ If you are already collecting AWS metrics, logs, and/or events, we recommend tha
   * View Monitors
   * Manage Entity Type Configs
   * Create access keys
-* **Sumo Logic Access ID and Key**. When you deploy the solution, you’ll need to supply a Sumo Logic Access ID and Access Key, which enable you to use Sumo Logic APIs. Make sure you have the role capabilities listed above before generating the Access ID and Key.
+  * **Sumo Logic Access ID and Key**. When you deploy the solution, you’ll need to supply a Sumo Logic Access ID and Access Key, which enable you to use Sumo Logic APIs. Make sure you select default scope and have the role capabilities listed above before generating the Access ID and Key.
+  ![Default-Scope.png](/img/observability/Default-Scope.png)
+  :::note
+  For the AWS Observability Solution, you must use the default scope when generating the Access ID and Key; custom scopes are not supported.
+  :::
 * **AWS credentials**. To deploy the solution, you will need to log onto the AWS Console. For the CloudFormation template deployment option, your AWS role must have the permissions described by this [JSON file](https://sumologic-appdev-aws-sam-apps.s3.amazonaws.com/AWSObservabilityCFTemplatePermissions.json). As necessary, you may add JSON text to an existing or a new policy associated with an AWS IAM role as described in the [AWS documentation](https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-create-and-attach-iam-policy.html). For Terraform deployment options, see the \*.tmpl files in this folder [aws-observability-terraform/source-module/templates/](https://github.com/SumoLogic/sumologic-solution-templates/tree/master/aws-observability-terraform/source-module/templates).
 * Set up the [AWS CLI](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-install.html) and configure the AWS CLI as described in the [AWS documentation](https://docs.aws.amazon.com/cli/latest/userguide/cli-chap-configure.html) if you would like to use an AWS profile for Terraform script based deployment.
 * The AWS Observability solution comes with pre-packaged alerts in the form of Sumo Logic Monitors. To understand more about their capabilities please visit the Monitors page.
@@ -185,7 +189,7 @@ Here’s a sample `sources.json` file that you can include in your AMI.
 
 Before setting up the AWS Observability solution we recommend testing permissions for both AWS and Sumo Logic by using a test AWS CloudFormation template. To execute this template:
 
-1. Invoke the AWS CloudFormation template at this [URL](https://console.aws.amazon.com/cloudformation/home#/stacks/quickcreate?templateURL=https://sumologic-appdev-aws-sam-apps.s3.amazonaws.com/aws-observability-versions/v2.11.0/permissionchecker/permissioncheck.template.yaml).
+1. Invoke the AWS CloudFormation template at this [URL](https://console.aws.amazon.com/cloudformation/home#/stacks/quickcreate?templateURL=https://sumologic-appdev-aws-sam-apps.s3.amazonaws.com/aws-observability-versions/v2.12.0/permissionchecker/permissioncheck.template.yaml).
 1. Select the desired AWS region to test.
 1. Enter a Stack Name, Sumo Logic Deployment, and Sumo Logic Access ID and Access Key.<br/>  ![Testing_sumo_Permission_1.png](/img/observability/Testing_sumo_Permission_1.png)
 1. Click **Create Stack.**

docs/observability/aws/deploy-use-aws-observability/changelog.md

@@ -9,6 +9,18 @@ This section provides details on the available versions of the AWS Observability
 
 To install or upgrade to the required version of the CloudFormation template, use the URL of the YAML file corresponding to the right version number as the Amazon S3 URL in the AWS CloudFormation section of the AWS Management Console. See [Selecting a stack template](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/cfn-using-console-create-stack-template.html) for more information.
 
+## v2.12.0, 01-Apr-2025
+AWS Observability Solution (S3 Link for CloudFormation template): `https://sumologic-appdev-aws-sam-apps.s3.amazonaws.com/aws-observability-versions/v2.12.0/sumologic_observability.master.template.yaml`
+
+AWS Observability Solution (Terraform-based) repo: [sumologic-solution-templates](https://github.com/SumoLogic/sumologic-solution-templates).
+
+Updates:
+* Updated the SAM Lambda runtime from Node.js v20.x to v22.x.
+* Updated the Lambda runtime to Node.js v22.x in the CloudFormation template for `AWS CloudWatch Logs with Dead Letter Queue Support`.
+* Updated the SecurityHub SAM Lambda runtime from Python v3.11 to v3.13.
+* Updated Lambda runtime to Python v3.13 in the CloudFormation template for `Kinesis Metric Collection`
+* Discontinued support for Mumbai deployment.
+
 ## v2.11.0, 24-Jan-2025
 AWS Observability Solution (S3 Link for CloudFormation template): `https://sumologic-appdev-aws-sam-apps.s3.amazonaws.com/aws-observability-versions/v2.11.0/sumologic_observability.master.template.yaml`
 

docs/observability/aws/deploy-use-aws-observability/deploy-with-aws-cloudformation/automatic-installation-script.md

@@ -88,7 +88,6 @@ chmod +x DeployAWSOPosix.sh
 | Existing Sumo Logic Lambda CloudWatch Logs Source API URL | empty                                                                                                     |
 | Subscribe log groups to Sumo Logic Lambda Forwarder     | Both                                                                                                       |
 | Regex for AWS Lambda Log Groups                         | lambda                                                                                                    |
-| Select the Sumo Logic Root Cause Explorer Source        | Both                                                                                                       |
 | Enable ELB Classic Access logging                       | Both                                                                                                       |
 | Create Sumo Logic ELB Logs Source                       | Yes                                                                                                        |
 | Existing Sumo Logic ELB Classic Logs Source API URL     | empty                                                                                                      |

docs/observability/aws/deploy-use-aws-observability/deploy-with-aws-cloudformation/deploy-multiple-accounts-regions.md

@@ -19,8 +19,8 @@ Given that we use an account alias, we recommend you use StackSets to automati
 
 1. Sign in to the AWS Management console.
 1. Choose an option to invoke AWS CloudFormation Template:
-    * Click [this URL](https://console.aws.amazon.com/cloudformation/home#/stacks/quickcreate?templateURL=https://sumologic-appdev-aws-sam-apps.s3.amazonaws.com/aws-observability-versions/v2.11.0/sumologic_observability.master.template.yaml) to invoke the latest Sumo Logic AWS CloudFormation template.
-    * Download the AWS Observability Solution template (S3 link for CloudFormation template): https://sumologic-appdev-aws-sam-apps.s3.amazonaws.com/aws-observability-versions/v2.11.0/sumologic_observability.master.template.yaml to invoke the latest Sumo Logic AWS CloudFormation template.
+    * Click [this URL](https://console.aws.amazon.com/cloudformation/home#/stacks/quickcreate?templateURL=https://sumologic-appdev-aws-sam-apps.s3.amazonaws.com/aws-observability-versions/v2.12.0/sumologic_observability.master.template.yaml) to invoke the latest Sumo Logic AWS CloudFormation template.
+    * Download the AWS Observability Solution template (S3 link for CloudFormation template): https://sumologic-appdev-aws-sam-apps.s3.amazonaws.com/aws-observability-versions/v2.12.0/sumologic_observability.master.template.yaml to invoke the latest Sumo Logic AWS CloudFormation template.
     :::note
     If you would like to download or inspect this or other versions of this template, see the [Changelog](../changelog.md).
     :::
@@ -87,7 +87,7 @@ In case you do not provide a CSV file or if we detect that it does not have the
     in your AWS account.
 1. Click **Create StackSet**.  
     ![CloudFormation_Stackset 1.png](/img/observability/ClodFormation_Stackset_1.png)
-1. Paste the URL `https://sumologic-appdev-aws-sam-apps.s3.amazonaws.com/aws-observability-versions/v2.11.0/sumologic_observability.master.template.yaml` in the Amazon S3 URL option and click **Next**. If you'd like to download or inspect this or other versions of this template, see the [Changelog](../changelog.md).<br/>  ![multi-create-stack.png](/img/observability/multi-create-stack.png)
+1. Paste the URL `https://sumologic-appdev-aws-sam-apps.s3.amazonaws.com/aws-observability-versions/v2.12.0/sumologic_observability.master.template.yaml` in the Amazon S3 URL option and click **Next**. If you'd like to download or inspect this or other versions of this template, see the [Changelog](../changelog.md).<br/>  ![multi-create-stack.png](/img/observability/multi-create-stack.png)
 1. Provide a StackSet Name and supply the values for each of the prompts listed as per instructions in the [Deploy the AWS Observability Solution](/docs/observability/aws/deploy-use-aws-observability) section with the following exception:
     * Leave the field “Alias for AWS Account Identification” blank.  <br/>  ![aws-field.png](/img/observability/aws-field.png)
     * Provide the S3 Object URL of a CSV file that maps AWS Account IDs to an Account Alias in Section 2 of the template “AWS Account Alias”.  <br/>  ![aws-url.png](/img/observability/aws-url.png)