aws-sagemaker-invoke-pipeline
StartPipelineExecution directly invokes a SageMaker Pipeline, running its steps as the pipeline's execution role.
match (effective permission)
{
"action": "sagemaker:StartPipelineExecution",
"resource_type": "AWS::SageMaker::Pipeline"
}
emit
| source type | Identity |
|---|---|
| target type | Workflow |
| source | <principal> |
| target | <SageMaker Pipeline> |
| permissions | sagemaker:StartPipelineExecution |
| conditions | iam_permission |
Narrative
{principal.name} can start {pipeline.name} (sagemaker:StartPipelineExecution), causing its steps to run as the pipeline's execution role.
Raw rule rules/derived/aws/sagemaker.yaml
id: aws-sagemaker-invoke-pipeline
emits: CanInvoke
description: StartPipelineExecution directly invokes a SageMaker Pipeline, running its steps as the pipeline's
execution role.
match_effective_permission:
action: sagemaker:StartPipelineExecution
resource_type: AWS::SageMaker::Pipeline
emit:
source_type: Identity
target_type: Workflow
source: <principal>
target: <SageMaker Pipeline>
permissions:
- sagemaker:StartPipelineExecution
conditions:
- iam_permission
false_positive_note: StartPipelineExecution alone only grants execution of the CURRENT pipeline definition.
If the definition already contains attacker-controllable steps (e.g. a custom script source that can
be overwritten), this becomes ACTIVE for CanExecuteAs via cicd-chains (trigger-runner-executes-as).
If the pipeline definition is clean and pinned, triggering it is CONDITIONAL(attacker_influenced_definition).
narrative: '{principal.name} can start {pipeline.name} (sagemaker:StartPipelineExecution), causing its
steps to run as the pipeline''s execution role.'