aboutsummaryrefslogtreecommitdiffstats
path: root/readme.md
diff options
context:
space:
mode:
authorMichael Chandler <mchandler89@gmail.com>2019-10-06 09:13:01 +1000
committerMichael Chandler <mchandler89@gmail.com>2019-10-06 09:13:01 +1000
commit3c727a0b0f28e0aaaa09d9c3f763b86279ac4e4c (patch)
treea6649cc66a79e9578444ee3aad805060c2fc02ba /readme.md
parenta51634655cebd9660757360ceff543b273d44bcf (diff)
Add note about stack getting stuck on CREATE_IN_PROGRESS.
Diffstat (limited to 'readme.md')
-rw-r--r--readme.md8
1 files changed, 8 insertions, 0 deletions
diff --git a/readme.md b/readme.md
index 05267ef..f7503d6 100644
--- a/readme.md
+++ b/readme.md
@@ -121,6 +121,14 @@ Be sure to check out factoriotools's repositories on Docker Hub and GitHub. Unle
- Docker Hub: https://hub.docker.com/r/factoriotools/factorio/
- GitHub: https://github.com/factoriotools/factorio-docker
+### Stack gets stuck on CREATE_IN_PROGRESS
+
+It may be because the `m3.medium` instance is not available in your region. As a result of this, an auto-scaling group gets successfully created - however it never launches an instance. This means the ECS service cannot ever start, as it has nowhere to place the container. I would suggest going to the AWS Console > EC2 > Spot Requests > Pricing History, and find a suitable instance type that's cost effective and has little to no fluctuation in price.
+
+In the below example (Paris), `m5.large` looks like a good option. Try to create the CloudFormation stack again, changing the InstanceType CloudFormation parameter to `m5.large`. See: https://github.com/m-chandler/factorio-spot-pricing/issues/10
+
+![Spot pricing history](readme-spot-pricing.jpg?raw=true).
+
### Basic Docker Debugging
If you SSH onto the server, you can run the following commands for debugging purposes:
send patches to the email below
yukais@pinapelz.com
include the subject [PATCH repo_name]
pinapelz.com
homepage