Does anyone here have experience with AWS CodeCommit?

Do you like it compared to other popular tools like github/gitlab/bitbucket/tfs?

I just started playing with it today and think it's pretty neat, wanted to reach out to the community here and see if you guys/gals know of any gotcha's that you may have encountered?

Too many eggs in 1 basket when it comes to aws.

Granted I use AWS EC2 for servers and S3 for assets and storage but source code, I don’t trust aws that much yet.

@C0D4 that’s really interesting, I’d be curious to hear more about what you mean. Do you think the block storage is more robust then their version control? Or are you saying that you don’t fear losing your block storage as much as you’d fear losing your source code and commit history?

@benrooke block storage can be replaced, plus most of the files originate locally anyway.
they do have versioning on S3 which has come in handy in the pass so thats a bonus.

I’m just not the kind of person to hand 1 company my entire system from source to versions to assets, and pray it never goes south or missing.

Now that’s not to say that codeCommit isn’t a useful product or a good alternative.

@C0D4 hey thanks for responding. Yeah, I was super curious. I think it makes sense. I personally don’t use AWS’s code commit service either.

@C0D4 @benrooke I really appreciate your guy’s thoughts on this and I can totally see the benefit of not putting all of my eggs into 1 basket. Once I can afford to pay for a github account I’ll move stuff back over there. (I’m just embarrassed of my crappy code and want to keep it a secret in a private repo until it’s decent enough to release it out into the wild 😜)

@TerraNimbus-io Haha I know what you mean. Have you taken a look at BitBucket?

@benrooke we used it at my last job, it was alright but I didn’t care for it all too much. But I may not have had enough exposure to it.