AWS security-ir: Document investigative agent data processing locations and inference profiles
Summary
Rewrites the investigative agent processing page to explain that processing location depends on the case Region's Amazon Bedrock inference profile (Geographic vs Global), adds a table of supported case Regions and where processing can occur, lists Regions where the agent is unavailable, and describes cross-Region investigation behavior for standard, opt-in, and global services.
Security assessment
The change is documentation of data residency and processing boundaries for the Security Incident Response investigative agent, including an explicit warning that Global inference profiles may process case metadata in any commercial AWS Region and that opt-in Regions are excluded from investigation. This is security/compliance-relevant guidance (data residency, metadata handling, IAM/CloudTrail metadata access scope) rather than a fix for a specific vulnerability or incident.
Evidence
If you create cases in a Region that uses the Global inference profile, case metadata can be processed in any commercial AWS Region.
Diff
diff --git a/security-ir/latest/userguide/agent-processing-location.md b/security-ir/latest/userguide/agent-processing-location.md index fc01ef7..5feda88 100644 --- a//security-ir/latest/userguide/agent-processing-location.md +++ b//security-ir/latest/userguide/agent-processing-location.md @@ -6,0 +7,2 @@ +Supported Regions and where your data is processedRegions where the investigative agent isn't availableHow the investigative agent investigates resources in multiple Regions + @@ -9 +11,75 @@ -The Security Incident Response investigative agent processes metadata in Amazon Bedrock's global region, regardless of which Region your case or findings data originates from. This processing is transient—the agent analyzes the metadata to generate insights and recommendations but does not store the metadata persistently in the Amazon Bedrock infrastructure. +The investigative agent runs in the Region where you create your case. Amazon Bedrock then sends model requests based on that Region's _inference profile_. An inference profile determines where your data can be processed. There are two types: + + * **Geographic** : Processing stays within a specific geography, such as the US or the EU. Your data doesn't leave that geography. + + * **Global** : Processing can happen in any commercial AWS Region. + + + + +Regardless of profile type, results are always stored in your case Region, and Amazon Bedrock doesn't keep the metadata used during processing. + +## Supported Regions and where your data is processed + +Cases created in the following Regions have full investigative agent support. Find your case Region in the first column to see where your data can be processed. + +Investigative agent processing locations by case Region Case Region | Inference profile | Where processing can occur +---|---|--- +US East (N. Virginia) | US | `us-east-1`, `us-east-2`, `us-west-2` +US East (Ohio) | US | `us-east-1`, `us-east-2`, `us-west-2` +US West (Oregon) | US | `us-east-1`, `us-east-2`, `us-west-2` +Europe (Ireland) | EU | `eu-central-1`, `eu-north-1`, `eu-west-1`, `eu-west-3` +Europe (London) | EU | `eu-central-1`, `eu-north-1`, `eu-west-1`, `eu-west-3` +Europe (Paris) | EU | `eu-central-1`, `eu-north-1`, `eu-west-1`, `eu-west-3` +Europe (Frankfurt) | EU | `eu-central-1`, `eu-north-1`, `eu-west-1`, `eu-west-3` +Europe (Stockholm) | EU | `eu-central-1`, `eu-north-1`, `eu-west-1`, `eu-west-3` +Asia Pacific (Tokyo) | Japan | `ap-northeast-1`, `ap-northeast-3` +Asia Pacific (Sydney) | Australia | `ap-southeast-2` +Canada (Central) | Global | Any commercial AWS Region +South America (São Paulo) | Global | Any commercial AWS Region +Asia Pacific (Seoul) | Global | Any commercial AWS Region +Asia Pacific (Singapore) | Global | Any commercial AWS Region +Asia Pacific (Mumbai) | Global | Any commercial AWS Region + +###### Important + +If you create cases in a Region that uses the Global inference profile, case metadata can be processed in any commercial AWS Region. Organizations with strict data residency requirements must evaluate whether this cross-Region processing is compatible with their compliance obligations. Results are always stored in your case Region. + +## Regions where the investigative agent isn't available + +AWS Security Incident Response is available in the following Regions, but the investigative agent isn't available in them. Cases created in these Regions don't receive automated investigation. + + * Africa (Cape Town): `af-south-1` + + * Asia Pacific (Hong Kong): `ap-east-1` + + * Asia Pacific (Hyderabad): `ap-south-2` + + * Asia Pacific (Jakarta): `ap-southeast-3` + + * Asia Pacific (Melbourne): `ap-southeast-4` + + * Europe (Milan): `eu-south-1` + + * Europe (Spain): `eu-south-2` + + * Europe (Zurich): `eu-central-2` + + * Middle East (Bahrain): `me-south-1` + + * Middle East (UAE): `me-central-1` + + + + +## How the investigative agent investigates resources in multiple Regions + +A case can include impacted resources in more than one Region. The agent retrieves metadata from each Region separately. What it can access depends on the type of Region: + + * **Standard Regions** : The agent can retrieve metadata, such as AWS CloudTrail events and Amazon Elastic Compute Cloud (Amazon EC2) details, from any standard Region. This is true even if the Region differs from your case Region. + + * **Opt-in Regions** : The agent can't retrieve metadata from opt-in Regions. Resources in an opt-in Region aren't included in the investigation. + + * **Global services** : Data from AWS Identity and Access Management (IAM) and AWS Cost Explorer is always available, regardless of Region. + + @@ -11 +86,0 @@ The Security Incident Response investigative agent processes metadata in Amazon -When the agent completes its analysis, the generated insights and recommendations are stored with your case investigation data in the Region where the case was created. The metadata used for processing is not retained in Amazon Bedrock global Region after the analysis completes.