docs: address feedback and improve Runtime/Gateway documentation #163

sundargthb · 2025-09-10T15:07:35Z

Add explicit region configuration guidance

Clarify ARM64 requirements and rationale
Restructure Gateway quickstart with numbered steps
Add Console resource links for better navigation
Document uv as recommended package manager
Create troubleshooting guide for common issues
Improve CDK integration documentation

Type of Change

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
Documentation update
Performance improvement
Code refactoring

Testing

[x ] Unit tests pass locally
[x ] Integration tests pass (if applicable)
[x ] Test coverage remains above 80%
[ x] Manual testing completed

Checklist

[x ] My code follows the project's style guidelines (ruff/pre-commit)
[x ] I have performed a self-review of my own code
[x ] I have commented my code, particularly in hard-to-understand areas
[x ] I have made corresponding changes to the documentation
[x ] My changes generate no new warnings
[x ] I have added tests that prove my fix is effective or that my feature works
[ x] New and existing unit tests pass locally with my changes
[x ] Any dependent changes have been merged and published

Security Checklist

[x ] No hardcoded secrets or credentials
[x ] No new security warnings from bandit
[x ] Dependencies are from trusted sources
[x ] No sensitive data logged

Breaking Changes

List any breaking changes and migration instructions:

N/A

Additional Notes

Add any additional notes or context about the PR here.

…d explicit region configuration guidance - Clarify ARM64 requirements and rationale - Restructure Gateway quickstart with numbered steps - Add Console resource links for better navigation - Document uv as recommended package manager - Create troubleshooting guide for common issues - Improve CDK integration documentation

siwachabhi · 2025-09-10T15:24:22Z

documentation/docs/api-reference/cli.md


 The `agentcore` CLI provides commands for configuring, launching, managing agents, and working with gateways.

+## Recent Improvements


this is duplicate I think, commit log would already give this info

i am good removing this - thought we should let the users know about the recent improvement we have made in the docs

siwachabhi · 2025-09-10T15:24:47Z

documentation/docs/api-reference/cli.md


 - `--user-id, -u TEXT`: User ID for authorization flows

+**Enhanced Output:**


Lets just call it example outputs

siwachabhi · 2025-09-10T15:25:14Z

documentation/docs/user-guide/gateway/quickstart.md

@@ -1,528 +1,247 @@
 # QuickStart: A Fully Managed MCP Server in 5 Minutes! 🚀

-Amazon Bedrock AgentCore Gateway provides an easy and secure way for developers to build, deploy, discover, and connect to tools at scale. AI agents need tools to perform real-world tasks—from querying databases to sending messages to analyzing documents. With Gateway, developers can convert APIs, Lambda functions, and existing services into Model Context Protocol (MCP)-compatible tools and make them available to agents through Gateway endpoints with just a few lines of code. Gateway supports OpenAPI, Smithy, and Lambda as input types, and is the only solution that provides both comprehensive ingress authentication and egress authentication in a fully-managed service. Gateway eliminates weeks of custom code development, infrastructure provisioning, and security implementation so developers can focus on building innovative agent applications.


This was specifically added by Nick, lets confirm before changing

I have not changed the content - just converted them into bullet points based on workshop feedback

siwachabhi · 2025-09-10T15:25:50Z

documentation/docs/user-guide/runtime/permissions.md

+}
+```

-### What Gets Auto-Created


we should keep this what get auto created

siwachabhi · 2025-09-10T15:26:22Z

documentation/docs/user-guide/runtime/quickstart.md

- **AWS Account** with credentials configured (`aws configure`)
+- **AWS Account** with credentials configured  in your desired region (`aws configure`)
 - **Python 3.10+** installed
- **AWS Permissions**:


this is important, lets not remove it

siwachabhi · 2025-09-10T15:26:47Z

documentation/docs/user-guide/runtime/quickstart.md

+curl -LsSf https://astral.sh/uv/install.sh | sh
+
+# Clone and install
+git clone https://github.com/aws/bedrock-agentcore-starter-toolkit.git


why git clone?

siwachabhi · 2025-09-10T16:47:22Z

documentation/docs/user-guide/runtime/quickstart.md

+⚠️ **Important**: AgentCore Runtime requires ARM64 architecture containers. This is because:
+- Runtime uses AWS Graviton processors for cost-efficiency and performance
+- All containers must be built for `linux/arm64` platform
+- Local development on x86 machines requires Docker buildx or CodeBuild deployment


lets clarify launch uses code build by default, and move docker buildx to after

siwachabhi · 2025-09-10T16:48:31Z

documentation/docs/user-guide/runtime/quickstart.md

-cat > requirements.txt << EOF
-bedrock-agentcore
-strands-agents
-EOF


when does user add these?

fixed this step.

siwachabhi · 2025-09-10T16:48:57Z

README.md

+
+```bash
+# Clone the repository
+git clone https://github.com/aws/bedrock-agentcore-starter-toolkit.git


