News for hackers. Stuff that matters.
Re:Launched a service around automation for AWS tasks. Would... by abcd_f on Wednesday February 05, 2014 @02:07PM (#7185972)
Selecting anything from yellow droplist yields gigantic "PLEASE SIGN-UP TO PROCEED" popup that cannot be dismissed. Selected item is not getting selected, all other droplists are either disabled or obscured by the POPUP.

This is how you drive people off your website, not get them interested enough to sign-up for a trial account :)

Re:Launched a service around automation for AWS tasks. Would... by icecommander on Wednesday February 05, 2014 @02:18PM (#7186071)
We can't populate those other dropdowns at that time because they're based on real values. Here's what a filled-in set looks like: http://i.imgur.com/tMLtncD.png
Re:Launched a service around automation for AWS tasks. Would... by rpedela on Wednesday February 05, 2014 @03:23PM (#7186530)
Well then I would recommend a video or screenshot instead, or just populate with fake data. I personally just wanted to see what the possible values could be.

I know the service is new so I am giving you the benefit of the doubt. But if I came to your website from Google or a news article, I would be immediately turned off by that giant sign-up popup.

Re:Launched a service around automation for AWS tasks. Would... by icecommander on Wednesday February 05, 2014 @03:25PM (#7186543)
Thanks, we're going to address this in the next release.
Re:Launched a service around automation for AWS tasks. Would... by rpedela on Wednesday February 05, 2014 @03:31PM (#7186583)
No problem. I do see the service being useful and I think it has potential.
Re:Launched a service around automation for AWS tasks. Would... by throaway154 on Wednesday February 05, 2014 @03:44PM (#7186665)
Product seems useful.

However, as someone who has launched multiple products with the aim of improving on something inside AWS (some successful, some not), I want to warn you about pursuing this type of AWS-centric business model.

I can tell you from experience that if you start to see traction, AWS will not hesitate to rip it off and incorporate it into their console. A quick Google search will show a rich history of treating their "partners" in this fashion.

Be careful, and good luck!

Re:Launched a service around automation for AWS tasks. Would... by aaronpk on Wednesday February 05, 2014 @01:57PM (#7185891)
Is this creating autoscale groups and such on my behalf? Or is the automation being done by a service in finally.io?
Re:Launched a service around automation for AWS tasks. Would... by icecommander on Wednesday February 05, 2014 @01:59PM (#7185906)
Right now the automation is done by a service (no autoscaling groups are created on your behalf). Do you have triggers in mind that you would like to create autoscaling groups for you?
Re:Launched a service around automation for AWS tasks. Would... by aaronpk on Wednesday February 05, 2014 @02:03PM (#7185940)
No I mean that AWS provides a lot of this sort of automation internally, for example by configuring autoscale groups to respond to various cloudwatch metrics. I was wondering if finally.io is a UI layer on top of the existing AWS tools.
Re:Launched a service around automation for AWS tasks. Would... by icecommander on Wednesday February 05, 2014 @03:00PM (#7186394)
Our initial set of automation rules consists of things that are not readily doable with autoscaling. We do use the AWS APIs but I wouldn't consider what we do to be a UI layer. We automate things that are currently hard or impossible to do with the AWS console. A great example of this is scaling RDS storage or DynamoDB capacity based on actual use (and not just as a one-off operation).