Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running Snibox on AWS ECS #8

Open
mmillican opened this issue Oct 12, 2020 · 0 comments
Open

Running Snibox on AWS ECS #8

mmillican opened this issue Oct 12, 2020 · 0 comments

Comments

@mmillican
Copy link

I'm trying to run Snibox (Docker) version on AWS Elastic Container Service. I have the container host built and its working as far as I can tell. However, when I try to deploy Snibox to it, the frontend keeps failing with the error:

nginx: [emerg] host not found in upstream "backend:3000" in /etc/nginx/conf.d/default.conf:17

Here is my ecs-params.yml file which "complements" the docker-compose.yml file:

version: 1
task_definition:
  task_role_arn: ecs-cluster-dev-ECSRole-XXXXXX
  task_execution_role: ecs-cluster-dev-ECSRole-XXXXXX
  services:
    frontend:
      cpu_shares: 5
      mem_limit: 256
      volumesFrom:
        - ContainerName: backend
          Readonly: false
    
    backend:
      cpu_shares: 5
      mem_limit: 512

    database:
      cpu_shares: 10
      mem_limit: 512
  
  docker_volumes:
    - name: 'pg-data'
      scope: 'shared'
      autoprovision: true
    - name: 'static-files'
      scope: 'shared'
      autoprovision: true
run_params:
  network_configuration:
    awsvpc_configuration: 
      subnets:
        - subnet-XXXXXX
        - subnet-XXXXXX

Note that the dependsOn option is not valid in ECS, so its essentially ignored. I read that you can use volumesFrom instead, but that doesn't seem to change anything.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant