Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
alien_
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
32 ms
·
151.
▲
Show HN: AutoSpotting now supports the Ohio AWS region and new instance types
(blog.cloudprowess.com)
1 points
by
alien_
10y ago
|
0 comments
152.
▲
Why API Gateway is mot yet ready for production and how it could be fixed
(blog.cloudprowess.com)
2 points
by
alien_
10y ago
|
0 comments
153.
▲
by
alien_
10y ago
The AMI creation is only needed if you store data on the machines, which you shouldn't do anyway, not even with on-demand ones. You should always try to keep the instances stateless and store any data outside the instances, such as on
154.
▲
Show HN: AutoSpotting is now open source
(github.com)
1 points
by
alien_
10y ago
|
0 comments
155.
▲
by
alien_
10y ago
Now also open source and available on GitHub: https://github.com/cristim/autospotting
156.
▲
by
alien_
10y ago
The latest version is adding support for EC2 Classic security groups and full-blown launch configuration setups which as of now make it usable enough for environments of real-life complexity.
157.
▲
Major update of AutoSpotting, an AutoScaling-friendly EC2 spot market bidder
(mcristi.wordpress.com)
2 points
by
alien_
10y ago
|
2 comments
158.
▲
by
alien_
10y ago
I've looked in a bit more detail and it seems to attach the nodes to the ELB used by the AutoScaling group, while I am attaching them to the group itself, which indirectly adds them to the load balancer. I'm curious how does that
159.
▲
by
alien_
10y ago
I didn't know about that one, indeed, it seems pretty similar.
160.
▲
by
alien_
10y ago
It's because so far I am only considering replacing the nodes slowly, one at a time, mostly in order not to hit any soft limits that may be defined on the account(like total number of instances), but also in order to give the user the
161.
▲
by
alien_
10y ago
Yes, but I actually did start a few weeks before the spot fleet was launched. The problem with the spot fleet 1) it's kind of awkward to use 2) it has statically defined capacity so you can't scale it 3) it has a static bid pri
162.
▲
by
alien_
10y ago
With my approach the AutoScaling group would always replace failed instances with the on-demand ones identical to those initially defined on the group's launch configuration. All I do is I later attempt to replace them with whatever I
163.
▲
My take at making AWS EC2 cheaper by automating SPOT instances with AutoScaling
(mcristi.wordpress.com)
83 points
by
alien_
10y ago
|
33 comments