why git clone?

removed this.

siwachabhi · 2025-09-10T16:49:23Z

README.md

+pip install -e .
+```
+
+### About Package Management


should this move to contributions.md?

000-000-000-000-000 · 2025-09-10T18:58:53Z

documentation/docs/user-guide/gateway/quickstart.md

+### Step 3: Deploy and Test
+
+```bash
+# Deploy the agent with Gateway integration
+agentcore configure --entrypoint weather_agent.py
+agentcore launch
+
+# Test the integration
+agentcore invoke '{"prompt": "What is the weather in Seattle?"}'


why do i now need to do this via CLI..? Ideally I should not.

removed the CLI - it was a mistake. please check again

000-000-000-000-000 · 2025-09-10T18:59:55Z

documentation/docs/user-guide/gateway/quickstart.md

+```bash
+# List resources
+agentcore status
+
+# Remove specific agent
+agentcore destroy --agent weather-agent
+
+# Clean up Gateway (via console or SDK)
+# Note: Cognito resources may need manual cleanup


what is this doing? we should just include this in the python.

removed this section

000-000-000-000-000 · 2025-09-10T19:00:12Z

documentation/docs/user-guide/gateway/quickstart.md

+
+## Best Practices
+
+1. **Same Region**: Deploy Gateway and Runtime in the same region


Why are we talking about Runtime here? Remove this please

removed references to Runtime

000-000-000-000-000 · 2025-09-10T19:00:39Z

documentation/docs/user-guide/gateway/quickstart.md

+# Deploy the agent with Gateway integration
+agentcore configure --entrypoint weather_agent.py
+agentcore launch


Remove this please. We should not include anything about AgentCore Runtime in this guide.

removed references to Runtime

000-000-000-000-000 · 2025-09-10T19:01:23Z

documentation/docs/user-guide/gateway/quickstart.md

+- Completed [Runtime QuickStart](../runtime/quickstart.md)
+- Agent deployed and running



remove this.

removed references to Runtime

000-000-000-000-000 · 2025-09-10T19:02:51Z

documentation/docs/user-guide/gateway/quickstart.md

-Amazon Bedrock AgentCore Gateway provides an easy and secure way for developers to build, deploy, discover, and connect to tools at scale. AI agents need tools to perform real-world tasks—from querying databases to sending messages to analyzing documents. With Gateway, developers can convert APIs, Lambda functions, and existing services into Model Context Protocol (MCP)-compatible tools and make them available to agents through Gateway endpoints with just a few lines of code. Gateway supports OpenAPI, Smithy, and Lambda as input types, and is the only solution that provides both comprehensive ingress authentication and egress authentication in a fully-managed service. Gateway eliminates weeks of custom code development, infrastructure provisioning, and security implementation so developers can focus on building innovative agent applications.
+Amazon Bedrock AgentCore Gateway provides an easy and secure way for developers to build, deploy, discover, and connect to tools at scale.

-In the quick start guide you will learn how to set up a Gateway and integrate it into your agents using the AgentCore Starter Toolkit. You can find more comprehensive guides and examples [**here**](https://github.com/awslabs/amazon-bedrock-agentcore-samples/tree/main/01-tutorials/02-AgentCore-gateway).


why are we removing this?

siwachabhi · 2025-09-11T09:48:05Z

documentation/docs/user-guide/runtime/quickstart.md

-bedrock-agentcore
-strands-agents
-EOF
+echo "strands-agents" > requirements.txt


bedrock-agentcore should also be here

siwachabhi · 2025-09-11T09:48:47Z

documentation/docs/user-guide/runtime/quickstart.md


 ```bash
-# Configure and deploy (auto-creates all required resources)
-agentcore configure -e my_agent.py


lets use -e

siwachabhi · 2025-09-11T09:50:03Z

documentation/docs/user-guide/runtime/quickstart.md

+### LangGraph Example

-### Getting Help
+Create `langgraph_agent.py`:


