amazon-ecs

问题 In Re:Invent 2018, AWS seems to have launched new integrations with Step Functions, which includes ECS Fargate support. https://docs.aws.amazon.com/step-functions/latest/dg/connectors-ecs.html I have been digging up on this, and I am able to get the ECS task to startup, and do its thing, but I am not able to send desired output back to the step function. The response syntax too does not seem to have anything that corresponds to the output of a particular state. https://docs.aws.amazon.com

问题 In Re:Invent 2018, AWS seems to have launched new integrations with Step Functions, which includes ECS Fargate support. https://docs.aws.amazon.com/step-functions/latest/dg/connectors-ecs.html I have been digging up on this, and I am able to get the ECS task to startup, and do its thing, but I am not able to send desired output back to the step function. The response syntax too does not seem to have anything that corresponds to the output of a particular state. https://docs.aws.amazon.com

问题 I'm looking for a way to inject secrets/certificates into Amazon ECS containers. In my case, it's a simple nginx container. I've been following this post, using AWS Parameter Store: https://aws.amazon.com/blogs/compute/managing-secrets-for-amazon-ecs-applications-using-parameter-store-and-iam-roles-for-tasks/ Here's the basic gist: On my Dockerfile, I attach a script on entrypoint which installs the AWS client and fetches the keys from AWS parameter store. Dockerfile FROM nginx:1.16.0 ...

问题 I've recently started using Docker for my own personal website. So the design my website is basically Nginx -> Frontend -> Backend -> Database Currently, the database is hosted using AWS RDS. So we can leave that out for now. So here's my questions I currently have my application separated into different repository. Frontend and Backend respectively. Where should I store my 'root' docker-compose.yml file. I can't decide to store it in either the frontend/backend repository. In a docker

问题 I need to implement a reverse proxy/redirect service for site which will be hosted in AWS S3 (static JS assets) + CloudFront and multiple backends running as different tasks AWS ECS available at domain.com/api/session_number Redirect or reverse proxy service should analyze input parameter and redirect to corresponding backend. So far I've found ECS-nginx-proxy but it looks more like the tool for dev/stage environments. How such service can be implemented for production using AWS services like

问题 I don't want to have to deploy a whole other ECS service just to enable X-Ray. I'm hoping I can run X-Ray on the same docker container as my app, I would have thought that was the preferred way of running it. I know there might be some data loss if my container dies. But I don't much care about that, I'm trying to stop this proliferation of extra services which serve only extra analytical/logging functions, I already have a logstash container I'm not happy about, my feeling is that apps

问题 I don't want to have to deploy a whole other ECS service just to enable X-Ray. I'm hoping I can run X-Ray on the same docker container as my app, I would have thought that was the preferred way of running it. I know there might be some data loss if my container dies. But I don't much care about that, I'm trying to stop this proliferation of extra services which serve only extra analytical/logging functions, I already have a logstash container I'm not happy about, my feeling is that apps

问题 I don't want to have to deploy a whole other ECS service just to enable X-Ray. I'm hoping I can run X-Ray on the same docker container as my app, I would have thought that was the preferred way of running it. I know there might be some data loss if my container dies. But I don't much care about that, I'm trying to stop this proliferation of extra services which serve only extra analytical/logging functions, I already have a logstash container I'm not happy about, my feeling is that apps

问题 I don't want to have to deploy a whole other ECS service just to enable X-Ray. I'm hoping I can run X-Ray on the same docker container as my app, I would have thought that was the preferred way of running it. I know there might be some data loss if my container dies. But I don't much care about that, I'm trying to stop this proliferation of extra services which serve only extra analytical/logging functions, I already have a logstash container I'm not happy about, my feeling is that apps

问题 I don't want to have to deploy a whole other ECS service just to enable X-Ray. I'm hoping I can run X-Ray on the same docker container as my app, I would have thought that was the preferred way of running it. I know there might be some data loss if my container dies. But I don't much care about that, I'm trying to stop this proliferation of extra services which serve only extra analytical/logging functions, I already have a logstash container I'm not happy about, my feeling is that apps