Introduction In the part 1 of this article series, we introduced Amazon Bedrock AgentCore and specifically Amazon Bedrock AgentCore Gateway which transforms existing APIs and AWS Lambda functions into agent-ready tools, offering unified…

Sichere Programmierung dev.to 22.12.2025, 09:13 Uhr 3 Min. Lesezeit Cloud & IT-Enterprise

↗ Quelle (dev.to)

Reagiere als Erste:r — dein Feedback zählt!

STANDARD — Regulärer Patch-Zyklus ~3 Min. (549 W.)

Deep Tech

Amazon Bedrock AgentCore Gateway - Part 5 Add API Gateway REST API as a target for Amazon Bedrock AgentCore Gateway

Angriffsfläche

Enterprise IT / Cloud Infrastruktur

Exploit-Status

Geringe Ausnutzungswahrscheinlichkeit / Keine aktiven Kampagnen

Sofortmaßnahme

Asset-Inventar prüfen & Upstream-Advisory überwachen

Introduction

In the part 1 of this article series, we introduced Amazon Bedrock AgentCore and specifically Amazon Bedrock AgentCore Gateway which transforms existing APIs and AWS Lambda functions into agent-ready tools, offering unified access across protocols, including into Model Context Protocol (MCP), and runtime discovery. In the part 2 of the series, we used Amazon Bedrock AgentCore Gateway to convert the existing Amazon API Gateway REST API into MCP compatible tools and made it available to agents through Gateway endpoint. We also used Strands MCP Client to talk to this AgentCore Gateway endpoint. In the example we extracted Open API spec to transform the existing Amazon Gateway API REST API into MCP tools using Bedrock AgentCore Gateway, because AgentCore Gateway didn't support directly creating Amazon API Gateway REST API as target as of time of writing (only AWS Lambda was supported as an AWS internal service). This has now changed and this feature is supported:

Let's explore it in detail.

Adding API Gateway REST API as a target for Amazon Bedrock AgentCore Gateway

Let's expose the same Amazon Gateway REST API as we did in part 2.

Let's focus on the part of creating API Gateway REST API as a target type of AgentCore Gateway. We first need to give Target a name and optionally a description and select the existing API Gateway API and the stage:

Then all existing API operations will be displayed:

We select both GET HTTP methods to expose them as MCP tools (as we did in the part 2):

We are required to set a proper name (which will be MCP tool name). The full tool name will be exposed as the AgentCore Gateway target name and "__" and our selected tool name and is currently limited to 64 characters maximum. So please carefully select target and tool names as they are used by the search for the right MCP tool Please also set a proper tool description:

Please review part 2 how to set other parameters of the AgentCore Gateway as "API Key" of "Outbound Auth configurations" as they remain completely the same.

Before you create the AgentCore Gateway make sure that each your Amazon API Gateway operations/resource has at least one method response like this:

It even concerns operations that you don't want to expose as MCP tools. Otherwise, I've got an error message when creating an AgentCore Gateway target that Open API specification couldn’t be extracted from the Amazon API Gateway API because the path element doesn't contain response(s) value. All such operations are listed in the error message:

After having created API Gateway REST API as a target for Amazon Bedrock AgentCore Gateway, the target itself looks like this:

Conclusion

In this article, we explored how to create API Gateway REST API as a target for Amazon Bedrock AgentCore Gateway. I think it's a good add-on to the other target types as it allows us to create this type of target much quicker without extracting Open API specification of the API Gateway REST API. You can find more information about this feature in the official article Add an API Gateway REST API as a target for Amazon Bedrock AgentCore Gateway.

1. Sofort-Triage & Abwehrmaßnahmen

IR-PLAYBOOK-RCEHIGH

Schritte anzeigen

SOC Incident Playbook: Remote Code Execution (RCE) Defense

WAF MitigationSofort

Virtuelles Patchen am Reverse Proxy / WAF für gefährdete URL-Pfade und Payloads aktivieren.

SecRule REQUEST_URI "@rx ..." "id:1001,phase:1,deny,status:403"

Web Shell ScanSofort

Web-Root auf neu angelegte Scripts, anomal modifizierte Dateien und Persistence scannen.

find /var/www -type f -name "*.php" -mmin -120

Outbound FilteringSofort

Ausgehenden Datenverkehr (Reverse Shells zu unbekannten IPs/Ports) blockieren.

ss -tunp | grep -E ":(4444|1337|8080|9001)"

Vendor Patching

Hersteller-Update in Staging validieren und schnellstmöglich in Produktion ausrollen.

apt update && apt --only-upgrade install <pkg>

1-Click Detection Engineering: Multi-Dialect SIEM Rules5 Formate

Regeln anzeigen

Syntax validiert (0 Fehler)

