Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -391,7 +391,7 @@
"source": [
"#### 2.1 - Setup Cognito User Pool\n",
"\n",
"Before deploy agents, we have to set up a Cognito User Pool, so it can validate users that are accessing our agents.\n",
"Before deploy agents, we have to set up a Cognito User Pool, so it can validate users that are accessing our agents, or any other Idenitty provider like Okta, Microsoft Entra ID, etc.\n",
"\n",
"We're going to import a helper class, that has methods to simplify few steps in our workshop. This helper class will import methods responsible to create Cognito User Pool"
]
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -11,11 +11,13 @@
}
},
"source": [
"# MCPify your AWS Lambda\n",
"# MCPify your AWS Lambda with Gateway OAuth Inbound\n",
"## Transform AWS Lambda functions into secure MCP tools with Bedrock AgentCore Gateway\n",
"\n",
"## Overview\n",
"Bedrock AgentCore Gateway provides customers a way to turn their existing AWS Lambda functions into fully-managed MCP servers without needing to manage infra or hosting. Gateway will provide a uniform Model Context Protocol (MCP) interface across all these tools. Gateway employs a dual authentication model to ensure secure access control for both incoming requests and outbound connections to target resources. The framework consists of two key components: Inbound Auth, which validates and authorizes users attempting to access gateway targets, and Outbound Auth, which enables the gateway to securely connect to backend resources on behalf of authenticated users. Gateways uses IAM role to authorize the calls to AWS Lambda functions for outb ound authorization.\n",
"Bedrock AgentCore Gateway provides customers a way to turn their existing AWS Lambda functions into fully-managed MCP servers without needing to manage infra or hosting. Gateway will provide a uniform Model Context Protocol (MCP) interface across all these tools. Gateway employs a dual authentication model to ensure secure access control for both incoming requests and outbound connections to target resources. The framework consists of two key components: Inbound Auth, which validates and authorizes users attempting to access gateway targets, and Outbound Auth, which enables the gateway to securely connect to backend resources on behalf of authenticated users. Gateways uses IAM role to authorize the calls to AWS Lambda functions for outbound authorization.\n",
"\n",
"In this example, we will demonstrate OAuth for inbound authorization and IAM roles for outbound authorization.\n",
"\n",
"![How does it work](images/lambda-iam-gateway.png)\n",
"\n",
Expand Down Expand Up @@ -482,7 +484,7 @@
],
"metadata": {
"kernelspec": {
"display_name": "Python 3 (ipykernel)",
"display_name": ".env",
"language": "python",
"name": "python3"
},
Expand All @@ -496,7 +498,7 @@
"name": "python",
"nbconvert_exporter": "python",
"pygments_lexer": "ipython3",
"version": "3.12.9"
"version": "3.13.7"
}
},
"nbformat": 4,
Expand Down
Loading
Loading