AWS solutions documentation change

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

File: solutions/latest/instance-scheduler-on-aws/troubleshooting.md

Summary

Added troubleshooting section for 'Unexpected API costs from informational tagging' explaining how tag governance policies can cause high costs and providing resolution guidance

Security assessment

This change addresses cost optimization and operational efficiency issues related to AWS Resource Groups Tagging API calls and AWS Config evaluations. While it mentions tag governance policies, it doesn't discuss security vulnerabilities, access control, or data protection. The focus is on cost management and policy compliance rather than security features or vulnerabilities.

Diff

diff --git a/solutions/latest/instance-scheduler-on-aws/troubleshooting.md b/solutions/latest/instance-scheduler-on-aws/troubleshooting.md
index cc1992b32..c94cef64b 100644
--- a//solutions/latest/instance-scheduler-on-aws/troubleshooting.md
+++ b//solutions/latest/instance-scheduler-on-aws/troubleshooting.md
@@ -80,0 +81,10 @@ Refer to [Encrypted EC2 EBS Volumes](./security-1.html#encrypted-ec2-ebs-volumes
+### Problem: Unexpected API costs from informational tagging
+
+Unexpectedly high costs from AWS Resource Groups Tagging API calls, AWS Config evaluations, or related remediation actions.
+
+### Resolution
+
+Instance Scheduler writes [informational tags](./monitor-the-solution.html#informational-tags) to managed resources on each scheduling interval. If your environment enforces tag governance through AWS Config rules, tag policies, or automated remediation, ensure that Instance Scheduler’s tag keys are permitted. For the full list of tag keys and configuration guidance, refer to [Tag governance considerations](./monitor-the-solution.html#informational-tag-conflict-with-tag-policies).
+
+If you are unable to update your tag governance policies, disable informational tagging by setting the **Enable informational tagging** parameter to `No` on the hub stack.
+