AWS bedrock-agentcore documentation change
Summary
Formatting changes (markdown header style) and typographical fixes (apostrophe style) in gateway debugging documentation
Security assessment
Changes are purely formatting (changing '######' headers to bold text) and typographical (apostrophe style). The security-relevant content about showing detailed error messages during debugging vs. generic errors in production remains unchanged. No new security information is added, and no security issues are addressed.
Diff
diff --git a/bedrock-agentcore/latest/devguide/gateway-debug-messages.md b/bedrock-agentcore/latest/devguide/gateway-debug-messages.md index 602fdc327..bd11107cd 100644 --- a//bedrock-agentcore/latest/devguide/gateway-debug-messages.md +++ b//bedrock-agentcore/latest/devguide/gateway-debug-messages.md @@ -11 +11 @@ While your gateway is in development, you can turn on debugging messages to retu -###### To turn on debugging messages, do one of the following: +**To turn on debugging messages, do one of the following:** @@ -22 +22 @@ While your gateway is in development, you can turn on debugging messages to retu -When you're done debugging your gateway, you can update the gateway to turn off debugging messages, such that the message to the end user only shows an unspecified internal error. +When you’re done debugging your gateway, you can update the gateway to turn off debugging messages, such that the message to the end user only shows an unspecified internal error. @@ -24 +24 @@ When you're done debugging your gateway, you can update the gateway to turn off -###### To turn off debugging messages, do one of the following: +**To turn off debugging messages, do one of the following:** @@ -35 +35 @@ When you're done debugging your gateway, you can update the gateway to turn off -As an example, suppose that the user doesn't have permissions to invoke a Lambda function that is targeted by the gateway. A request that calls this function would return a different message depending on whether debugging is on or off: +As an example, suppose that the user doesn’t have permissions to invoke a Lambda function that is targeted by the gateway. A request that calls this function would return a different message depending on whether debugging is on or off: @@ -37 +37 @@ As an example, suppose that the user doesn't have permissions to invoke a Lambda - * **Debugging on** – A detailed error message would be returned in the content's `text` field and also in the `_meta` field in the response, as in the following example: + * **Debugging on** – A detailed error message would be returned in the content’s `text` field and also in the `_meta` field in the response, as in the following example: @@ -59 +59 @@ As an example, suppose that the user doesn't have permissions to invoke a Lambda - * **Debugging off** – A generic error message would be returned in the content's `text` field in the response, as in the following example: + * **Debugging off** – A generic error message would be returned in the content’s `text` field in the response, as in the following example: