无法在代码管道操作AWS CDK上由代码管道承担角色

如何解决无法在代码管道操作AWS CDK上由代码管道承担角色

我一直在使用AWS CDK,并正在AWS educate account上构建代码管道堆栈。我正在使用的用户具有足够的权限来访问和使用代码管道。我的问题是,AWS CDK为code pipeline action是根帐户的Principle的{​​{1}}生成角色。因此它无权执行在root帐户上承担的角色。

操作代码:

ARN

Cloudformation模板输出:

 {
  stageName: "Build",actions: [
      new codepipelineActions.CodeBuildAction(
        {
          actionName: "Build",input: sourceOutput,project: builder
        }
      )
    ]
}

这将引发错误:

"devPipelineBuildCodePipelineActionRole8696D056": {
      "Type": "AWS::IAM::Role","Properties": {
        "AssumeRolePolicyDocument": {
          "Statement": [
            {
              "Action": "sts:AssumeRole","Effect": "Allow","Principal": {
                "AWS": {
                  "Fn::Join": [
                    "",[
                      "arn:",{
                        "Ref": "AWS::Partition"
                      },":iam::",{
                        "Ref": "AWS::AccountId"
                      },":root"
                    ]
                  ]
                }
              }
            }
          ],"Version": "2012-10-17"
        }
      },"Metadata": {
        "aws:cdk:path": "PipeLineStack/dev-Pipeline/Build/Build/CodePipelineActionRole/Resource"
      }
    }
...
{
  "Actions": [
    {
      "ActionTypeId": {
        "Category": "Build","Owner": "AWS","Provider": "CodeBuild","Version": "1"
      },"Configuration": {
        "ProjectName": {
          "Ref": "BuildAndTestB9A2F419"
        }
      },"InputArtifacts": [
        {
          "Name": "SourceOutput"
        }
      ],"Name": "Build","RoleArn": {
        "Fn::GetAtt": [
          "devPipelineBuildCodePipelineActionRole8696D056","Arn"
        ]
      },"RunOrder": 1
    }
  ],"Name": "Build"
}

如果我从arn:aws:iam::acount_id:role/PipeLineStack-devPipelineRole5B29FEBC-1JK24J0K5N1UG is not authorized to perform AssumeRole on role arn:aws:iam::acount_id: role/PipeLineStack-devPipelineBuildCodePipelineActionRo-17ETJU1KZCCNQ (Service: AWSCodePipeline; Status Code: 400; Error Code: InvalidStructureException; Req uest ID: c8c8af89-2409-4cc1-aad8-4de553a1764f; Proxy: null) 中删除了RoleArn并执行了它可以工作的模板。

我的问题是,如何防止CDK阻止使用root帐户或变通方法在Principle中添加默认角色?

解决方法

当前似乎不允许操作在AWS Educate中扮演任何角色。因此,要解决此问题并消除人工开销,请使用CDK L1 Constructs修改生成的云形成。

可以像这样创建管道:

   // Custom role to pass in to pipeline
    const pipeLineRole = new iam.Role(this,"CodePipeLineRole",{
      assumedBy: new iam.ServicePrincipal("codepipeline.amazonaws.com"),});

    pipeLineRole.addToPolicy( 
      // Required policy for each aciton to run
    )
    const pipeline = new codepipeline.Pipeline(this,"Pipeline",{
      role: pipeLineRole,stages: [
        //  ...
        {
          actions: [action1,action2],},//  ...
      ],});

    // Altering cloudformation to remove role arn from actions
    const pipelineCfn = pipeline.node.defaultChild as cdk.CfnResource;
    // addDeletionOverride  removes the property from the cloudformation itself
    // Delete action arn for every stage and action created
    pipelineCfn.addDeletionOverride("Properties.Stages.1.Actions.0.RoleArn");
    pipelineCfn.addDeletionOverride("Properties.Stages.2.Actions.0.RoleArn");
    pipelineCfn.addDeletionOverride("Properties.Stages.3.Actions.0.RoleArn");

这是一种解决方法,它可以工作,但是仍然存在创建的有害策略和角色,这些策略和角色尚未分配给针对单个操作创建的任何服务。

,

管道配置中的以下代码:

"RoleArn": {
        "Fn::GetAtt": [
          "devPipelineBuildCodePipelineActionRole8696D056","Arn"
        ]
      },

...表示当CodePipeline服务将调用“ Build”操作时,它将“承担”角色“ devPipelineBuildCodePipelineActionRole8696D056”,但是此角色与“ codepipeline.amazonaws.com”服务没有信任策略,因此会出现错误。

当您有跨帐户操作(CodeBuild项目位于另一个帐户中)时,该操作下的'RoleArn'属性很有用,因此除非是这种情况,否则最好删除此属性。

我们将需要查看cdk代码来回答您的问题:

如何防止CDK阻止使用root帐户或替代方法在Principle中添加默认角色?

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


依赖报错 idea导入项目后依赖报错,解决方案:https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错:更换其他版本 无法下载依赖可参考:https://blog.csdn.net/weixin_42628809/a
错误1:代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
错误1:gradle项目控制台输出为乱码 # 解决方案:https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
错误还原:在查询的过程中,传入的workType为0时,该条件不起作用 <select id="xxx"> SELECT di.id, di.name, di.work_type, di.updated... <where> <if test=&qu
报错如下,gcc版本太低 ^ server.c:5346:31: 错误:‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
解决方案1 1、改项目中.idea/workspace.xml配置文件,增加dynamic.classpath参数 2、搜索PropertiesComponent,添加如下 <property name="dynamic.classpath" value="tru
删除根组件app.vue中的默认代码后报错:Module Error (from ./node_modules/eslint-loader/index.js): 解决方案:关闭ESlint代码检测,在项目根目录创建vue.config.js,在文件中添加 module.exports = { lin
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams['font.sans-serif'] = ['SimHei'] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -> systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping("/hires") public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate<String
使用vite构建项目报错 C:\Users\ychen\work>npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-