CODEWITHSUNDEEP
amazon-web-servicesamazon-ec2continuous-integrationgitlabgitlab-ci
Nika Kurashvili
Nika Kurashvili

Reputation: 6462

from gitlab ci/cd to AWS EC2

It's beens ome time since I've been trying to figure out the really easy way.

I am using gitlab CI/CD and want to move the built data from there to AWS EC2. Problem is i found 2 ways which both are really bad ideas.

  1. building project on gitlab ci/cd, then ssh into the AWS, pull the project from there again, and run npm scripts. This is really wrong and I won't go into details why.
  1. I saw the following: How to deploy with Gitlab-Ci to EC2 using AWS CodeDeploy/CodePipeline/S3 , but it's so big and complex.

Isn't there any easier way to copy built files from gitlab ci/cd to AWS EC2 ?

Upvotes: 0

Views: 1468

Answers (1)

peter n
peter n

Reputation: 1280

I use Gitlab as well, and what has worked for me is configuring my runners on EC2 instances. A few options come to mind:

  1. I'd suggest managing your own runners (vs. shared runners) and giving them permissions to drop built files in S3 and have your instances pick from there. You could trigger SSM commands from the runner targeting your instances (preferably by tags) and they'll download the built files.
  2. You could also look into S3 notifications. I've used them to trigger Lambda functions on object uploads: it's pretty fast and offers retry mechanisms. The Lambda could then push SSM commands to instances. https://docs.aws.amazon.com/AmazonS3/latest/dev/NotificationHowTo.html

Upvotes: 2

Related Questions