title: Detect Exploitation - Amazon Bedrock AgentCore Gateway - Part 5 Add API Gateway REST API as a target for Amazon Bedrock AgentCore Gateway
id: 21723b39-eef9-429d-9e8d-b4262ce4018a
status: experimental
description: Automatisch generierte SIEM-Erkennungsregel basierend auf CTI Intelligence
references:
  - https://tsecurity.de/
author: iShareStuff CTI Automated Detection Engine
date: 2026-09-25
logsource:
  category: network_connection
  product: any
detection:
  selection:
      CommandLine|contains:
        - 'exploit'
  condition: selection
falsepositives:
  - Legitime administrative Zugriffe oder Penetrationstests
level: high
tags:
  - attack.initial_access

Syntax validiert (0 Fehler)

rule CTI_Threat_Indicator {
    meta:
        author = "iShareStuff CTI Automated Detection Engine"
        date = "2026-09-25"
        description = "YARA Signature for "
    strings:
        $str = "Amazon Bedrock AgentCore Gatew" ascii wide
    condition:
        any of them
}

Syntax validiert (0 Fehler)

index=security sourcetype IN ("cisco:asa", "pan:traffic", "zeek_conn", "suricata", "WinEventLog:Security")
("Amazon Bedrock AgentCore Gateway - Part ")
| stats count earliest(_time) as first_seen latest(_time) as last_seen by src_ip, dest_ip, dest_host, signature
| eval first_seen=strftime(first_seen, "%Y-%m-%d %H:%M:%S"), last_seen=strftime(last_seen, "%Y-%m-%d %H:%M:%S")
| sort - count

Syntax validiert (0 Fehler)

message: "*Amazon Bedrock AgentCore Gateway - Part *"

Syntax validiert (0 Fehler)

CommonSecurityLog
| where Message has "Amazon Bedrock AgentCore Gateway - Part "
| summarize EventCount = count(), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by SourceIP, DestinationIP, DestinationPort, Activity
| extend DetectionRule = "iShareStuff-CTI-Compiled"
| sort by EventCount desc

2. Cyber Threat Intelligence & Forensik

🎯

MITRE ATT&CK Matrix Navigator 14 Taktiken

Reconnaissance

Resource Development

Initial Access

Execution

Persistence

Privilege Escalation

Defense Evasion

Credential Access

Discovery

Lateral Movement

Collection

Command and Control

Exfiltration

Impact

💡 Tipp: Klicken Sie auf eine TTP, um Gegenmaßnahmen und SIEM-Erkennungsregeln anzuzeigen.Enterprise Matrix v14.1

🚀 Auf tsecurity.de entdecken

◀ VORHERIGER BEITRAG 2 Min

The two most important tools for HTML developers

Sichere Programmierung

NÄCHSTER BEITRAG 2 Min

2025.12.0

IT Security DownloadsWeiterlesen ▶

Blättern: Pfeiltasten [ ← ] [ → ] · Tasten j / k · mobil: Wischen

Fokus-Vektor:

Kognitive Analyse für identifizierte Bedrohung: Erhöhte Bedrohungslage im Bereich Amazon Bedrock AgentCore Gateway - Part .... Basierend auf 368k Vektor-Korrelationen werden sofortige Isolationsmaßnahmen für betroffene Endpunkte empfohlen.

🛡️ Angriffsfläche & Exposure

Netzwerk/Remote-Zugriff ohne Vorauthentifizierung möglich.

⚡ Empfohlene Sofortmaßnahmen

1. Perimeter-Inspektion: Relevante Portfreigaben und exponierte Endpunkte unverzüglich scannen.
2. Patch-Applikation: Hersteller-Hotfix einspielen oder betroffene Daemons in isolierte DMZ-Segmente überführen.
3. Telemetrie & EDR-Alerts: Prozessaufrufe und Child-Processes auf anomale Shell-Spawns überwachen.

🔗 Semantisch verwandte Zero-Days MariaDB 11.7 VEC

Schnell-Prompts für Analysten

⚠️ DEFANGED SANDBOX VIEW (tsecurity.de): Alle Netzwerkindikatoren und URLs wurden neutralisiert (2 Indikatoren entschärft). Nur zur defensiven Analyse!

Format: python

#!/usr/bin/env python3
# Exploit Title: PoC for Target
import socket, sys
target = '192[.]168[.]1[.]10'
url = 'hxxp://target[.]local/vuln'
s = socket.socket()
s.connect((target, 80))
s.send(b'GET / HTTP/1.1\r\nHost: target.local\r\n\r\n')

Auch interessante Nachrichten Amazon Bedrock AgentCore Gateway - Part 5 Add API Gateway REST API as a target for Amazon Bedrock AgentCore Gateway

