Browse through the questions and answers listed below or filter and sort to narrow down your results.
Block read access to a branch in a CodeCommit Repository
I have created a repository in CodeCommit. It has one master branch and a few other branches such as module-1, module-2, module-3, module-4, and module-5. I have created 3 groups(org-1, org-2, org-3) and each group has 10 users. Now I am trying to figure out to achieve the following level of restriction. module-1 - org-1 users only - view and modify module-2 - org-2 users only - view and modify module-3 - org-3 users only - view and modify module-4 - org-1 users and org-2 users only - view and modify module-5 - all group users can access - read-only I am trying to enforce policies but can not achieve this. I can block write access successfully, but when it comes to blocking read access for a particular branch and making a branch invisible for a certain user group, cannot achieve that. Can you please help me with this scenario? Thanks in advance.
YAML_FILE_ERROR: mapping values are not allowed in this context at line 1
DOWNLOAD_SOURCE - YAML_FILE_ERROR: mapping values are not allowed in this context at line 1 Reference YAML file: buildspec.yaml version: 0.2 `phases: pre_build: commands: - echo Logging in to Amazon ECR... - $(aws ecr get-login --no-include-email --region $AWS_DEFAULT_REGION) build: commands: - echo Build started on `date` - echo Building the Docker image... - docker build -t web:1 . - docker tag web:1 020861552741.dkr.ecr.ap-southeast-1.amazonaws.com/hasib_cloud post_build: commands: - echo Build completed on `date` - echo Pushing the Docker image... - docker push 020861552741.dkr.ecr.ap-southeast-1.amazonaws.com/hasib_cloud ~ ![screenshot](/media/postImages/original/IMD8WJYdlxT_6k-v3PKRmBGA)
Not able to clone a codecommit repository
I followed these steps to get access to codecommit but i'm not able to clone repositories. 1. Install latest pip and git-remote-codecommit 2. Create and IAM user with policy AWSCodeCommitPowerUser and attach SSH and AWS Git credentials. 3. Configure the IAM user locally. I get the following error when try to clone through ssh: ``` Cloning into 'nfs-utils'... Enter passphrase for key '/home/risbhat/.ssh/id_rsa': no such identity: /home/risbhat/.ssh/id_ed25519: No such file or directory Permission denied (publickey). fatal: Could not read from remote repository. ``` I can see the repository exists and I have added the ssh keys/Git credentials to my IAM user. Am i missing some step?
CodeCommit merge-pull-request-by-three-way merges by commit-id rather than branch
We are trying to use CodeCommit and CodeBuild to implement a process by which when a developer creates a pull request to merge changes from his/her branch, rather than merging into master, he/she requests the changes be merged into an integration branch. Before the merge, the integration and master branches reference the same commit id. After the merge of the developer's changes into the integration branch, integration is now ahead of master and the corresponding CodeBuild job builds the integration branch. Once all the unit and integration tests have been verified, the integration branch is then merged into master branch and integration and master will once again reference the same commit id. What I have observed is that when I execute a merge-pull-request-by-three-way (cli) specifying the pull request that was created to merge from the developer branch into integration, the end result is that the code is merged into both the integration and master branches. Unlike merge-branches-by-three-way, merge-pull-request-by-three-way does not give you an option to specify the target branch, but it shouldn't since the pull request already specifies the target branch into which changes are to be merged. It is unclear to me if this is happening because the commit id's are the same and the merge is doing it based on that, or if CodeCommit thinks master is the "current" branch (referring to the git-merge behavior), but regardless, the result was not what I was expecting. Is this behavior of ignoring the pull requests target branch when merging using merge-branches-by-three-way, a bug or is this expected behavior/"feature" of merge-pull-request-by-three-way (and possibly the other merge-pull-request-* commands) and I should instead use merge-branches-by-three-way.
Lambda API Calls duration
I have a lambda function that makes calls to different aws services. For example: DynamoDB, CodeCommit, SES. My problem is the one call's duration. codecommit.getMergeOptions() for some reason ( I want to know which ) this call last too much compared with others. For example codecommit.getDifferences last 300 ms but codecommit.getMergeOptions() 900 ms. Why that happen?