-
Notifications
You must be signed in to change notification settings - Fork 0
/
rdk-role.yml
60 lines (60 loc) · 2.38 KB
/
rdk-role.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
##
# Copyright Amazon.com, Inc. or its affiliates. All Rights Reserved.
# SPDX-License-Identifier: MIT-0
#
# Permission is hereby granted, free of charge, to any person obtaining a copy of this
# software and associated documentation files (the "Software"), to deal in the Software
# without restriction, including without limitation the rights to use, copy, modify,
# merge, publish, distribute, sublicense, and/or sell copies of the Software, and to
# permit persons to whom the Software is furnished to do so.
#
# THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED,
# INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
# PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT
# HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
# OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
# SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
##
AWSTemplateFormatVersion: '2010-09-09'
Description: AWS CloudFormation template to create custom AWS Config rules. You will
be billed for the AWS resources used if you create a stack from this template.
Metadata:
AWS::CloudFormation::Interface:
ParameterGroups:
- Label:
default: Lambda Account ID
Parameters:
- LambdaAccountId
ParameterLabels:
LambdaAccountId:
default: 'REQUIRED: Account ID that contains Lambda Function(s) that back
the Rules in this template.'
Parameters:
LambdaAccountId:
Description: Account ID that contains Lambda functions for Config Rules.
MaxLength: '12'
MinLength: '12'
Type: String
Resources:
ConfigRole:
Type: AWS::IAM::Role
Metadata:
cfn_nag:
rules_to_suppress:
- id: W28
reason: "This role name is explicitly mentioned in the Blog post."
Properties:
RoleName: AWSRDKLambdaRole
AssumeRolePolicyDocument:
Version: '2012-10-17'
Statement:
- Sid: REMOTE
Action: sts:AssumeRole
Effect: Allow
Principal:
AWS: !Sub arn:${AWS::Partition}:iam::${LambdaAccountId}:root
Condition:
StringLike:
aws:PrincipalArn: !Sub arn:${AWS::Partition}:iam::${LambdaAccountId}:role/rdk/*
ManagedPolicyArns:
- !Sub arn:${AWS::Partition}:iam::aws:policy/service-role/AWSConfigRole