Questions tagged with AWS CodeStar

I am trying to create a CICD of my application that is available on Bitbucket. For this, I have created AWS CodePipeline that will deploy this app to ECS Cluster. I am trying to do this via AWS CLI. Here is my JSON file: ``` { "pipeline": { "roleArn": "arn:aws:iam::xxxxxxxxxxxx:role/service-role/AWSCodePipelineServiceRole-us-east-1-HubspotConnector", "stages": [{ "Name": "Source", "Actions": [{ "InputArtifacts": [], "ActionTypeId": { "Version": "1", "Owner": "AWS", "Category": "Source", "Provider": " " }, "OutputArtifacts": [{ "Name": "SourceArtifact" }], "RunOrder": 1, "Configuration": { "ConnectionArn": "arn:aws:codestar-connections:us-east-1:7xxxxxxxx3930:connection/5bxxxx2-257f-4xxxxx0-xxx3-edfdsfsdf7d672f", "FullRepositoryId": "rxxxxxh/hubspotcctorpipeline", "BranchName": "main", "OutputArtifactFormat": "CODE_ZIP" }, "Name": "ApplicationSource" }] }, { "name": "Build", "actions": [{ "inputArtifacts": [{ "name": "SourceArtifact" }], "name": "Build", "actionTypeId": { "category": "Build", "owner": "AWS", "version": "1", "provider": "CodeBuild" }, "outputArtifacts": [{ "name": "default" }], "Configuration": { "ProjectName": "cicdCli" }, "runOrder": 1 }] }, { "Name": "DeployECS", "ActionTypeId": { "Category": "Deploy", "Owner": "AWS", "Provider": "ECS", "Version": "1" }, "RunOrder": 2, "Configuration": { "ClusterName": "my-ecs-cluster", "ServiceName": "sample-app-service", "FileName": "imagedefinitions.json", "DeploymentTimeout": "15" }, "OutputArtifacts": [], "InputArtifacts": [{ "Name": "my-image" }] } ], "artifactStore": { "type": "S3", "location": "codepipeline-us-east-1-1xxx5xxxx29" }, "name": "newPipelineCicd", "version": 1 } } ``` Here is the error I am facing:  Can Someone describe me what I am doing wrong? I have searched for these errors but didn't get any help from anywhere. Also no one have written any tutorial or proper guide for this. I have found AWS documentation, one of the complexest documentations. Please guide me here.I would really appreciate that.lg...

Currently facing an issue with creating a notification rule for code pipeline using CDK with Pipeline or CodePipeline constructs ``` Resource handler returned message: "Invalid request provided: AWS::CodeStarNotifications::NotificationRule" (RequestToken: <GUID>, HandlerErrorCode: InvalidRequest) ``` The topic and chatbot are already defined in a different stack. The topic already has configured an access policy. However when I attempt to create a rule for my pipelines, it fails. Every time. ``` { "Version": "2008-10-17", "Statement": [ { "Sid": "AWSCodeStarNotifications_publish", "Effect": "Allow", "Principal": { "Service": "codestar-notifications.amazonaws.com" }, "Action": "SNS:Publish", "Resource": "arn:aws:sns:us-east-1:123456789:PipelineNotifications" } ] } ``` Referencing topic: ``` const pipelineNotificationsTopic = sns.Topic.fromTopicArn( this, "PipelineNotifications", `arn:aws:sns:${props?.env.region}:${props?.env.account}:PipelineNotifications ` ); ``` Pipeline code: ``` this.pipeline = new Pipeline( this, `${props?.appName}-MyPipeline`, { pipelineName: "MyPipeline", crossAccountKeys: true, restartExecutionOnUpdate: true, } ); const rule = this.pipeline.notifyOn( "CodeStarRule", pipelineNotificationsTopic, { events: [ PipelineNotificationEvents.PIPELINE_EXECUTION_SUCCEEDED, PipelineNotificationEvents.PIPELINE_EXECUTION_FAILED, PipelineNotificationEvents.ACTION_EXECUTION_FAILED, ], detailType: DetailType.FULL, } ); ``` or ``` this.pipeline = new Pipeline( this, `${props?.appName}-MyPipeline`, { pipelineName: "MyPipeline", crossAccountKeys: true, restartExecutionOnUpdate: true, } ); const rule =new NotificationRule(this, "Notification", { detailType: DetailType.FULL, events: [ "codepipeline-pipeline-pipeline-execution-failed", "codepipeline-pipeline-action-execution-failed", "codepipeline-pipeline-stage-execution-failed", "codepipeline-pipeline-manual-approval-failed", "codepipeline-pipeline-manual-approval-needed", ], source: pipeline, targets: [pipelineNotificationsTopic], }); ```lg...

