{"id":94763,"date":"2026-10-08T16:32:30","date_gmt":"2026-10-08T14:32:30","guid":{"rendered":"https:\/\/www.skaylink.com\/?p=94763"},"modified":"2026-10-08T16:32:30","modified_gmt":"2026-10-08T14:32:30","slug":"getting-started-with-aws-agentcore","status":"publish","type":"post","link":"https:\/\/www.skaylink.com\/en\/insights\/blog\/getting-started-with-aws-agentcore\/","title":{"rendered":"Getting started with AWS AgentCore"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Home<\/a><\/span><\/span><\/p>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"\"\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Blog<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t

Getting started with AWS AgentCore<\/h1>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\tLearn how to develop, deploy, and test a scalable AI agent using AWS AgentCore and Terraform.\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t
\n\t\t\t\t\t
\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\tOctober 8, 2026\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\t\t\"Picture\n\t\t\t\t<\/div>\n\t\t\t\n\t\t\t
\n\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\n\t\t\t\t\t\t\tClaudia M\u00fcller\t\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/div>\n\t\t\t\t\n\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t

Senior AWS Consultant<\/p>\n\t\t\t\t\t<\/div>\n\t\t\t\t\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\n\t\t\t
\n\t\t\t\t\n\t\t\t\t\n\t\t\t\t\t\t\t<\/div>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

What is an AI Agent?<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

An AI agent is a program that uses a large language model (LLM) not just to answer questions, but to take actions<\/strong>. Instead of generating text and stopping, an agent can decide to call external functions \u2014 query a database, fetch a file, call an API \u2014 and then use the results to formulate its final answer.<\/p>

The basic loop looks like this:<\/p>

  1. User sends a question.<\/li>
  2. The LLM reads the question and the list of available tools.<\/li>
  3. The LLM decides: can I answer directly, or do I need to call a tool first?<\/li>
  4. If it calls a tool, it receives the tool’s output and continues reasoning.<\/li>
  5. Steps 3\u20134 repeat until the LLM has enough information to respond.<\/li>
  6. The LLM produces a final answer for the user.<\/li><\/ol>

    This “reason \u2192 act \u2192 observe \u2192 repeat” loop is what separates an agent from a simple chatbot. The LLM becomes the decision-maker that orchestrates tool calls autonomously.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

    \n\t\t\t\t
    \n\t\t\t\t\t

    AgentCore vs Bedrock Agents: Why a New Service?<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
    \n\t\t\t\t
    \n\t\t\t\t\t\t\t\t\t

    AWS is retiring Bedrock Agents<\/strong>, which was already a fully managed agent service where you configure tools via the console, attach action groups, and AWS handles orchestration. So why a new service? Bedrock Agents works well for standard use cases, but the orchestration logic is a black box. You can’t change how the agent loops, which framework it uses, or how tools are routed.<\/p>

    Bedrock AgentCore<\/strong> is the infrastructure layer underneath. It gives you:<\/p>

    • Your own container<\/strong> \u2014 run any agent framework (Strands, LangChain, CrewAI, or custom code)<\/li>
    • Full orchestration control<\/strong> \u2014 custom hooks, iteration limits, short-circuit logic, anything<\/li>
    • MCP protocol for tools<\/strong> \u2014 the open Model Context Protocol standard, not a proprietary format<\/li>
    • Managed compute<\/strong> \u2014 you don’t run servers; AWS scales the containers for you<\/li><\/ul>

      \u00a0<\/p><\/td>

      Bedrock Agents<\/p><\/td>

      Bedrock AgentCore<\/p><\/td><\/tr>

      Orchestration<\/strong><\/p><\/td>

      AWS-managed (fixed)<\/p><\/td>

      Your code, any framework<\/p><\/td><\/tr>

      Tool protocol<\/strong><\/p><\/td>

      Action Groups (OpenAPI)<\/p><\/td>

      MCP (open standard)<\/p><\/td><\/tr>

      Deployment<\/strong><\/p><\/td>

      Config-only (no container)<\/p><\/td>

      Your Docker image<\/p><\/td><\/tr>

      Customization<\/strong><\/p><\/td>

      Console knobs<\/p><\/td>

      Unlimited \u2014 it’s your code<\/p><\/td><\/tr><\/tbody><\/table>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

      \n\t\t\t\t
      \n\t\t\t\t\t

      AgentCore Components Explained<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
      \n\t\t\t\t
      \n\t\t\t\t\t\t\t\t\t

      AgentCore might look overwhelming with all it’s different parts, so here I’m just focusing on the bare minimum of resources you need to get an agent up and running. AgentCore has three core components. Understanding what each one does (and doesn’t do) is the key to getting your first agent running.<\/p>

      1. The Runtime<\/strong><\/li><\/ol>

        The Runtime<\/strong> is your Docker container running on AWS-managed compute. It’s where your agent logic lives \u2014 the Python code, the LLM calls, the orchestration loop.<\/p>

        Think of it as a Fargate task that AWS manages for you: it pulls your image from ECR, starts the container, and routes incoming invocations to it. You don’t manage instances, scaling, or networking (unless you choose VPC mode for private resources).<\/p>

        What it does:<\/strong><\/p>

        • Runs your agent code (any language, any framework)<\/li>
        • Receives invocations via the invoke-agent-runtime API (IAM-authenticated)<\/li>
        • Has an IAM role that lets it call Bedrock (for the LLM) and the Gateway (for tools)<\/li><\/ul>

          What it doesn’t do:<\/strong><\/p>

          • It doesn’t decide which tools to call \u2014 that’s your LLM<\/li>
          • It doesn’t route tool calls \u2014 that’s the Gateway<\/li>
          • It doesn’t execute tools \u2014 that’s the tool backend (Lambda, an API, or another service)<\/li><\/ul>

            Configuration that matters:<\/strong><\/p>

            • server_protocol = “HTTP” \u2014 your container is an HTTP server, not an MCP server<\/li>
            • network_mode = “PUBLIC” \u2014 AWS handles outbound internet; use “VPC” only if you need private network access<\/li>
            • Container must be ARM64 architecture<\/li><\/ul>
              1. The Gateway<\/strong><\/li><\/ol>

                The Gateway<\/strong> is an MCP (Model Context Protocol) endpoint that routes tool calls from your Runtime to the backends that execute them. It’s the router between “the LLM decided to call a tool” and “the tool actually runs.”<\/p>

                When your agent’s MCP client sends a tool call, the Gateway:<\/p>

                1. Verifies the request (AWS_IAM SigV4 authentication)<\/li>
                2. Looks up which target matches the tool name<\/li>
                3. Invokes that target’s backend with the tool’s parameters<\/li>
                4. Returns the response back to your agent<\/li><\/ol>

                  What it does:<\/strong><\/p>

                  • MCP protocol endpoint (tool discovery + tool execution)<\/li>
                  • Routes each tool name to the correct backend (Lambda, an external MCP server, or other AWS services)<\/li>
                  • Authenticates every request using IAM<\/li><\/ul>

                    What it doesn’t do:<\/strong><\/p>

                    • It doesn’t decide which tool to call \u2014 that’s the LLM<\/li>
                    • It doesn’t run tool logic \u2014 that’s whatever backend the target points to<\/li>
                    • It has no knowledge of your agent’s conversation or state<\/li><\/ul>
                      1. Gateway Targets<\/strong><\/li><\/ol>

                        A Gateway Target<\/strong> is the binding between a tool name and a backend that executes it. For each tool you want your agent to use, you create one target that says: “when the MCP client calls tool X, route it to backend Y.”<\/p>

                        The backend doesn’t have to be a Lambda function, Gateway Targets support multiple target types. Lambda is the most common for custom logic, but you can also point targets at other MCP-compatible endpoints or AWS services. In this tutorial we use Lambda because it’s the simplest way to run custom code without managing servers, but keep in mind that the Gateway is a generic MCP router, not a Lambda-specific feature.<\/p>

                        Each target includes a tool schema<\/strong> \u2014 the name, description, and input parameters that get advertised to the LLM. When your agent calls list_tools_sync(), it receives these schemas, and that’s how the LLM knows what tools are available and what they do.<\/p>

                        Pattern for Lambda targets:<\/strong> one Lambda, many aliases, many targets. You don’t need a separate Lambda per tool \u2014 use aliases (alias name = tool name) and dispatch inside the handler.<\/p>

                        What We’re Building in this Tutorial<\/strong><\/p>

                        A minimal agent that:<\/p>

                        • Runs Claude Sonnet in a container managed by AgentCore<\/li>
                        • Has one MCP tool (GetCakeRecipe) backed by a Lambda function<\/li>
                        • Deploys entirely via terraform apply<\/li><\/ul>

                          Ask it “Can you give me a cake recipe?”<\/em> and it calls the tool, gets a Schwarzw\u00e4lder Kirschtorte recipe, and formats the answer. Ask it anything else and it answers from its own knowledge without calling the tool.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

                          \n\t\t\t\t
                          \n\t\t\t\t\t

                          Architecture<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
                          \n\t\t\t\t
                          \n\t\t\t\t\t\t\t
                          \n\t\t\t
                          \n\t\t\t\t\n\t\t\t\t\tinvoke-agent-runtime (AWS API, SigV4-signed)\r\n        \u2502\r\n        \u25bc\r\nAgentCore Runtime (your Docker container)\r\n  \u2514\u2500 Strands Agent + Claude Sonnet via Bedrock\r\n        \u2502\r\n        \u2502  MCP over HTTPS (SigV4-signed automatically)\r\n        \u25bc\r\nAgentCore Gateway (AWS_IAM auth, MCP protocol)\r\n        \u2502\r\n        \u2502  Invokes tool backend\r\n        \u25bc\r\nTool Backend (Lambda function in this example)\r\n  \u2514\u2500 Returns static recipe JSON\r\n<\/xmp>\n\t\t\t\t<\/code>\n\t\t\t<\/pre>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-bc3d832 elementor-widget elementor-widget-heading\" data-id=\"bc3d832\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">The Python Code in Detail<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-6f79db3b elementor-widget elementor-widget-text-editor\" data-id=\"6f79db3b\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<h4><strong>The Tool Function<\/strong><\/h4><p>The simplest possible tool receives whatever parameters the LLM passes and returns a JSON response:<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-fdb53ad elementor-widget elementor-widget-code-highlight\" data-id=\"fdb53ad\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"code-highlight.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t<div class=\"prismjs-default copy-to-clipboard \">\n\t\t\t<pre data-line=\"\" class=\"highlight-height language-javascript line-numbers\">\n\t\t\t\t<code readonly=\"true\" class=\"language-javascript\">\n\t\t\t\t\t<xmp># src\/lambda\/tool\/handler.py\r\ndef handler(event, context):\r\n    return {\r\n        \"status\": \"ok\",\r\n        \"recipe\": {\r\n            \"name\": \"Oma's Schwarzw\u00e4lder Kirschtorte\",\r\n            \"servings\": 12,\r\n            \"ingredients\": [\r\n                \"200g dark chocolate\", \"200g butter\", \"200g sugar\",\r\n                \"5 eggs\", \"150g flour\", \"2 tsp baking powder\",\r\n                \"500ml heavy cream\", \"3 tbsp kirsch (cherry brandy)\",\r\n                \"1 jar sour cherries (drained)\", \"chocolate shavings\",\r\n            ],\r\n            \"steps\": [\r\n                \"Melt chocolate and butter, let cool.\",\r\n                \"Beat eggs and sugar until fluffy, fold in chocolate.\",\r\n                \"Fold in flour + baking powder. Bake 175\u00b0C, 25 min.\",\r\n                \"Slice into 3 layers. Whip cream with kirsch.\",\r\n                \"Layer: cake, cream, cherries. Repeat. Decorate.\",\r\n            ],\r\n        },\r\n    }\r\n<\/xmp>\n\t\t\t\t<\/code>\n\t\t\t<\/pre>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-48f51442 elementor-widget elementor-widget-text-editor\" data-id=\"48f51442\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>In a real agent, this function would query a database, call an API, or do anything you need. We use a Lambda function here because it&#8217;s the simplest serverless option, but Gateway Targets can also point to other backends. The contract is the same regardless: receive parameters, return JSON.<\/p><h4><strong>The Agent Container (app.py)<\/strong><\/h4><p>This is the brain. Let&#8217;s walk through each piece:<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-66e7e0d elementor-widget elementor-widget-code-highlight\" data-id=\"66e7e0d\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"code-highlight.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t<div class=\"prismjs-default copy-to-clipboard \">\n\t\t\t<pre data-line=\"\" class=\"highlight-height language-javascript line-numbers\">\n\t\t\t\t<code readonly=\"true\" class=\"language-javascript\">\n\t\t\t\t\t<xmp>app = BedrockAgentCoreApp()\r\n_agent = None\r\n<\/xmp>\n\t\t\t\t<\/code>\n\t\t\t<\/pre>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-5070ae9c elementor-widget elementor-widget-text-editor\" data-id=\"5070ae9c\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>The app is the HTTP server AgentCore talks to. The _agent is cached globally so we don&#8217;t rebuild it (and re-discover tools) on every invocation \u2014 the agent&#8217;s MCP connection persists across requests within the same container lifetime.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-8c8da16 elementor-widget elementor-widget-code-highlight\" data-id=\"8c8da16\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"code-highlight.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t<div class=\"prismjs-default copy-to-clipboard \">\n\t\t\t<pre data-line=\"\" class=\"highlight-height language-javascript line-numbers\">\n\t\t\t\t<code readonly=\"true\" class=\"language-javascript\">\n\t\t\t\t\t<xmp>def _get_agent():\r\n    global _agent\r\n    if _agent is not None:\r\n        return _agent\r\n\r\n    mcp_tools = []\r\n    if GATEWAY_URL:\r\n        mcp = MCPClient(lambda: aws_iam_streamablehttp_client(\r\n            endpoint=GATEWAY_URL,\r\n            aws_region=AWS_REGION,\r\n            aws_service=\"bedrock-agentcore\",\r\n        ))\r\n        mcp.start()\r\n        mcp_tools = list(mcp.list_tools_sync())\r\n\r\n    _agent = Agent(\r\n        model=model,\r\n        tools=mcp_tools,\r\n        system_prompt=\"You are a helpful assistant. Use the GetCakeRecipe tool when the user asks for a recipe.\",\r\n    )\r\n    return _agent\r\n<\/xmp>\n\t\t\t\t<\/code>\n\t\t\t<\/pre>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-19c72d3f elementor-widget elementor-widget-text-editor\" data-id=\"19c72d3f\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>MCPClient takes a factory function (the lambda:) that creates the transport connection. This is lazy \u2014 the actual HTTPS connection to the Gateway is only established when mcp.start() is called.<\/p><p>mcp.start() opens the connection and keeps it alive for subsequent calls.<\/p><p>mcp.list_tools_sync() asks the Gateway &#8220;what tools do you have?&#8221; and gets back the tool schemas you defined in Terraform. This is how the agent discovers tools dynamically \u2014 add a new tool in Terraform, and the agent picks it up on next startup without a code change.<\/p><p>Agent(&#8230;) wires everything together: the LLM (model), the available actions (tools), and the behavioral instructions (system_prompt). The system prompt tells the LLM <em>when<\/em> to use the tool \u2014 without it, the LLM might answer recipe questions from its own training data instead of calling GetCakeRecipe.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-7a86504 elementor-widget elementor-widget-code-highlight\" data-id=\"7a86504\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"code-highlight.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t<div class=\"prismjs-default copy-to-clipboard \">\n\t\t\t<pre data-line=\"\" class=\"highlight-height language-javascript line-numbers\">\n\t\t\t\t<code readonly=\"true\" class=\"language-javascript\">\n\t\t\t\t\t<xmp>@app.entrypoint\r\ndef invoke_agent(payload: dict):\r\n    prompt = payload.get(\"prompt\", \"\")\r\n    agent = _get_agent()\r\n    result = agent(prompt)\r\n    return {\"result\": str(result)}\r\n<\/xmp>\n\t\t\t\t<\/code>\n\t\t\t<\/pre>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-de21afc elementor-widget elementor-widget-text-editor\" data-id=\"de21afc\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>@app.entrypoint registers this function as the handler for incoming invocations. When someone calls invoke-agent-runtime, AgentCore delivers the payload here.<\/p><p>agent(prompt) \u2014 this single line triggers the full agent loop:<\/p><ol><li>The prompt is sent to Claude along with the tool schemas<\/li><li>Claude decides whether to call GetCakeRecipe or answer directly<\/li><li>If it calls the tool, the MCP client sends the request to the Gateway, the Gateway invokes the tool backend, and the result comes back<\/li><li>Claude sees the tool result and formulates its final answer<\/li><li>The result object contains the final text<\/li><\/ol><h4><strong>Dockerfile<\/strong><\/h4>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-53534d5 elementor-widget elementor-widget-code-highlight\" data-id=\"53534d5\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"code-highlight.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t<div class=\"prismjs-default copy-to-clipboard \">\n\t\t\t<pre data-line=\"\" class=\"highlight-height language-javascript line-numbers\">\n\t\t\t\t<code readonly=\"true\" class=\"language-javascript\">\n\t\t\t\t\t<xmp>FROM python:3.12-slim\r\nWORKDIR \/app\r\nRUN apt-get update && apt-get install -y --no-install-recommends gcc g++ \\\r\n    && rm -rf \/var\/lib\/apt\/lists\/*\r\nCOPY requirements.txt .\r\nRUN pip install --no-cache-dir -r requirements.txt\r\nCOPY app.py .\r\nEXPOSE 8080\r\nCMD [\"python\", \"app.py\"]\r\n<\/xmp>\n\t\t\t\t<\/code>\n\t\t\t<\/pre>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-de4ce29 elementor-widget elementor-widget-text-editor\" data-id=\"de4ce29\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>gcc\/g++ are needed because some Python packages (cryptography, certain boto3 dependencies) compile C extensions. The image must be built for ARM64 \u2014 AgentCore doesn&#8217;t support x86.<\/p><h3><strong>The Terraform<\/strong><\/h3><h4><strong>IAM: Three Roles, Three Boundaries<\/strong><\/h4>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-fa69df4 elementor-widget elementor-widget-code-highlight\" data-id=\"fa69df4\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"code-highlight.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t<div class=\"prismjs-default copy-to-clipboard \">\n\t\t\t<pre data-line=\"\" class=\"highlight-height language-javascript line-numbers\">\n\t\t\t\t<code readonly=\"true\" class=\"language-javascript\">\n\t\t\t\t\t<xmp># Runtime role \u2014 AgentCore runs your container with this identity\r\nresource \"aws_iam_role\" \"runtime\" {\r\n  assume_role_policy = jsonencode({\r\n    Statement = [{ Principal = { Service = \"bedrock-agentcore.amazonaws.com\" }, ... }]\r\n  })\r\n}\r\n\r\n# Gateway role \u2014 AgentCore uses this to invoke your tool backends\r\nresource \"aws_iam_role\" \"gateway\" {\r\n  assume_role_policy = jsonencode({\r\n    Statement = [{ Principal = { Service = \"bedrock-agentcore.amazonaws.com\" }, ... }]\r\n  })\r\n}\r\n\r\n# Lambda role \u2014 execution role for our tool function (this example uses Lambda)\r\nresource \"aws_iam_role\" \"lambda\" {\r\n  assume_role_policy = jsonencode({\r\n    Statement = [{ Principal = { Service = \"lambda.amazonaws.com\" }, ... }]\r\n  })\r\n}\r\n<\/xmp>\n\t\t\t\t<\/code>\n\t\t\t<\/pre>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-7a26cb7 elementor-widget elementor-widget-text-editor\" data-id=\"7a26cb7\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>The Runtime role needs these permissions:<\/p><ul><li>bedrock:InvokeModel \u2014 call Claude<\/li><li>bedrock-agentcore:InvokeGateway \u2014 call the Gateway (THE ONE EVERYONE FORGETS)<\/li><li>ecr:BatchGetImage \u2014 pull the container image<\/li><li>logs:PutLogEvents \u2014 write CloudWatch logs<\/li><\/ul><p>The Gateway role needs:<\/p><ul><li>Permissions to invoke whatever backend your targets use (in this example: lambda:InvokeFunction)<\/li><\/ul><h4><strong>The Gateway and Tool Binding<\/strong><\/h4>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-433713a elementor-widget elementor-widget-code-highlight\" data-id=\"433713a\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"code-highlight.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t<div class=\"prismjs-default copy-to-clipboard \">\n\t\t\t<pre data-line=\"\" class=\"highlight-height language-javascript line-numbers\">\n\t\t\t\t<code readonly=\"true\" class=\"language-javascript\">\n\t\t\t\t\t<xmp>resource \"aws_bedrockagentcore_gateway\" \"main\" {\r\n  name            = \"myagent-gateway\"\r\n  role_arn        = aws_iam_role.gateway.arn\r\n  authorizer_type = \"AWS_IAM\"\r\n  protocol_type   = \"MCP\"\r\n}\r\n\r\nresource \"aws_lambda_alias\" \"get_cake_recipe\" {\r\n  name             = \"GetCakeRecipe\"\r\n  function_name    = aws_lambda_function.tool.function_name\r\n  function_version = \"$LATEST\"\r\n}\r\n\r\nresource \"aws_bedrockagentcore_gateway_target\" \"get_cake_recipe\" {\r\n  gateway_identifier = aws_bedrockagentcore_gateway.main.gateway_id\r\n  target_configuration {\r\n    mcp {\r\n      lambda {\r\n        lambda_arn = aws_lambda_alias.get_cake_recipe.arn\r\n        tool_schema {\r\n          inline_payload {\r\n            name        = \"GetCakeRecipe\"\r\n            description = \"Returns a cake recipe. Call this when the user asks about baking.\"\r\n            input_schema { type = \"object\" }\r\n          }\r\n        }\r\n      }\r\n    }\r\n  }\r\n}\r\n<\/xmp>\n\t\t\t\t<\/code>\n\t\t\t<\/pre>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-d69002a elementor-widget elementor-widget-text-editor\" data-id=\"d69002a\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>The description in tool_schema is what the LLM sees. Write it clearly \u2014 this is how Claude decides whether to call your tool. A vague description means the tool never gets used; an overly broad one means it gets called when it shouldn&#8217;t be.<\/p><h4><strong>The Runtime<\/strong><\/h4>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-ccc625d elementor-widget elementor-widget-code-highlight\" data-id=\"ccc625d\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"code-highlight.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t<div class=\"prismjs-default copy-to-clipboard \">\n\t\t\t<pre data-line=\"\" class=\"highlight-height language-javascript line-numbers\">\n\t\t\t\t<code readonly=\"true\" class=\"language-javascript\">\n\t\t\t\t\t<xmp>resource \"aws_bedrockagentcore_agent_runtime\" \"main\" {\r\n  agent_runtime_name = \"myagent_runtime\"\r\n  agent_runtime_artifact {\r\n    container_configuration {\r\n      container_uri = \"${aws_ecr_repository.agent.repository_url}:latest\"\r\n    }\r\n  }\r\n  role_arn = aws_iam_role.runtime.arn\r\n  protocol_configuration { server_protocol = \"HTTP\" }\r\n  network_configuration  { network_mode = \"PUBLIC\" }\r\n  environment_variables = {\r\n    MODEL_ID    = \"eu.anthropic.claude-sonnet-4-5-20250929-v1:0\"\r\n    AWS_REGION  = \"eu-central-1\"\r\n    GATEWAY_URL = aws_bedrockagentcore_gateway.main.gateway_url\r\n  }\r\n}<\/xmp>\n\t\t\t\t<\/code>\n\t\t\t<\/pre>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-11155a1 elementor-widget elementor-widget-text-editor\" data-id=\"11155a1\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>GATEWAY_URL is computed from the Gateway resource \u2014 Terraform wires them together automatically.<\/p><h3><strong>Deploy and Test<\/strong><\/h3>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-de73c6f elementor-widget elementor-widget-code-highlight\" data-id=\"de73c6f\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"code-highlight.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t<div class=\"prismjs-default copy-to-clipboard \">\n\t\t\t<pre data-line=\"\" class=\"highlight-height language-javascript line-numbers\">\n\t\t\t\t<code readonly=\"true\" class=\"language-javascript\">\n\t\t\t\t\t<xmp>terraform init && terraform apply<\/xmp>\n\t\t\t\t<\/code>\n\t\t\t<\/pre>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-50a8af7 elementor-widget elementor-widget-text-editor\" data-id=\"50a8af7\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>The Terraform includes a null_resource that builds the ARM64 Docker image and pushes it to ECR before creating the Runtime. One command, no manual steps.<\/p><p>After apply (2\u20133 minutes for the container to start):<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-dd198c5 elementor-widget elementor-widget-code-highlight\" data-id=\"dd198c5\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"code-highlight.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t<div class=\"prismjs-default copy-to-clipboard \">\n\t\t\t<pre data-line=\"\" class=\"highlight-height language-javascript line-numbers\">\n\t\t\t\t<code readonly=\"true\" class=\"language-javascript\">\n\t\t\t\t\t<xmp>aws bedrock-agentcore invoke-agent-runtime \\\r\n  --agent-runtime-arn \"$(terraform output -raw runtime_arn)\" \\\r\n  --payload '{\"prompt\": \"Give me a cake recipe\"}' \\\r\n  --content-type application\/json \\\r\n  \/dev\/stdout<\/xmp>\n\t\t\t\t<\/code>\n\t\t\t<\/pre>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-523af4f5 elementor-widget elementor-widget-heading\" data-id=\"523af4f5\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">Things That Will Bite You<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-edec8fa elementor-widget elementor-widget-text-editor\" data-id=\"edec8fa\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<ol><li><strong>Missing <\/strong>InvokeGateway permission. Agent works but never calls tools. No error in logs \u2014 the MCP client gets a silent 403. Add bedrock-agentcore:InvokeGateway to the Runtime role.<\/li><li>server_protocol = &#8220;MCP&#8221; on the Runtime. Your container speaks HTTP (BedrockAgentCoreApp is an HTTP server). MCP is only the protocol between Runtime \u2192 Gateway. Set &#8220;HTTP&#8221;.<\/li><li><strong>x86 container image.<\/strong> AgentCore only runs ARM64. You need &#8211;platform linux\/arm64 and QEMU\/buildx for cross-compilation on Intel\/AMD machines.<\/li><li><strong>Image not refreshing after push.<\/strong> AgentCore caches the pulled image. Change any environment variable to force a restart with the fresh image.<\/li><li><strong>VPC mode with no outbound route.<\/strong> network_mode = &#8220;VPC&#8221; requires the subnets to have internet access (NAT or VPC endpoints). Use &#8220;PUBLIC&#8221; unless you specifically need private network access.<\/li><\/ol>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-e24df0b elementor-widget elementor-widget-heading\" data-id=\"e24df0b\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"heading.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t<h2 class=\"elementor-heading-title elementor-size-default\">What You Can Build with This<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<div class=\"elementor-element elementor-element-f06f0b5 elementor-widget elementor-widget-text-editor\" data-id=\"f06f0b5\" data-element_type=\"widget\" data-e-type=\"widget\" data-widget_type=\"text-editor.default\">\n\t\t\t\t<div class=\"elementor-widget-container\">\n\t\t\t\t\t\t\t\t\t<p>The cake recipe is one tool returning static data. But the same architecture supports agents that reason across multiple tool calls to answer complex questions.<\/p><p>Consider a billing data assistant where a user asks: <em>&#8220;Which of my customers have unpaid invoices from last quarter, and what&#8217;s their total outstanding amount?&#8221;<\/em><\/p><p>No single database query answers that. The agent breaks it down:<\/p><ol><li>First it calls a tool that lists unpaid invoices filtered by date range<\/li><li>Then it calls a tool that aggregates amounts grouped by customer<\/li><li>It combines both results and presents a ranked list with totals<\/li><\/ol><p>The LLM decides this sequence on its own \u2014 you don&#8217;t hardcode the chain. You just provide the tools (each one a parameterized query) and a system prompt that describes when to use which. The agent figures out that answering the user&#8217;s question requires two steps, picks the right tool for each, passes the right parameters (date range, paid status filter), and synthesizes the results into one coherent answer.<\/p><p>Scale that to 10 or 15 tools covering different aspects of a database \u2014 customers, invoices, payments, revenue aggregations, full-text search \u2014 and the agent can answer almost any analytical question a business user throws at it.<\/p><p>That&#8217;s the jump from &#8220;one tool, one response&#8221; to a real production agent: the LLM becomes an autonomous query planner that chains multiple data retrievals together, each one scoped and parameterized, to answer questions that no single query could handle alone.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"<p>Learn how to develop, deploy, and test a scalable AI agent using AWS AgentCore and Terraform.<\/p>\n","protected":false},"author":23,"featured_media":94772,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[100],"tags":[182,168],"class_list":["post-94763","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","tag-ai-ml-2","tag-aws"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.skaylink.com\/en\/wp-json\/wp\/v2\/posts\/94763","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.skaylink.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.skaylink.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.skaylink.com\/en\/wp-json\/wp\/v2\/users\/23"}],"replies":[{"embeddable":true,"href":"https:\/\/www.skaylink.com\/en\/wp-json\/wp\/v2\/comments?post=94763"}],"version-history":[{"count":12,"href":"https:\/\/www.skaylink.com\/en\/wp-json\/wp\/v2\/posts\/94763\/revisions"}],"predecessor-version":[{"id":94782,"href":"https:\/\/www.skaylink.com\/en\/wp-json\/wp\/v2\/posts\/94763\/revisions\/94782"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.skaylink.com\/en\/wp-json\/wp\/v2\/media\/94772"}],"wp:attachment":[{"href":"https:\/\/www.skaylink.com\/en\/wp-json\/wp\/v2\/media?parent=94763"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.skaylink.com\/en\/wp-json\/wp\/v2\/categories?post=94763"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.skaylink.com\/en\/wp-json\/wp\/v2\/tags?post=94763"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}