I have container A this container holds my broker service that delivers messages and creates a socket that my other services connect to and then send messages t
Problem Getting target type ip,which is incompatible with the bridge network mode error when trying to create an ECS service with an existing NLB whose target
I get this error when applying terraform. It's clearly something wrong with my env_Vars. I've tried making name and value in quotes or without. Error: ECS Task
I'm trying to setup via CloudFormation an EFS mount for self-hosted Prometheus. Below is the CloudFormation for my setup: Resources: ServiceSecurityGroup:
I have a Docker Image built with the following CMD # Dockerfile ... CMD ["nginx", "-g", "daemon off;"] When my task definition does not include entryPoint or c
I am trying to implement a proxy to our Aurora RDS instance, but having difficulty getting the IAM access to work properly. We have a microservice in an ECS con
If a ECS container is out of memory or is in hung state or stopped thought is gets restarted. is there a way to I se up alarms on top of that using cloudwatch o
I am following this tutorial: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-cli-tutorial-fargate.html the json for a policy is as shown: {
I tried to make the construction like figure1. figure1 In the local environment, I can access http://127.0.0.1 after running docker-compose up -d --build. And I
I have setup an ECS Cluster and I'm using ECS CLI to create services/tasks from my existing docker-compose file. This is how my compose file looks like: version
1- I have a project core-infra that encapasses all the core infra related compoents (VPCs, Subnets, ECS Cluster...etc) 2- I have microservice projects with inde
Setup Security Groups ALB (inbound rules) HTTPS:443 from 0.0.0.0/0 & ::/0 HTTP:80 from 0.0.0.0/0 & ::/0 Cluster (inbound rules) All traffic from ALB se
I am trying to run a private repository on aws-ecs-fargate-1.4.0 platform. For private repository authentication, I have followed the docs and it was working w
I have a docker image I want to run on AWS ECS. This is a API I want to use from other applications. I have set up the task definition, however it runs for a fe
I am trying to deploy my docker image in AWS ECS. I have created the ECR repository and done all required steps till pushing the image to ECS. My docker-compose
I'm having a fargate cluster with a service having two containers: a container running nginx for terminating mTLS (it accepts a defined list of CAs) and forwar
Can one service in ECS cluster c1 can call another service in cluster c2 using ECS service discovery (https://docs.aws.amazon.com/AmazonECS/latest/developergui
My CDK stack with a Fargate task won't start, tasks stop directly with the error: "standard_init_linux.go:228: exec user process caused: exec format error" I
When creating ECS infrastructure we describe our Task Definitions with CloudFormation. We want to be able to dynamically pass environment variables as a paramet
When trying to deploy my multi-docker application through beanstalk with a dockerrun.aws.json file, where it has secrets, I get an error that I have to specify