ECS Plugin issues

7 views
Skip to first unread message

ashok reddy C k

unread,
Feb 23, 2026, 12:54:57 PM (13 hours ago) Feb 23
to Chad Wilson, go...@googlegroups.com
Hi Chad/GoCD Team,

We are using the following plugins and base image as centos-9,AWS optimized AMI 


GoCD Elastic Agent Plugin for Amazon ECS Version

9.0.0-896

  • DockerVersion: 20.10.25
  • 1.84.0
issues 1) ECS Ec2 servers, we have given 12 as max in the cluster profile But it's shown max 10 servers in the error logs

2026-02-19 02:05:41,739 INFO  [899991@MessageListener for ServerPingListener] ECSElasticPlugin:72 - [server-ping] Cluster has total 12 LINUX instances which is beyond permissible limit(10). Terminating idle instances.

 
is there any way to limit extend? due to this max as 12 , ui showed 11 , keep on one ec2 server, span up and terminating..... Is there any way to limit the extension? Due to a maximum of 12, the UI shows like (10),(11),(12)...etc. We need to keep on one EC2 serverspinning up and terminating instances. During this time, jobs or pipelines are being assigned to terminated instances. 2) ec2 servers are not terminated as we expected in profile time intervals
  • 60
  • 2
manually terminating the ECS Ec2 servers Production jobs were delayed last week by 40 minutes due to this terminated server registered for the task(out of 12 to 10 )

3)Regarding ECS EC2 tasks, is there a way to assign them equally across each EC2 server?

For example, if there are 5 servers and 50 tasks, can we configure it so that each server runs 10 tasks? Please find the attachment screenshots via a separate email ECS Ec2 server is registered and healthy but container is not assigned image.png regarding above issues we have connected to AWS support team ECS EC2 these 2 teams said ec2 and ec2 cluster is healthy , issue with plugins (go-agent)
  • 
    
Reply all
Reply to author
Forward
0 new messages