amazon-ecs-agent | Amazon Elastic Container Service Agent | AWS library

I can't access a running docker image from outside of the EC2 instance.

• I created a cluster in ECS, a service with a related task definition and an Application Load Balancer.
• When the task gets executed I can see the logs from the Docker image in the task:
• I also see the related EC2 instance running. When I ssh into the instance I can see the docker image running, as expected:

We want to build an ECS cluster with the following characteristics:

1. It must run inside a VPC, then, we need the awsvpc mode
2. It must use GPU instances, so we can't use Fargate
3. It must provision dynamically the instances, therefore, we need a capacity provider
4. It will run tasks (batch jobs) that are going to be triggered directly through the AWS ECS API. For this reason, we don't need a service, only a task definition.
5. These tasks must have access to S3 (internet), so according to AWS documentation the instances must be placed inside a private subnet (a reference to docs).

We've already read this post in stackoverflow where it says that we need to set up a private subnet with a route table that points to a NAT Gateway configured in a public subnet, and this public subnet should point to an internet gateway. We already have this configuration. We also have an S3 vpc endpoint configured in the route table.

Bellow, you can see some relevant configurations of the cluster in terraform (for the shake of simplicity I only put the relevant parts):

I'm trying to configure logentries for a Task Definition on AWS ECS As you can see here "logentries" is available for container instances.

However I can not find any documentation or example about how to configure it. I've seen examples of other drivers: https://docs.aws.amazon.com/AmazonECS/latest/userguide/example_task_definitions.html

So I've tried to set the needed parameters defined in this documentation in the aws console:

However when I try to run a task with this configuration I get:

service my-service was unable to place a task because no container instance met all of its requirements. The closest matching container-instance is missing an attribute required by your task. For more information, see the Troubleshooting section.

Any ideas?

When using a custom IAM Role as an ECS Task Definition'scustom execution role, our resulting Service wil fail to startup on our ECS instance due to an inability to initialize the CloudWatch logging driver. Specifically, we see the following errors from ECS agent in CloudWatch:

I used CodeFresh to build my Docker Image and push to AWS ECR.

I check my ECR, I can see the pushed there successfully.

I SSH into my EC2, I don't see any content there.

I've recently inherited a micro-service system that runs on the spring-boot and netflix stack on AWS ECS, I'm quite new to spring-boot and the netflix side of things. I'm trying to move this over from using statically defined ports to using dynamic ports so that we can better use existing machines, but I'm having trouble getting the microservices to register themselves in Eureka.

The services are still starting up fine, when they are getting marked as offline in Spring Boot Admin. When I click on the service name in Spring Boot Admin I see the following links on the top right

Using the ecs agent container on an Ubuntu instance, I am able to register the agent with my cluster.

I also have a service created in that cluster and task definitions as well. When I try to add a task to the cluster I get the useless error message:

I'am trying to make my aws elastic cluster service send logs to logentries. But I can't find any good documentation on how to do it.

When i create task definition I have the option to choose logentries as image below shows:

But where do I find this token? And do I have to do anything else?

All i can find on the topic is this: https://github.com/aws/amazon-ecs-agent/issues/1059

I'm using AWS ECS to deploy my group of docker containers and in bridge network mode all works perfectly but with a slow performance...

I've read that this problem resolves with a host network mode but if i use this, it causes an error on containers deploy (some of them), "CannotCreateContainerError: Container already exists".

Looking for the error, i've see that is caused by links in containers (https://github.com/aws/amazon-ecs-agent/issues/185) but i need it,

Any ideas of this?

Thanks a lot!