• 3 Votes
    18 Posts
    4k Views
    AdamFA

    Looking at the details page, here is a limitation depending on how you handle client accounts, or your own accounts.

    What are the Lightsail service limits?
    You can currently create up to 20 Lightsail instances, 5 static IPs, and 3 DNS domain zones in a Lightsail account.

    But this is pretty cool. Ability to manage traffic before it hits your VPS:

    Can I manage firewall settings for my instance?
    .
    You can control the data traffic for your instances by using the Lightsail firewall. From the Lightsail console, you can set rules about which ports of your instance are publicly accessible for different types of traffic.

  • 1 Votes
    48 Posts
    15k Views
    handsofqwertyH

    @thecreativeone91 said:

    @scottalanmiller said:

    @thecreativeone91 said:

    I just realized what the "Big red V" is....

    Not to be confused with the big pink V.

    And what is that?

    I have no idea either.

  • 4 Votes
    5 Posts
    2k Views
    scottalanmillerS

    @JaredBusch said:

    @scottalanmiller said:

    @thecreativeone91 said:

    How come they don't fail over the VMs to another server, then update the original server move them back and so on as to make it an update with no down time?

    Cloud is not high availability. That's a very common misconception. Cloud is beneath the HA layer. Anyone who had HA stayed up and running, of course, but cloud itself is not HA.

    They easily could have chosen to do so, but the workload would not offset the cost I am sure.

    Not really, because you can only do so much HA at that layer. Not every workload can be made HA in that way. But more importantly, HA is always an option and most importantly, HA is something you do, not something that you buy. But anyone who had an outage, like us, chose to not pay for HA because it is cheaper to have blips than to have the cost of HA.

    It's really the end users who opted out of HA.