Add AWSO 2.x and 3.x Deployment, Migration guide with manual and automation scripts

[Apoorvkudesia-sumologic]

Purpose of this pull request

This pull request adds changes for the AWSO 2.x.x to 3.x.x migration steps with manual and automation script docs.

Select the type of change

• Minor Changes - Typos, formatting, slight revisions
• Update Content - Revisions, updating sections
• New Content - New features, sections, pages, tutorials
• Site and Tools - .clabot, version updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)

Ticket (if applicable)

[amee-sumo]

Review feedback

A few items to address before merge:

1. Script download path unclear — In the CloudFormation migration doc (line 92), it says "Download the migration script from the sumologic-solution-templates repository" but doesn't provide a direct URL or curl command to download it. Users will need to search the repo. Consider adding a direct link, e.g.:

   curl -O https://raw.githubusercontent.com/SumoLogic/sumologic-solution-templates/main/<path>/MigrateToV300.sh

2. Placeholder note in manual doc — Line 174 says "Images showing where to find the role ARN in the CloudFormation console and where to update it in Sumo Logic will be added here." This should be resolved before merge — either add the images or remove the note.

3. Table rendering — In the scripted doc (line 145), --install-apps Yes\|No uses a backslash-pipe that may not render correctly. Consider using Yes/No or `Yes` or `No` instead.

4. Horizontal rules — The manual doc uses --- separators between steps. These aren't commonly used elsewhere in this repo and add visual weight. Consider removing them for consistency.

— via Claude Code

[amee-sumo]

Review feedback (round 2)

A few more items from the latest revision:

1. Missing download link for migration script (CloudFormation doc, line 92) — The doc says "Download the migration script from the sumologic-solution-templates repository" but still doesn't provide a direct URL or path. Users can't proceed without searching the repo. Please add a direct link or curl command, e.g.:

   curl -O https://raw.githubusercontent.com/SumoLogic/sumologic-solution-templates/main/<path>/MigrateToV300.sh

2. Table rendering issue (CloudFormation doc, line 145) — --install-apps Yes\|No renders literally as Yes\|No. The backslash-escaped pipe doesn't work as expected in Markdown tables. Use Yes / No or `Yes` or `No` instead.

3. Cross-reference link text mismatch (Manual doc, line 13) — The link says "using the migration script" but the linked page title is "Migrate AWS Observability from v2.x to v3.0.0 using CloudFormation". The link text should match the target page title for consistency.

— via Claude Code

[amee-sumo]

Review feedback (round 3)

One remaining issue that will confuse users:

Duplicate numbered steps in manual doc (lines 154–166) — The "Find the new IAM role ARN" section has overlapping instructions. Steps 3–4 appear twice with slightly different wording, and the numbered list restarts at 3 after the first screenshot:

1. Go to AWS Console > CloudFormation > Stacks...
2. In the Resources tab, find CreateCommonResources...
3. In the CreateCommonResources stack, go to Resources...search for SumoLogicSourceRole.
4. Note the Physical ID...

[screenshot]

3. In the CreateCommonResources stack, go to Resources...search for SumoLogicSourceRole.  ← duplicate
4. Click the Physical ID link to open the IAM role.  ← duplicate

[screenshot]

5. On the IAM role page, copy the ARN...

This should be a single sequential list (1→2→3→4→5) with screenshots placed between the relevant steps. The old text from before the screenshots were added (lines 154–157) should be removed since lines 159–168 now cover the same steps with proper screenshots.

— via Claude Code

[kimsauce]

Re-review of the latest commit (6bdea4c): 1 of 3 issues from the earlier pass is fixed (the v2.15.0 template URL in the update-stack doc — nice fix, now points to the "latest" section instead of hardcoding a version). Two link-target issues remain, flagged inline below.

---

Generated by Claude Code

[kimsauce]

All 8 topic cards on this "v3.0.0 (latest)" landing page link to un-versioned flat paths (before-you-deploy/, deploy-with-aws-cloudformation/, deploy-with-terraform/, migration-strategy-using-terraform/, view-dashboards/, configure-alerts/, update-aws-observability-stack/, resources/ — lines 42, 48, 54, 60, 66, 72, 78, 84), instead of the v3.0.0/-prefixed paths. None of these flat files exist anywhere in the repo anymore on this branch — every one of these docs now lives only under v2.15.0/ or v3.0.0/. So every card on this page is a dead link.

The sibling v2.15.0/index.md added in this same PR gets this right — it prefixes every card link with v2.15.0/. This file should follow the same pattern and prefix each link with v3.0.0/.

---

Generated by Claude Code

[kimsauce]

This note's Terraform cross-link points to the wrong doc: /docs/observability/aws/deploy-use-aws-observability/v3.0.0/migration-strategy-using-terraform/ is the unrelated, pre-existing "Migrate CloudWatch Source to Kinesis Firehose Source using Terraform" page, not a v2.x→v3.0.0 migration guide.

The actual v2.x→v3.0.0 Terraform migration guide added in this PR now lives at /docs/observability/aws/deploy-use-aws-observability/migration/terraform/ (per its slug in migration/terraform.md). This link should point there instead, so Terraform users land on the real migration steps rather than an unrelated source-migration doc.

---

Generated by Claude Code

[amee-sumo]

Missing 3.0.0 row in the AWSO lifecycle table. Both new migration guides tell readers to check this table for the list of "active AWSO versions" (migration-strategy-v2x-to-v300-manual.md:13, migration-strategy-v2x-to-v300-automate.md:13), but the table stops at 2.15.0 and there's no v3.0.0 row (or a ## v3.0.0 changelog section below it, unlike every prior version). Could you add one? I can confirm the Terraform Registry module was published 2026-08-27, but I don't have the right facts for the Active Support status or any region/deprecation caveats (e.g., the ESC/Zurich notes on the 2.14/2.15 rows) — those need author input.