With some trial and error, seems these are us-east-1 AMIs. The last one you
shared is indeed too new - this wont work. (2024-08-21).
{
"body": {
"VirtualizationType": "hvm",
"Description": "Amazon Linux AMI 2.0.20240821 x86_64 ECS HVM GP2",
"Hypervisor": "xen",
"ImageOwnerAlias":
*Something* must have changed, e.g you changed AMI, or when instances start
they now upgrade pre-installed software during cloud-init to different
versions of pre-installed tools. In future, you need to share the specific
name of the AMI, the release date and the region etc - an AMI ID on its own
i
Hi Sriram,
- does the ECS consumer get created and registered if you remove the user
data script? : *yes*.
We have taken marketplace AMI: ami-0a5f593ecaa0f722d , if we create
the server manually via the launch template and added to the ECS cluster,
its works. the same step if we are doi
( I am ill so please excuse the limited questions)
- does the ECS consumer get created and registered if you remove the user
data script?
- what changed between when this ECS used to work vs now?
— Sriram
On Tue, 3 Sep 2024 at 7:23 PM, pradeep devaraj
wrote:
> Hi Team / Chad Wilson.
>
> Docker
Hi Team / Chad Wilson.
Docker service and ECS service is failing when new server comes up. AMI id:
ami-0a5f593ecaa0f722d community one. when we manully spin the server and
attach via ASG it's registering to cluster. when we try the same from gocd
ecs cluster profile(AWS ECS ELastic plugin) i
Adding++
we are getting the agnet creation and deletion in loop
[go] Received a request to create an agent for the job:
[SpecOps_UAT_Elastic_Img_crt/6/test/1/test]
[go] No running instance(s) found to build the ECS Task to perform current
job.
[go] Creating a new container instance to schedule
