AWS Security ChangesHomeSearch

AWS solutions documentation change

Service: solutions · 2025-03-26 · Documentation low

File: solutions/latest/scene-intelligence-with-rosbag-on-aws/using-aws-cloudformation.md

Summary

Updated formatting (dashes, image syntax), corrected CloudFormation launch URL, and renumbered deployment steps

Security assessment

Changes involve formatting improvements and process clarifications. No security-specific content added or modified beyond existing IAM references which were already documented.

Diff

diff --git a/solutions/latest/scene-intelligence-with-rosbag-on-aws/using-aws-cloudformation.md b/solutions/latest/scene-intelligence-with-rosbag-on-aws/using-aws-cloudformation.md
index 37e8a4052..b52804443 100644
--- a/solutions/latest/scene-intelligence-with-rosbag-on-aws/using-aws-cloudformation.md
+++ b/solutions/latest/scene-intelligence-with-rosbag-on-aws/using-aws-cloudformation.md
@@ -11 +11 @@ This solution uses a CloudFormation template to handle the uninstallation workfl
-**Time to deploy:** Approximately 100–120 minutes 
+**Time to deploy:** Approximately 100-120 minutes
@@ -17 +17 @@ You can download the CloudFormation template for uninstalling this solution befo
-[ ![View template button.](/images/solutions/latest/scene-intelligence-with-rosbag-on-aws/images/view-template.png) ](https://solutions-reference.s3.amazonaws.com/scene-intelligence-with-rosbag-on-aws/latest/scene-intelligence-with-rosbag-on-aws-delete.template) **scene-intelligence-with-rosbag-on-aws-delete.template** \- Use this template to destroy the modules related to the solution and all associated components orchestrated by an open source GitOps library called `seedfarmer`. 
+[ ![View template button](/images/solutions/latest/scene-intelligence-with-rosbag-on-aws/images/view-template.png) ](https://solutions-reference.s3.amazonaws.com/scene-intelligence-with-rosbag-on-aws/latest/scene-intelligence-with-rosbag-on-aws-delete.template) **scene-intelligence-with-rosbag-on-aws-delete.template** Use this template to destroy the modules related to the solution and all associated components orchestrated by an open source GitOps library called `seedfarmer`.
@@ -34 +34 @@ Follow the step-by-step instructions in this section to uninstall the solution f
-**Time to deploy:** Approximately 100–120 minutes 
+**Time to deploy:** Approximately 100-120 minutes
@@ -38 +38 @@ Follow the step-by-step instructions in this section to uninstall the solution f
-[ ![Launch solution button.](/images/solutions/latest/scene-intelligence-with-rosbag-on-aws/images/launch-button.png) ](https://console.aws.amazon.com/cloudformation/home?region=us-east-1#/stacks/new?stackName=Scene-intelligence-with-rosbag-on-aws-role&templateURL=https://solutions-reference.s3.amazonaws.com/scene-intelligence-with-rosbag-on-aws/latest/scene-intelligence-with-rosbag-on-aws-delete.template)
+[ ![launch solution](/images/solutions/latest/scene-intelligence-with-rosbag-on-aws/images/launch-button.png) ](https://console.aws.amazon.com/cloudformation/home?region=us-east-1#/stacks/create/template?stackName=Scene-intelligence-with-rosbag-on-aws-role&templateURL=https://solutions-reference.s3.amazonaws.com/scene-intelligence-with-rosbag-on-aws/latest/scene-intelligence-with-rosbag-on-aws-delete.template)
@@ -40 +40,4 @@ Follow the step-by-step instructions in this section to uninstall the solution f
-  2. The template launches in the US East (N. Virginia) Region by default. To launch the solution in a different AWS Region, use the Region selector in the console navigation bar. 
+
+
+
+  1. The template launches in the US East (N. Virginia) Region by default. To launch the solution in a different AWS Region, use the Region selector in the console navigation bar.
@@ -46 +49 @@ This solution uses the Amazon MWAA service, which is not currently available in
-  3. On the **Create stack** page, verify that the correct template URL is in the **Amazon S3 URL** text box and choose **Next**. 
+  2. On the **Create stack** page, verify that the correct template URL is in the **Amazon S3 URL** text box and choose **Next**.
@@ -48 +51 @@ This solution uses the Amazon MWAA service, which is not currently available in
-  4. On the **Specify stack details** page, assign a name to your solution stack. For information about naming character limitations, see [IAM and AWS STS quotas](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_iam-limits.html) in the _AWS Identity and Access Management User Guide_. 
+  3. On the **Specify stack details** page, assign a name to your solution stack. For information about naming character limitations, see [IAM and AWS STS quotas](https://docs.aws.amazon.com/IAM/latest/UserGuide/reference_iam-limits.html) in the _AWS Identity and Access Management User Guide_.
@@ -50 +53 @@ This solution uses the Amazon MWAA service, which is not currently available in
-  5. Select **Next**. 
+  4. Select **Next**.
@@ -52 +55 @@ This solution uses the Amazon MWAA service, which is not currently available in
-  6. On the **Configure stack options** page, choose **Next** after reviewing the settings. 
+  5. On the **Configure stack options** page, choose **Next** after reviewing the settings.
@@ -54 +57 @@ This solution uses the Amazon MWAA service, which is not currently available in
-  7. On the **Review and create** page, review and confirm the settings. Select the box acknowledging that the template will create IAM resources. 
+  6. On the **Review and create** page, review and confirm the settings. Select the box acknowledging that the template will create IAM resources.
@@ -56 +59 @@ This solution uses the Amazon MWAA service, which is not currently available in
-  8. Choose **Submit** to deploy the stack. 
+  7. Choose **Submit** to deploy the stack.
@@ -61 +64 @@ This solution uses the Amazon MWAA service, which is not currently available in
-You can view the status of the stack in the AWS CloudFormation console in the **Status** column. You should receive a CREATE_COMPLETE status in approximately 100 \- 120 minutes 
+You can view the status of the stack in the AWS CloudFormation console in the **Status** column. You should receive a CREATE_COMPLETE status in approximately 100 - 120 minutes