I’ve seen that this lab is getting possibly removed by the abuse of some users but until it’s removed I’m stuck on my AWS (level 4) journey in the KodeKloudEngineer path.
Can you atleast for now just remove/hide it? because i need to finish it to be able and continue to my next AWS task.
thanks.
I’m told that CodePipeline should be back in the system in the next few days. Sorry for the delay, but we needed time to get “guardrails” implemented and to test that. But it’s on its way.
Hello,
When pipeline is start, the error occurs:
Error calling startBuild: User: arn:aws:sts::983375543249:assumed-role/role-1/1770622844750 is not authorized to perform: codebuild:StartBuild on resource: arn:aws:codebuild:us-east-1:983375543249:project/xfusion-build-project with an explicit deny in a service control policy (Service: AWSCodeBuild; Status Code: 400; Error Code: AccessDeniedException; Request ID: 6d176c43-e388-4b5e-87df-dd3a70cb9b2c; Proxy: null)
We’ve added a fair amount of new information about the limits of what you can do with CodePipeline in the playground landing page:
CodePipeline - CI/CD Service
Automates build, test, and deploy phases.
- Compute types limited to t3.micro, t3.small, t3.medium. Violations updated to t3.micro.
You should make sure your test is in these limits
Hi everyone,
I ran into a permission issue during the build stage while setting up my CI/CD pipeline and I’m curious how others have handled similar problems. How did you configure IAM roles and permissions, did you have to deal with any Service Control Policies (SCPs), and what are your best practices for running CodeBuild smoothly in a pipeline? I’d love to hear about your experiences and suggestions.
Latest action execution message
Error calling startBuild: User: arn:aws:sts::094402022762:assumed-role/devops-webapp-pipeline-role/1771230735761 is not authorized to perform: codebuild:StartBuild on resource: arn:aws:codebuild:us-east-1:094402022762:project/devops-build-project with an explicit deny in a service control policy (Service: AWSCodeBuild; Status Code: 400; Error Code: AccessDeniedException; Request ID: b63ef145-b790-4bb0-8dce-55606a02de44; Proxy: null)
This is a valid issue with SCP permissions. There is an internal ticket for it, and the team is working on it. I’ll keep you updated.
Nope, just make sure the pipeline is working as expected.
Dear @raymond.baoly
This command doesn’t work
aws s3 cp index.html s3://datacenter-deployment-8179/index.html
What do you mean by “the command doesn’t work”? Please share a screenshot or provide more context.
Please ensure that the CodeBuild role has the proper permissions, the S3 bucket name is correct and exists, and the S3 policy is configured correctly.