I created a project with CodeStar. Cloud9 was integrated with CodeCommit. My last commits were in March, 2022. Tried to commit a file in July 2022 and Cloud9 has forgotten how to connect to the repository. I opened a ticket and the first level of support "transferred the ticket to the CodeStar team", who have not done anything for three business days. I have posted a couple replies in the support ticket, does anyone know how to escalate a ticket? Or at least to get it noticed, that it is waiting on AWS response and not on customer?lg...

The idea is the following: * Codecommit has a notification rule. * Notification's target it's an sns topic. * The topic's target is a lambda function. * Minimally I want lambda X-Ray trace when the notification occurs. If all trace better. I post a message from the SNS Topic console, the X-Ray trace is generated with SNS and Lambda. However, if I trigger a notification, the trace is not generated (Lambda runs correctly). I would like to know if I can make the complete or partial trace be generated when generating a notification in CodeCommit. # Update My lambda logs insights: * Post message from SNS Topic:```"_X_AMZN_TRACE_ID": "Root=1-62gd6bfa-6ag9233f49fe8faf6ef7ed16;Parent=4b19513e742ad199;Sampled=1"``` * Codecommit notification: ```"_X_AMZN_TRACE_ID": "Root=1-62d56c36-3bg3f6fbaa075b171b9fdba6;Parent=2f5f68ffyf25388e;Sampled=0"``` My lambda Function has active tracing, and has permissions, but I don't know why the second case don't get sampled. It should be tracing all the invocations, being sampled or not sampled...lg...

Good afternoon dear experts. Help solve the issue. I run the sh file (with rights) through the terminal, I get No such file or directory/.bashrc Google didn't help. I'm beating this wall for the 3rd evening). sh file content: ` source ~/.bashrc cd ~/data python file.py ` Contents of the .bashrc file: ` # .bashrc export PATH="~/.pyenv/bin:$PATH" eval "$(pyenv init -)" eval "$(pyenv virtualenv-init -)" # Source global definitions if [ -f /etc/bashrc ]; then . /etc/bashrc fi # Uncomment the following line if you don't like systemctl's auto-paging feature: # export SYSTEMD_PAGER= # User specific aliases and functi # >>> conda initialize >>> # !! Contents within this block are managed by 'conda init' !! __conda_setup="$('/home/ec2-user/.pyenv/versions/anaconda3-2020.11/bin/conda' 'shell.bash' 'hook' 2> /dev/null)" if [ $? -eq 0 ]; then eval "$__conda_setup" else if [ -f "/home/ec2-user/.pyenv/versions/anaconda3-2020.11/etc/profile.d/conda.sh" ]; then . "/home/ec2-user/.pyenv/versions/anaconda3-2020.11/etc/profile.d/conda.sh" else export PATH="/home/ec2-user/.pyenv/versions/anaconda3-2020.11/bin:$PATH" fi fi unset __conda_setup # <<< conda initialize <<< `lg...

Is there a way to create a list of resources based on the date of creation? This is for understanding what resources were created after a MAP Agreement signed . And collect them in one place.lg...

I created a CodeBuild project for a .Net Framework repo in BitBucket cloud. The project is using OAuth to connect to BB Cloud. The build runs successfully and creates artifacts in S3. Next, I created a CodePipeline using this CodeBuild project. The pipeline wizard forces me to select a Bitbucket app or create a new one to connect to the BB Cloud repo. I've tried using the apps there as well as using the install new app method and have the same problem outlined below. The apps that are already installed were created with my AWS account. **Problem:** I am getting a build error when trying to pull from the Bitbucket cloud repo. The build error is: > authorization failed for primary source and source version I have a user in my Bitbucket Cloud repo with admin privs for my AWS email...which is why my CodeBuild project works. So I'm not sure why I am still having this problem via the Pipeline using the same codebuild. Any thoughts?lg...

Account A has CodeStar Connection (sort of Admin account) Account B wants to create a CodePipeline using the CodeStar connection in account A. What permissions or setup is needed to achieve this? Using the connection ARN from account A in account B causes sourcing error in pipeline with message "The provided role does not have sufficient permissions". Is there any restriction of the "region" of the connection ARN to be used?lg...

