Clone a CodeCommit Repository in a Lambda Function
~~
ACM.353 This took way longer than it should have to figure out
~~
#aws #lambda #codecommit #git #clone
Clone a CodeCommit Repository in a Lambda Function
~~
ACM.353 This took way longer than it should have to figure out
~~
#aws #lambda #codecommit #git #clone
Revisiting The Generic Lambda Function Objective
~~
ACM.346 Create a #Lambda function to push changes in #CodeCommit to an #S3 bucket — The Function
~~
#Lambda #IAM #SCP
https://medium.com/cloud-security/revisiting-the-generic-lambda-function-objective-94012345a797
AWS CodeCommit Triggers
~~
ACM.345 Seeking an #AWS #CodeCommit #trigger event for GitPush
~~
I explored whether I can trigger copying files to an S3 bucket with a trigger when I push files to AWS CodeCommit. Turned out to be a bit of a research project.
https://medium.com/cloud-security/aws-codecommit-triggers-06fe3924deb0
In this post we get things working to clone a repo from #GitHub to #AWS #CodeCommit but I show you what not to do. I’ve already deleted those credentials. Hopefully today I’ll show you how to fix it. And if it works out, how to sort of enforce #MFA to #clone a GitHub repo even though GitHub doesn’t support it. AWS CodeCommit does. We’ll see if I can work this out. :)
https://medium.com/cloud-security/cloning-a-github-repo-to-aws-codecommit-40d10cedaf0c