Lambda Create CodeCommit Repository Fails

Question

I have a lambda that will create a codecommit repository. It works fine when testing locally, but the connection to codecommit times out when run in aws.  The logs show that dns is working, it is able to resolve the IP, but the connection times out after.  I have the lambda running in a subnet that is public & has an internet gateway attached.  The lambda also goes over the internet to connect to the database, and that connection works correctly.  There's nothing in the security groups that would prevent access, both ingress and egress allow all tcp traffic.  What else could be the issue?

Riku_Kobayashi · Answer

Hello.

CodeCommit is no longer available for new AWS accounts.  
I think that's why it's an error.  
https://aws.amazon.com/jp/blogs/devops/how-to-migrate-your-aws-codecommit-repository-to-another-git-provider/  
> After careful consideration, we have made the decision to close new customer access to AWS CodeCommit, effective July 25, 2024. AWS CodeCommit existing customers can continue to use the service as normal. AWS continues to invest in security, availability, and performance improvements for AWS CodeCommit, but we do not plan to introduce new features.

Didier_Durand · Answer

Hi,

Did you check that the IP resolved on AWS is the same as IP resolved when run locally ?

It may be a different CodeCommit service endpoint when on AWS. That may require updates to the sec group as a consequence.

Best,

Didier

Lambda Create CodeCommit Repository Fails

Relevant content