From this post (https://news.ycombinator.com/item?id=29891656), it looks like GitHub is no longer supporting unauthenticated "git://". Our CodePipeline builds stopped working today and we're getting the following error in the `Source` step: ``` [GitHub] GitHub returned an Internal Error exception. Please retry shortly. If the issue continues it may be reported on the GitHub status page at https://githubstatus.com ``` Does CodeStar use "git://"?lg...

I am running codepipeline with codebuild, I can pull the repo, however, I cannot pull the LFS large files. I have followed various guides on the internet, but have come to realize that codestar is not trying to connect to bitbucket LFS. In the bitbucket history I see the regular clone request but do not see the git lfs request. Codestar seems to be acting as a proxy I am enclosing my buildpec.yml and some logs. It fails at line `git lfs pull` ``` phases: install: commands: - cd /tmp/ - curl -OJL https://github.com/git-lfs/git-lfs/releases/download/v2.13.3/git-lfs-linux-amd64-v2.13.3.tar.gz - tar xzf git-lfs-linux-amd64-v2.13.3.tar.gz - ./install.sh - cd $CODEBUILD_SRC_DIR - git lfs pull build: commands: - echo Build started on `date` - echo Building the Docker image... - docker build -f ci/Dockerfile -t system1.datagen.tech:5000/dg-simulated-reality-ecr:teststeve . post_build: commands: - echo Build completed on `date` - echo Pushing the Docker images... - docker push system1.datagen.tech:5000/dg-simulated-reality-ecr:teststeve - echo Writing image definitions file... ``` aws logs ``` [Container] 2021/12/28 14:06:47 Running command git lfs pull batch response: Authorization error: https://codestar-connections.us-east-1.amazonaws.com/git-http/ACCOUNTNUMBER/us-east-1/ARNSTUFF/MYCOMPANY/MYREPO.git/info/lfs/objects/batch Check that you have proper access to the repository ........ [Container] 2021/12/28 14:06:47 Command did not exit successfully git lfs pull exit status 2 [Container] 2021/12/28 14:06:47 Phase complete: INSTALL State: FAILED [Container] 2021/12/28 14:06:47 Phase context status code: COMMAND_EXECUTION_ERROR Message: Error while executing command: git lfs pull. Reason: exit status 2 ```lg...

Hello all, I'm trying to separate the stages in the pipeline, but failing. My project follows the Python webservice template in which the below section, seems to create both "Prod" and "Stage" automatically: ``` Parameters: ProjectId: Type: String Description: CodeStar projectId used to associate new resources to team members CodeDeployRole: Type: String Description: IAM role to allow AWS CodeDeploy to manage deployment of AWS Lambda functions Stage: Type: String Description: The name for a project pipeline stage, such as Staging or Prod, for which resources are provisioned and deployed. Default: '' ``` I tried: https://docs.aws.amazon.com/codestar/latest/userguide/customize-ec2-multi-endpoints-newstage.html And ended up with the new "*-prod" stack failing to create. I also tried: https://docs.aws.amazon.com/codepipeline/latest/userguide/pipelines-edit.html But the downloaded template does not have a deployment stage section. What I am trying is to be able to have "Stage" as default from a "develop" branch and "Prod" only from "master". Can someone please provide instructions on how to do that? Thank youlg...

Using the CodeStar Python webservice as starting point I have created a lambda function to write data to DynamoDB. Using "sam local start-api" CLI the tests go well and the items appear on the DynamoDB (checking with the dashboard). However when I try to test the lambda function from the dashboard (Services > Lambda > Functions > "<MyLambda>" > Test) I get an AccessDeniedException in the form: "An error occurred (AccessDeniedException) when calling the PutItem operation: User: arn:aws:sts::xxx:assumed-role/CodeStar-<myproject>-Execution/awscodestar-<myproject>-lambda-<mylambda> is not authorized to perform: dynamodb:PutItem on resource: arn:aws:dynamodb:us-west-2:<mytable>" Here is part of my modified template.yml: LambdaExecutionRole: Description: Creating service role in IAM for AWS Lambda Type: AWS::IAM::Role Properties: RoleName: !Sub 'CodeStar-${ProjectId}-Execution${Stage}' AssumeRolePolicyDocument: Statement: - Effect: Allow Principal: Service: \[lambda.amazonaws.com] Action: sts:AssumeRole Path: / ManagedPolicyArns: - arn:aws:iam::aws:policy/service-role/AWSLambdaBasicExecutionRole - arn:aws:iam::aws:policy/AWSLambdaInvocation-DynamoDB - arn:aws:iam::aws:policy/AmazonDynamoDBFullAccess PermissionsBoundary: !Sub 'arn:${AWS::Partition}:iam::${AWS::AccountId}:policy/CodeStar_${ProjectId}_PermissionsBoundary' Can someone help?lg...