AWS imagebuilder: Add failure context links and rename Troubleshoot with AI section
Summary
Adds a table-of-contents entry and a cross-reference to the new 'Find the cause of a failed image build with failure context' page, and renames the 'Troubleshoot with AI' section heading to 'Failure context'.
Security assessment
The change only adds navigation links and renames a troubleshooting section heading; it describes build failure diagnostics, not any vulnerability, credential, or access-control concern.
Evidence
+A failed image also carries structured failure context that names the workflow step, component step, or distribution that caused the failure. For more information, see [Find the cause of a failed image build with failure context](./image-failure-context.html).
Diff
diff --git a/imagebuilder/latest/userguide/troubleshooting.md b/imagebuilder/latest/userguide/troubleshooting.md index 99fbb8d5c..9c708e92d 100644 --- a//imagebuilder/latest/userguide/troubleshooting.md +++ b//imagebuilder/latest/userguide/troubleshooting.md @@ -22,0 +23,2 @@ You can use the Troubleshoot feature, powered by AWS DevOps Agent, to diagnose f + * [Find the cause of a failed image build with failure context](./image-failure-context.html) + @@ -38,0 +41,2 @@ If an Image Builder pipeline build fails, Image Builder returns an error message +A failed image also carries structured failure context that names the workflow step, component step, or distribution that caused the failure. For more information, see [Find the cause of a failed image build with failure context](./image-failure-context.html). + @@ -247 +251 @@ Best practices -Troubleshoot with AI +Failure context