generated from amazon-archives/__template_Apache-2.0
-
Notifications
You must be signed in to change notification settings - Fork 37
feat: add EKS MCP server example #433
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
clareliguori
reviewed
Sep 8, 2025
Co-authored-by: Clare Liguori <[email protected]>
Co-authored-by: Clare Liguori <[email protected]>
Co-authored-by: Clare Liguori <[email protected]>
Co-authored-by: Clare Liguori <[email protected]>
Co-authored-by: Clare Liguori <[email protected]>
Co-authored-by: Clare Liguori <[email protected]>
- Uncomment CommandHooks and bundling for local testing - Update Python runtime to 3.13 - Add timeout configuration (10 seconds) - Update environment variables with LOG_LEVEL=DEBUG - Change region to us-west-2 - Enable AwsSolutionsChecks - Update dependencies to latest versions from book-search - Remove debug print statements - Update function requirements with proper PyPi comments
- Remove duplicate comments and dependencies - Keep proper PyPI usage comments as suggested by maintainer
- Remove MockClientContext class as suggested by maintainer - Construct client context directly for local development - Addresses maintainer feedback about context construction
- Remove Function URL and CfnOutput since this example is for AgentCore Gateway - Addresses maintainer feedback to remove Function URL configuration
- Add clear comments explaining why additional permissions are needed - Specify that EKS permissions are for MCP server operations not covered by managed policies - Clarify EC2 permissions are required for Lambda VPC access to EKS clusters - Addresses maintainer question about permission redundancy
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
Description of changes:
Add Amazon EKS MCP server example. This example contains the Amazon EKS MCP Server deployed as an AWS Lambda function for integration with Bedrock AgentCore Gateway.
The EKS MCP server implementation is available at awslabs/mcp/eks-mcp-server
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.