Lets move this to a separate path, maybe in examples

created a new file under examples and moved both Langgraph and CrewAI there. Although we should advertise somewhere that we work seamlessly with other frameworks too - improves discoverability for this repo

siwachabhi · 2025-09-11T09:51:40Z

README.md

+pip install bedrock-agentcore-starter-toolkit
+```
+
+### Development Setup


should this got to contributions.md?

siwachabhi · 2025-09-11T09:55:29Z

documentation/docs/user-guide/runtime/quickstart.md

 mkdir agentcore-runtime-quickstart
 cd agentcore-runtime-quickstart
-python3 -m venv venv
-source venv/bin/activate
+uv venv
+source .venv/bin/activate  # On Windows: .venv\Scripts\activate
+
+# Install packages
+uv pip install bedrock-agentcore-starter-toolkit strands-agents


this can be simplified to:

uv init agentcore-runtime-quickstart && cd agentcore-runtime-quickstart

uv add bedrock-agentcore strands-agents

source .venv/bin/activate

agentecore configure -e main.py
agentcore launch
agentcore invoke "tell me a joke"

I think quick start should have a single path to start with, lets continue without uv and capture uv after initial e2e. and keep it very brief.

moved uv to advanced setup section.. removed the clutter in the Setup section

siwachabhi · 2025-09-11T09:56:57Z

documentation/docs/user-guide/runtime/quickstart.md

+# Setup project
+mkdir agentcore-runtime-quickstart
+cd agentcore-runtime-quickstart
+python3 -m venv venv


lets use .venv

…eadMe, added comprehensive Gateway examples

000-000-000-000-000 · 2025-09-11T18:57:25Z

documentation/docs/api-reference/cli.md

+Response:
+Your formatted response here
+```
+


question: do the Gateway CLI sections below this work?

000-000-000-000-000 · 2025-09-11T18:59:43Z

documentation/docs/user-guide/gateway/quickstart.md

+# IMPORTANT: Set your AWS region here
+REGION = "us-west-2"  # Change to your preferred region
+
+def fix_gateway_role_trust_policy(role_name, account_id, region):


suggestion: please make this part of the agentcore-starter-toolkit if it's needed. This should not be in quickstart guide.

000-000-000-000-000 · 2025-09-11T19:01:05Z

documentation/docs/user-guide/gateway/quickstart.md

