AWS bedrock-agentcore high security documentation change
Summary
Restructured Google OAuth2 documentation, corrected region placeholder syntax in authorized domains and callback URL, fixed Google developer portal links, and updated configuration steps
Security assessment
The correction of the `region` placeholder syntax in authorized domains and callback URLs prevents potential misconfigurations that could break authentication flows. Fixed links to Google's official documentation ensure proper OAuth2 setup, reducing risks of insecure application configuration. The authorized domains requirement for bedrock-agentcore endpoints is crucial for security validation.
Diff
diff --git a/bedrock-agentcore/latest/devguide/identity-idp-google.md b/bedrock-agentcore/latest/devguide/identity-idp-google.md index 720ad67ab..3d510af2b 100644 --- a//bedrock-agentcore/latest/devguide/identity-idp-google.md +++ b//bedrock-agentcore/latest/devguide/identity-idp-google.md @@ -5,3 +5 @@ -Configuring a Google OAuth2 ApplicationOutbound - -Amazon Bedrock AgentCore is in preview release and is subject to change. +Outbound @@ -11 +9,3 @@ Amazon Bedrock AgentCore is in preview release and is subject to change. -You can set up Google as an outbound provider using Google OAuth 2.0. +Google can be configured as an AgentCore Identity credential provider for outbound resource access. This allows your agents to authenticate users through Google's OAuth2 service and obtain access tokens for Google API resources. + +## Outbound @@ -13 +13,3 @@ You can set up Google as an outbound provider using Google OAuth 2.0. -## Configuring a Google OAuth2 Application +**Step 1** + +Use the following procedure to set up a Google OAuth2 application and obtain the necessary client credentials for AgentCore Identity. @@ -17 +19 @@ You can set up Google as an outbound provider using Google OAuth 2.0. - 1. Create a [developer account with Google](https://docs.aws.amazon.com/https://developers.google.com/identity). + 1. Create a [developer account with Google](https://developers.google.com/identity). @@ -19 +21 @@ You can set up Google as an outbound provider using Google OAuth 2.0. - 2. Sign in to the [Google Cloud Platform console](https://docs.aws.amazon.com/https://console.cloud.google.com/home/dashboard). + 2. Sign in to the [Google Cloud Platform console](https://console.cloud.google.com/home/dashboard). @@ -29 +31 @@ You can set up Google as an outbound provider using Google OAuth 2.0. - 7. Enter the app information, an **App domain** , **Authorized domains** , and **Developer contact information**. Your **Authorized domains** must include `bedrock-agentcore.{region}.amazonaws.com`. Choose **SAVE AND CONTINUE**. + 7. Enter the app information, an **App domain** , **Authorized domains** , and **Developer contact information**. Your **Authorized domains** must include `bedrock-agentcore.`region`.amazonaws.com`. Choose **SAVE AND CONTINUE**. @@ -41 +43 @@ You can set up Google as an outbound provider using Google OAuth 2.0. - * `https://bedrock-agentcore.{region}.amazonaws.com/identities/oauth2/callback` + * `https://bedrock-agentcore.`region`.amazonaws.com/identities/oauth2/callback` @@ -50 +52 @@ You can set up Google as an outbound provider using Google OAuth 2.0. -## Outbound +**Step 2** @@ -74 +76 @@ GitHub -Salesforce +HubSpot