Skip to content
#

spot-instances

Here are 64 public repositories matching this topic...

Saves up to 90% of AWS EC2 costs by automating the use of spot instances on existing AutoScaling groups. Installs in minutes using CloudFormation or Terraform. Convenient to deploy at scale using StackSets. Uses tagging to avoid launch configuration changes. Automated spot termination handling. Reliable fallback to on-demand instances.

  • Updated Oct 1, 2020
  • Go
spotty
MiroFurtado
MiroFurtado commented Jun 22, 2019

In more managed environments, you don't always have the flexibility to create your own IAM role versus use the one that is assigned to you. Spotty should have the ability to use an already existing IAM role if it has the right permissions.

Opening this as an issue so I can keep track of it, I'll be submitting a pull request next week likely.

tcagkansokmen
tcagkansokmen commented Sep 9, 2020

"var/app/current/storage/logs/laravel.log" could not be opened. failed to open stream: permission denied.

How can we solve this?

I added

13_permissions:
# fix permissions on the Laravel app folder
command: "chmod 777 -R /var/app/current/storage/logs/"
cwd: "/var/app/current/storage/logs/"

Line to deploy.config, but has no help.

Improve this page

Add a description, image, and links to the spot-instances topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the spot-instances topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.