+```bash
+# Delete Gateway and all resources
+aws bedrock-agentcore-control delete-gateway \
+    --gateway-identifier YOUR_GATEWAY_ID \
+    --region us-east-1
+
+# Delete Cognito pool (optional)
+aws cognito-idp delete-user-pool \
+    --user-pool-id YOUR_POOL_ID \
+    --region us-east-1


can we just do this as part of python as well given rest of guide is in python?

000-000-000-000-000 · 2025-09-11T19:01:48Z

documentation/docs/user-guide/gateway/quickstart.md

+def test_mcp_request(method, params=None):
+    """Test an MCP request"""
+    headers = {
+        "Authorization": f"Bearer {config['access_token']}",
+        "Content-Type": "application/json"
+    }
+
+    payload = {
+        "jsonrpc": "2.0",
+        "id": str(int(time.time())),
+        "method": method,
+        "params": params or {}
+    }
+
+    try:
+        response = requests.post(
+            config['gateway_url'],
+            headers=headers,
+            json=payload,
+            timeout=10
+        )
+
+        print(f"   Status: {response.status_code}")
+


issue: we should not be hand-crafting MCP requests. Ideally we should rely on SDK.

this was an optional diagnostic code that i had added.. i have removed this and updated the troubleshooting section

000-000-000-000-000 · 2025-09-11T19:02:13Z

documentation/docs/user-guide/gateway/quickstart.md

+# ============= TEST 2: Verify Gateway Role =============
+print("\\n" + "=" * 60)
+print("TEST 2: Gateway Execution Role")
+print("-" * 60)
+
+role_arn = config.get('gateway_role_arn', f"arn:aws:iam::{account_id}:role/AgentCoreGatewayExecutionRole")
+role_name = role_arn.split('/')[-1]
+
+try:
+    role = iam.get_role(RoleName=role_name)
+    print(f"✅ Role exists: {role_arn}")
+
+    # Check trust policy
+    trust_policy = role['Role']['AssumeRolePolicyDocument']
+    can_be_assumed = any(
+        stmt.get('Principal', {}).get('Service') == 'bedrock-agentcore.amazonaws.com'
+        for stmt in trust_policy['Statement']
+    )
+
+    if can_be_assumed:
+        print("✅ Role can be assumed by bedrock-agentcore")
+    else:
+        print("❌ Role cannot be assumed by bedrock-agentcore")
+
+    # Check attached policies
+    attached = iam.list_attached_role_policies(RoleName=role_name)
+    print(f"📋 Attached policies: {len(attached['AttachedPolicies'])}")
+    for policy in attached['AttachedPolicies']:
+        print(f"   • {policy['PolicyName']}")
+
+    # Check inline policies
+    inline = iam.list_role_policies(RoleName=role_name)
+    print(f"📋 Inline policies: {len(inline['PolicyNames'])}")
+    for policy_name in inline['PolicyNames']:
+        print(f"   • {policy_name}")
+
+        # Get policy details
+        policy_doc = iam.get_role_policy(RoleName=role_name, PolicyName=policy_name)
+        statements = policy_doc['PolicyDocument']['Statement']
+
+        # Check for Lambda invoke permission
+        has_lambda_invoke = any(
+            'lambda:InvokeFunction' in stmt.get('Action', []) or
+            'lambda:*' in stmt.get('Action', [])
+            for stmt in statements
+        )
+
+        if has_lambda_invoke:
+            print("     ✅ Has lambda:InvokeFunction permission")
+        else:
+            print("     ❌ Missing lambda:InvokeFunction permission")
+
+except Exception as e:
+    print(f"❌ Role error: {e}")


all this stuff should be in the toolkit itself!

Added setup_gateway.py for Gateway creation, OAuth setup, and testing... updated the quickstart documentation

000-000-000-000-000 · 2025-09-11T19:02:59Z

documentation/docs/user-guide/gateway/quickstart.md

+### AWS PrivateLink Support
+
+Gateway now supports private VPC connectivity:
+
+```python
+# Create VPC endpoint for private access
+# Service name: com.amazonaws.{region}.bedrock-agentcore.gateway
+
+# Example endpoint policy for OAuth-based Gateway
+vpc_endpoint_policy = {
+    "Statement": [{
+        "Principal": "*",  # Required for OAuth (non-SigV4) authentication
+        "Effect": "Allow",
+        "Action": "*",
+        "Resource": f"arn:aws:bedrock-agentcore:{REGION}::gateway/{gateway_id}"
+    }]
+}
+```
+


why is this in the quickstart? This seems like info that would come in advanced topics in the very end

good point - i can move this to the Advanced topic section

000-000-000-000-000 · 2025-09-11T19:03:55Z

documentation/docs/user-guide/gateway/quickstart.md

+        print(f"⚠️  Warning: Could not update role trust policy: {e}")
+        return False
+
+def main():


way way too much code here. Can we please figure out how to put code in the starter toolkit itself as needed so that the quickstart remains just a few lines of code?

moved these into toolkit

…umentation Add setup_gateway.py to simplify gateway creation to just 3 lines of code. Update quickstart.md with express setup path for new users. Add unit tests for the new functionality.

000-000-000-000-000 · 2025-09-12T02:34:44Z

src/bedrock_agentcore_starter_toolkit/operations/gateway/setup_gateway.py

+class QuickGateway:
+    """One-line Gateway setup for quickstart"""
+
+    def __init__(self, region="us-east-1"):
+        self.region = region
+        self.client = GatewayClient(region_name=region)
+        self.config_file = Path("gateway_config.json")


why are we creating a QuickGateway on top of Gateway which is already supposed to be quick start? can we just incorporate any improvements (like IAM permission fixes) in other one. Also please do not club together creating authorizer, gateway, and target. It makes things very amibguous to the user what is actually going on behind the scenes and makes it very hard to graduate to more sophisticated usage

Agreed - removed QuickGateway entirely. IAM fixes and all improvements now live directly in GatewayClient as methods. Users call individual steps explicitly.

000-000-000-000-000 · 2025-09-12T02:36:14Z

src/bedrock_agentcore_starter_toolkit/operations/gateway/setup_gateway.py

+        # Import here to avoid circular dependencies
+        from strands import Agent
+        from strands.models import BedrockModel
+        from strands.tools.mcp.mcp_client import MCPClient
+        from mcp.client.streamable_http import streamablehttp_client


not sure what circular deps this refers to -- we should import like normal. Also my suggestion would be to keep the non-gateway agent interactions in the quickstart (what we have today) so it is clear how gateway is used with an agent

Fixed - no circular deps existed anyway. Agent code now stays entirely in quickstart as example usage, not in the gateway library.

000-000-000-000-000 · 2025-09-12T02:36:25Z

src/bedrock_agentcore_starter_toolkit/operations/gateway/setup_gateway.py

+    def cleanup(self):
+        """Remove all resources"""
+        if not self.config_file.exists():


add this to the normal gateway client code.

Done - cleanup_gateway() is now a method in GatewayClient, not a separate class.

000-000-000-000-000 · 2025-09-12T02:36:38Z

src/bedrock_agentcore_starter_toolkit/operations/gateway/setup_gateway.py

+        except Exception as e:
+            print(f"    ⚠️ IAM role update failed: {str(e)}. Continuing with best effort.")
+
+    def test(self):  # pragma: no cover


why repeat this?

Removed - QuickGateway is gone, so no more duplicate code or coverage issues.

000-000-000-000-000 · 2025-09-12T02:38:42Z

documentation/docs/user-guide/gateway/quickstart.md

+# Create and test Gateway
+gateway = QuickGateway(region="us-west-2") # enter your preferred region
+gateway.create()    # Creates Gateway, Lambda tools, and OAuth
+gateway.test()      # Interactive agent chat
+# gateway.cleanup() # Run this when done to remove resources


this completely defeats the purpose of actually teaching the user what is going on. that is why we have the clear code that was deleted showing the steps to create authorizer, gateway, and target.

yea, which is why my original version had each step written in the quickstart to educate the users but it looked like wanted it moved to the toolkit. we have to choose - whether to keep the code in quickstart vs toolkit. #163 (comment)

#163 (comment)

Completely restructured - quickstart now shows each step explicitly (create authorizer → create gateway → fix IAM → add target). Users see and control every operation.

000-000-000-000-000 · 2025-09-12T02:40:13Z

documentation/docs/user-guide/gateway/quickstart.md

+
+<details>
+<summary>Advanced: AWS PrivateLink for VPC Connectivity</summary>
+
+Create private connection between your VPC and Gateway:
+
+```bash
+aws ec2 create-vpc-endpoint \
+    --vpc-id vpc-12345678 \
+    --service-name com.amazonaws.region.bedrock-agentcore.gateway
+```
+
+</details>
+


does this even belong in quickstart? Maybe at bottom of advanced section? also why we adding another details section instead details section?

its a small section where they can learn to add VPC if they chose to

000-000-000-000-000 · 2025-09-12T02:40:32Z

documentation/docs/user-guide/gateway/quickstart.md

 </details>
+
+
+## Learn More


No one will read to bottom to see these. These should be at top.

moved it up - there are links to samples, boto3 doc and developer guide anyway in the first 2 paragraphs.

000-000-000-000-000 · 2025-09-12T02:41:08Z

documentation/docs/user-guide/gateway/quickstart.md

+        action = event.get('action')
+
+        # Your business logic here
+        result = process_customer_data(customer_id, action)


does this code even work? We should only have code that actually functions here.

this was an existing code that wanted to showcase custom lambda tools. let me know if you want it removed for now

removed non-working placeholder code. All examples now tested and functional.

000-000-000-000-000 · 2025-09-12T02:41:20Z

documentation/docs/user-guide/gateway/quickstart.md

-Here is an example of a simple Lambda function that implements these tools.
-```python
-import json



