1 Answer
- Newest
- Most votes
- Most comments
1
Hello Pritam,
There are a few issues that I see in your setup. Does your client not have source code management established and a CI/CD pipeline? Updating the code in EC2 instance actually defeats the autoscaling as manual intervention is needed.
You should suggest your customer to establish a CI/CD pipeline and establish triggers to push updated code to the servers automatically.
Of course there are options to sync the servers as well, but given that autoscaling will change server IPs it is not practical.
As far as I see it, the right solution is to establish CI/CD to update code.
answered 2 years ago
Relevant content
asked 3 years ago
- AWS OFFICIALUpdated 5 months ago

As the CI/CD is only capable when we have connect the server with CI/CD tools.
for Example as I'm using Jenkins for CI/CD i need to connect my server with Jenkins to perform any execution on my server. but in the auto-scaling server is created automatically then how i add those server in Jenkins or any CI/CD tools to perform the action over there ??
this is the deadlock situation for me where i actually stuck.
Actually tools like Jenkins are not needed for small and simple setup, you can establish a pipeline using scripts as well. I had setup a code update mechanism using shell scripts and cron. You can keep things simple as much as possible. For a small setup, tools only complicate the environments.
Hi Good Morning Mukul,
thanks for your Guidance, but can you please share the script part with me so, i can check if that part can help me on this scenario it's a big help for me !!
waiting for your reply !!
Hello Pritam,
I have shared the source code on GitHub. Please fork, copy, or otherwise use (responsibly) from my repository. Look for a shell script called mdgitpull.sh and you can tailor it for your own needs.