Skip to content

[ESC-5575] Fixing role name for workload scanning #146

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.

Sign up for GitHub

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 1 commit into from
Mar 10, 2025
Merged

[ESC-5575] Fixing role name for workload scanning #146

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions modules/vm_workload_scanning.cft.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,7 @@ Resources:
ScanningRole:
Type: AWS::IAM::Role
Properties:
RoleName: !Sub sysdig-vm-workload-scanning-${NameSuffix}
RoleName: !Sub secure-vm-workload-scanning-${NameSuffix}
AssumeRolePolicyDocument:
Version: '2012-10-17'
Statement:
Expand All @@ -86,7 +86,7 @@ Resources:
ECRPolicy:
Type: AWS::IAM::Policy
Properties:
PolicyName: !Sub sysdig-vm-workload-scanning-${NameSuffix}-ecr
PolicyName: !Sub secure-vm-workload-scanning-${NameSuffix}-ecr
Roles:
- !Ref ScanningRole
PolicyDocument:
Expand All @@ -104,7 +104,7 @@ Resources:
Type: AWS::IAM::Policy
Condition: IsLambdaEnabled
Properties:
PolicyName: !Sub sysdig-vm-workload-scanning-${NameSuffix}-lambda
PolicyName: !Sub secure-vm-workload-scanning-${NameSuffix}-lambda
Roles:
- !Ref ScanningRole
PolicyDocument:
Expand All @@ -128,7 +128,7 @@ Resources:
Type: AWS::CloudFormation::StackSet
Condition: IsOrganizational
Properties:
StackSetName: !Sub sysdig-vm-workload-scanning-${NameSuffix}
StackSetName: !Sub secure-vm-workload-scanning-${NameSuffix}
Description: Creates IAM roles within an AWS organization for Agentless Workload Scanning
PermissionModel: SERVICE_MANAGED
Capabilities:
Expand Down Expand Up @@ -189,7 +189,7 @@ Resources:
ScanningRole:
Type: AWS::IAM::Role
Properties:
RoleName: !Sub sysdig-vm-workload-scanning-${NameSuffix}
RoleName: !Sub secure-vm-workload-scanning-${NameSuffix}
AssumeRolePolicyDocument:
Version: "2012-10-17"
Statement:
Expand All @@ -203,7 +203,7 @@ Resources:
ECRPolicy:
Type: AWS::IAM::Policy
Properties:
PolicyName: !Sub sysdig-vm-workload-scanning-${NameSuffix}-ecr
PolicyName: !Sub secure-vm-workload-scanning-${NameSuffix}-ecr
Roles:
- !Ref ScanningRole
PolicyDocument:
Expand All @@ -221,7 +221,7 @@ Resources:
Type: AWS::IAM::Policy
Condition: IsLambdaEnabled
Properties:
PolicyName: !Sub sysdig-vm-workload-scanning-${NameSuffix}-lambda
PolicyName: !Sub secure-vm-workload-scanning-${NameSuffix}-lambda
Roles:
- !Ref ScanningRole
PolicyDocument:
Expand All @@ -246,5 +246,5 @@ Outputs:
ScanningRoleARN:
Description: ARN of the scanning role
Value:
Fn::Sub: sysdig-vm-workload-scanning-${NameSuffix}
Fn::Sub: secure-vm-workload-scanning-${NameSuffix}

2 changes: 1 addition & 1 deletion modules/vm_workload_scanning.components.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@
"version": "v0.1.0",
"trustedRoleMetadata": {
"aws": {
"roleName": "sysdig-vm-workload-scanning-{{NameSuffix}}"
"roleName": "secure-vm-workload-scanning-{{NameSuffix}}"
}
}
}
Expand Down
Loading