testdrivenio / django-ecs-terraform Goto Github PK

Following your awsome article mate 👍

Ready?!? View then execute the plan:
$ terraform plan
$ terraform apply

After Terraform apply I've got an error that Need at least 4 healthy instances in ASG, have 0.

ws_autoscaling_group.ecs-cluster: Still creating... [10m10s elapsed]

Error: "production_auto_scaling_group": Waiting up to 10m0s: Need at least 4 healthy instances in ASG, have 0. Most recent activity: {
  ActivityId: "9f05d49d-82b4-9711-3dc4-015de4ab3b25",
  AutoScalingGroupName: "production_auto_scaling_group",
  Cause: "At 2020-10-14T13:50:47Z an instance was started in response to a difference between desired and actual capacity, increasing the capacity from 0 to 4.",
  Description: "Launching a new EC2 instance.  Status Reason: The requested configuration is currently not supported. Please check the documentation for supported configurations. Launching EC2 instance failed.",
  Details: "{\"Subnet ID\":\"subnet-0f21a4e93054e04c2\",\"Availability Zone\":\"us-east-2a\"}",
  EndTime: 2020-10-14 13:50:48 +0000 UTC,
  Progress: 100,
  StartTime: 2020-10-14 13:50:48.613 +0000 UTC,
  StatusCode: "Failed",
  StatusMessage: "The requested configuration is currently not supported. Please check the documentation for supported configurations. Launching EC2 instance failed."
}

I see that most testdrivenio repos have MIT License but this repo has none. I would like to use this example as a basis for a small project, but without license there is no point.

Do you think you could add MIT License for this repo as well?

BTW - Are you going to create a course about this project in here https://testdriven.io/courses/ ? I would like to buy it but didn't see it there.

I was unable to ssh into an ec2-instance running in ECS cluster (operation timeout error).
When I changed the target of the VPC route table 0.0.0.0/0 to Internet Gateway of the VPC from the NAT Gateway, I could access the ec2-instance. I could not figure out why this was happening.
When I change the target to NAT Gateway again, the whole system works as expected.

This is an excellent tutorial -- thank you very much!

Everything goes very smoothly, apart from logging into the django admin site. There doesn't seem to be a superuser. Is one created -- and if so where is its username and password?

If not, what would be the best way to create one? Could I set up a "aws_ecs_task_definition" to create a superuser?

It appears after deploying and ssh'ing into one of the machines, the directory specified for the static files: /usr/src/app/staticfiles/ is not showing anything inside. If I run the command after docker is pushed and the image is swapped, then the files show up without issue. However, just running the deploy scripts and pushing the new images doesn't seem to do anything.

• GET
• POST
• DELETE

I keep getting a 503 error .. I've followed the tutorial several times and even cloned the repo but still this error persist for me

hello,

is it possible to add celery tasks in this as well?

Thanks