why are we removing this...

Preserved - the working Lambda handler example is back in the quickstart, now showing actual implementation of get_weather and get_time tools

000-000-000-000-000 · 2025-09-12T02:42:49Z

documentation/docs/user-guide/gateway/quickstart.md

+### Invocation Logging
+
+Monitor all Gateway invocations with:
+
+- **CloudWatch Logs**: Real-time analysis at `/aws/bedrock-agentcore/gateways/{gateway-id}`
+- **Amazon S3**: Long-term storage
+- **Amazon Data Firehose**: Stream to analytics services
+


no idea what this means... we have not even shown how to set this up!

removed the feature announcement

…w to: Create a Strands agent with short-term and long-term memory Add Gateway integration with a calculator tool Deploy the agent to AgentCore Runtime Test memory persistence and tool usage

Signed-off-by: Sundar Raghavan <[email protected]>

sundargthb temporarily deployed to auto-approve September 10, 2025 15:07 — with GitHub Actions Inactive

sundargthb requested a review from siwachabhi September 10, 2025 15:08

siwachabhi reviewed Sep 10, 2025

View reviewed changes

docs: address feedback and improve Runtime/Gateway documentation

215b960

sundargthb temporarily deployed to auto-approve September 10, 2025 16:42 — with GitHub Actions Inactive

