I started migrating my servers from Linode to Hetzner Cloud this month, but noticed that my quota only gave me ten instances.

I need many more, probably on the order of 25 right now and probably more later. I’d also like the ability to create test servers, etc.

I asked for an increase with all of that in mind, and Hetzner replied:

“As we try to protect our resources we are raising limits step by step and on the actuall [sic] requirement. Please tell us your currently needed limit.”

I don’t understand. Does Hetzner not have enough servers to accommodate me? Wouldn’t knowing the size of the server be relevant if it’s an actual resource question?

I manage a very large OpenStack cluster for my day job and we just give people what they pay for. I’m having a hard time wrapping my head around this unless Hetzner might not be able to give me what I ultimately want to pay for, and if that’s the case, I wonder if they’re the right solution for me after all.

It also makes me worry about cloud elasticity.

Does anyone have any insights that can help me understand why keeping a low limit matters?

  • @vsisEnglish
    11•11 months ago

    A posible attack from an untrusted client, is to create a lots of VMs in a short period of time.

    1440 VMs running for a minute cost the same as a single one running for a day. 43200 VMs running for a minute cost the same as a single one running for a month.

    Therefore, attacks are kinda cheap, specially if you are paid by the competence.

    So, for an untrusted client, the best is to limit the maximum number of VMs she can create.

    AWS does something similar. I recall something like 20 VMs as the limit for a new client.

    Edit: Here are AWS docs about that: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-resource-limits.html