Thematisch verwandte Begriffe: Amazon, Bedrock, AgentCore, Gateway · 6 Treffer

Sichere Programmierung DEV Community

Building a REST API Client with Java HttpClient + Jackson

vor 5 Tagen 📆 20.09.2026 um 07:43 Uhr

Weiterlesen ↗

Sicherheitslücken (CVE) KitPloit - PenTest Tools!

xalgorix v4.6.78

vor 5 Tagen 📆 19.09.2026 um 21:27 Uhr

Weiterlesen ↗

Sichere Programmierung DEV Community

The Database I Deleted: Migrating an Agentic RAG App to AWS Serverless #3

vor 5 Tagen 📆 19.09.2026 um 21:54 Uhr

Weiterlesen ↗

Sichere Programmierung DEV Community

See every API your server calls (and every call it receives) without changing a line of code

vor 5 Tagen 📆 19.09.2026 um 23:45 Uhr

Weiterlesen ↗

Sichere Programmierung t3n.de - Software & Entwickl

AI Contact Hotline: Hier können KI-Agenten selbstständig Sicherheitslücken melden

vor 5 Tagen 📆 20.09.2026 um 08:05 Uhr

Weiterlesen ↗

Sichere Programmierung DEV Community

I Rate-Limited an API by Hand. Then I Configured One in a Form Field.

vor 5 Tagen 📆 20.09.2026 um 09:21 Uhr

Weiterlesen ↗

Videos werden geladen ...

Beiträge werden geladen ...

Videos werden geladen ...

Beiträge werden geladen ...

Videos werden geladen ...

Beiträge werden geladen ...

Videos werden geladen ...

Beiträge werden geladen ...

Videos werden geladen ...

🚀 Auf tsecurity.de entdecken

Kommentare über Amazon Bedrock AgentCore Gateway - Part 5 Add API Gateway REST API as a target for Amazon Bedrock AgentCore Gateway

💬 Social News Network

Community Debatte 0 Beiträge

Tags:Noch keine Tags.

Noch keine Diskussion eröffnet

Sei der Erste, der seine Einschätzung oder PoC zu diesem Thema teilt.

🚀 Auf tsecurity.de entdecken

Echtzeit-Radar & Feeds

👥 Community & Social

🕒 tsecurity.de Such-Trends & Chronologie

Amazon Bedrock AgentCore Gateway - Part 5 Add API Gateway REST API as a target for Amazon Bedrock AgentCore Gateway

Introduction

Adding API Gateway REST API as a target for Amazon Bedrock AgentCore Gateway

Conclusion

1. Sofort-Triage & Abwehrmaßnahmen

SOC Incident Playbook: Remote Code Execution (RCE) Defense

2. Cyber Threat Intelligence & Forensik

MITRE ATT&CK Matrix Navigator 14 Taktiken

tsecurity.de Cognitive Threat RAG

Auch interessante Nachrichten Amazon Bedrock AgentCore Gateway - Part 5 Add API Gateway REST API as a target for Amazon Bedrock AgentCore Gateway

Building a REST API Client with Java HttpClient + Jackson

xalgorix v4.6.78

The Database I Deleted: Migrating an Agentic RAG App to AWS Serverless #3

See every API your server calls (and every call it receives) without changing a line of code

AI Contact Hotline: Hier können KI-Agenten selbstständig Sicherheitslücken melden

I Rate-Limited an API by Hand. Then I Configured One in a Form Field.

tsecurity.de LIVE

Echtzeit-Radar & Feeds

👥 Community & Social

Amazon Bedrock AgentCore Gateway - Part 5 Add API Gateway REST API as a target for Amazon Bedrock AgentCore Gateway

Introduction

Adding API Gateway REST API as a target for Amazon Bedrock AgentCore Gateway

Conclusion

1. Sofort-Triage & Abwehrmaßnahmen

SOC Incident Playbook: Remote Code Execution (RCE) Defense

2. Cyber Threat Intelligence & Forensik

MITRE ATT&CK Matrix Navigator 14 Taktiken

Mehr aus dieser Kategorie

tsecurity.de Cognitive Threat RAG

Auch interessante Nachrichten Amazon Bedrock AgentCore Gateway - Part 5 Add API Gateway REST API as a target for Amazon Bedrock AgentCore Gateway

Building a REST API Client with Java HttpClient + Jackson

xalgorix v4.6.78

The Database I Deleted: Migrating an Agentic RAG App to AWS Serverless #3

See every API your server calls (and every call it receives) without changing a line of code

AI Contact Hotline: Hier können KI-Agenten selbstständig Sicherheitslücken melden

I Rate-Limited an API by Hand. Then I Configured One in a Form Field.

tsecurity.de App