siwachabhi reviewed Sep 10, 2025

View reviewed changes

000-000-000-000-000 reviewed Sep 10, 2025

View reviewed changes

docs:address feedback from primtive owners

cd3575a

sundargthb temporarily deployed to auto-approve September 10, 2025 20:59 — with GitHub Actions Inactive

docs:address feedback from primtive owners

c281f2c

sundargthb temporarily deployed to auto-approve September 10, 2025 21:31 — with GitHub Actions Inactive

docs: add langgraph and crewai examples to runtime quickstart

27a38be

sundargthb temporarily deployed to auto-approve September 11, 2025 09:25 — with GitHub Actions Inactive

siwachabhi reviewed Sep 11, 2025

View reviewed changes

improvements: moved framework examples to examples folder, improved R…

92726d2

…eadMe, added comprehensive Gateway examples

sundargthb temporarily deployed to auto-approve September 11, 2025 17:54 — with GitHub Actions Inactive

siwachabhi approved these changes Sep 11, 2025

View reviewed changes

000-000-000-000-000 reviewed Sep 11, 2025

View reviewed changes

feat(gateway): Add QuickGateway setup class and update quickstart doc…

15f32b6

…umentation Add setup_gateway.py to simplify gateway creation to just 3 lines of code. Update quickstart.md with express setup path for new users. Add unit tests for the new functionality.

sundargthb temporarily deployed to auto-approve September 12, 2025 01:40 — with GitHub Actions Inactive

000-000-000-000-000 reviewed Sep 12, 2025

View reviewed changes

update GatewayClient, removed setup_gateway, updated quickstart

d9a809f

sundargthb temporarily deployed to auto-approve September 12, 2025 13:37 — with GitHub Actions Inactive

fix: minor formatting fix in quickstart

56a8d4e

sundargthb temporarily deployed to auto-approve September 12, 2025 13:52 — with GitHub Actions Inactive

Sundar Raghavan and others added 4 commits September 15, 2025 09:02

adds a comprehensive end-to-end quickstart guide that demonstrates ho…

b5dcc71

…w to: Create a Strands agent with short-term and long-term memory Add Gateway integration with a calculator tool Deploy the agent to AgentCore Runtime Test memory persistence and tool usage

Move quickstart guide to documentation-user guide folder

f435601

fix: updated Gateway quickstart per comments

edc9dbd

Merge branch 'main' into docs/feedback-improvements

d221309

Signed-off-by: Sundar Raghavan <[email protected]>

sundargthb temporarily deployed to auto-approve September 18, 2025 06:25 — with GitHub Actions Inactive

sundargthb merged commit a422708 into main Sep 18, 2025
16 checks passed


		The `agentcore` CLI provides commands for configuring, launching, managing agents, and working with gateways.

		## Recent Improvements


		- `--user-id, -u TEXT`: User ID for authorization flows

		Enhanced Output:

		@@ -1,528 +1,247 @@
		# QuickStart: A Fully Managed MCP Server in 5 Minutes! 🚀

		Amazon Bedrock AgentCore Gateway provides an easy and secure way for developers to build, deploy, discover, and connect to tools at scale. AI agents need tools to perform real-world tasks—from querying databases to sending messages to analyzing documents. With Gateway, developers can convert APIs, Lambda functions, and existing services into Model Context Protocol (MCP)-compatible tools and make them available to agents through Gateway endpoints with just a few lines of code. Gateway supports OpenAPI, Smithy, and Lambda as input types, and is the only solution that provides both comprehensive ingress authentication and egress authentication in a fully-managed service. Gateway eliminates weeks of custom code development, infrastructure provisioning, and security implementation so developers can focus on building innovative agent applications.


		## Best Practices

		1. Same Region: Deploy Gateway and Runtime in the same region

		- Completed [Runtime QuickStart](../runtime/quickstart.md)
		- Agent deployed and running

docs: address feedback and improve Runtime/Gateway documentation #163

docs: address feedback and improve Runtime/Gateway documentation #163

Uh oh!

Conversation

sundargthb commented Sep 10, 2025

Type of Change

Testing

Checklist

Security Checklist

Breaking Changes

Additional Notes

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!