AWS Security ChangesHomeSearch

AWS solutions documentation change

Service: solutions · 2026-03-28 · Documentation low

File: solutions/latest/instance-scheduler-on-aws/update-the-solution.md

Summary

Updated version compatibility notes and added 'Important' section about tag governance considerations when updating to newer versions

Security assessment

This change provides update guidance and tag governance considerations for the Instance Scheduler solution. It mentions that the solution writes up to 6 unique tags and advises ensuring tag governance policies allow these tags, but this is about operational compliance rather than security. No security vulnerabilities, access control issues, or data protection concerns are addressed.

Diff

diff --git a/solutions/latest/instance-scheduler-on-aws/update-the-solution.md b/solutions/latest/instance-scheduler-on-aws/update-the-solution.md
index dc82f73b3..a123b3d47 100644
--- a//solutions/latest/instance-scheduler-on-aws/update-the-solution.md
+++ b//solutions/latest/instance-scheduler-on-aws/update-the-solution.md
@@ -122 +122 @@ When updating to v3.1.0 or newer:
-  * Scheduled instance resizing (defining `period-name@size` in a schedule) is no longer supported.
+  * _(Restored in v3.2.0)_ Scheduled instance resizing (defining `period-name@size` in a schedule) was temporarily removed in v3.1.0 but has been re-implemented in v3.2.0 and newer. Refer to [Instance type](./schedule-reference.html#instance-type).
@@ -124 +124 @@ When updating to v3.1.0 or newer:
-  * Listing member accounts via an SSM parameter (passing `{param: ssm-param-name}` to the accounts parameter on the hub stack) is no longer supported. All trusted accounts must be passed to the hub stack at deploy-time
+  * Listing member accounts via an SSM parameter (passing `{param: ssm-param-name}` to the accounts parameter on the hub stack) is no longer supported. All trusted accounts must be passed to the hub stack at deploy-time.
@@ -136,0 +137,4 @@ When updating to v3.1.0 or newer:
+###### Important
+
+Instance Scheduler writes up to 6 unique tags to managed resources during normal operation. Ensure that your tag governance policies (such as AWS Config rules, tag policies, or automated remediation) are configured to allow these tags. For a full list of tags and important governance considerations, refer to [Informational tags](./monitor-the-solution.html#informational-tags).
+