5 ms·

Just to make sure I'm reading this right, the upfront reservation fees are higher, but the reserved hourly rates dropped a good bit. It's cheaper over the durat

by gtaylor 13y ago

Just to make sure I'm reading this right, the upfront reservation fees are higher, but the reserved hourly rates dropped a good bit. It's cheaper over the duration of the reservation, but you owe more of the term upfront. Given this tidbit, might you reserve an instance now, pay the lower fee, but still take advantage of the new hourly rates on April 1? Or are you locked in at whatever rate your reservation is for?

nirvdrum 13y ago
You're locked into whatever rate your reservation is for. This is why you see rate fluctuations on the marketplace for the same instance type. It's also why a 3 year reservation may not make sense.
- gtaylor 13y ago
  That makes sense, thanks for the clarification. Bummer, though. We just reserved a multi-AZ m3.large RDS instance last week. I wish AWS would take up Google's system of graduated price reductions over steady run duration.
  - nirvdrum 13y ago
    The other fun tidbit is on heavy reservations you pay per-hour even if you're not using the machine. That's not the case for the light or medium. So keep that in mind when planning out your reservations. When we switched off EC2 it was financially advantageous to basically give away our heavy instances on the marketplace just to shed the liability.
    - gtaylor 13y ago
      After this latest round of price cuts, I'm starting to question whether I even want to reserve instances on the lower end. An m3.medium is about $52/month on demand vs $35/month (amortized over 12 months with a 1-year heavy usage reservation). In this example, it becomes a question of whether it's worth saving $130'ish a year for the liability that a 1-year m3.medium heavy util reservation represents. At the lower end, that's not a huge amount of liability, but it may be a case where I just don't bother reserving m3.mediums anymore because it's a wash.
      - Aqua_Geek 13y ago
        Maybe my math is off, but I calculated $35/mo for medium utilization m3.medium vs $32/mo for heavy utilization. In that case, I don't think a heavy utilization reservation makes sense but a medium utilization reservation still might (as you're saving ~$20/mo over on-demand).
    - msmithstubbs 13y ago
      I tried to give away a heavy instance in the past but to sell on the Reserved Instance marketplace you must have a US bank account. Worth noting if you are considering heavy instances and are based outside the US. You will be stuck with them for the life of the reservation term.
  - eropple 13y ago
    That's when you talk to an AWS account rep and twist their arm a bit.
    - ceejayoz 13y ago
      Hell, in my experience, you don't even have to twist much. They're usually pretty happy to do a "just this once..." sort of thing.
nkvoll 13y ago
How I'm reading this, both up-front reservation fees and the hourly rates are lower for a lot of instance types. For example: Now: m3.xlarge $1266 $0.105 per Hour $1922 $0.086 per Hour April 1st: m3.xlarge $886 $0.074 per Hour $1345 $0.06 per Hour It sounds weird if Amazon is actually going to keep charging the higher rate to existing customers, as they've already paid the higher reservation fee as well.

by gtaylor 13y ago

nirvdrum 13y ago

You're locked into whatever rate your reservation is for. This is why you see rate fluctuations on the marketplace for the same instance type. It's also why a 3 year reservation may not make sense.

gtaylor 13y ago
That makes sense, thanks for the clarification. Bummer, though. We just reserved a multi-AZ m3.large RDS instance last week. I wish AWS would take up Google's system of graduated price reductions over steady run duration.
- nirvdrum 13y ago
  The other fun tidbit is on heavy reservations you pay per-hour even if you're not using the machine. That's not the case for the light or medium. So keep that in mind when planning out your reservations. When we switched off EC2 it was financially advantageous to basically give away our heavy instances on the marketplace just to shed the liability.
  - gtaylor 13y ago
    After this latest round of price cuts, I'm starting to question whether I even want to reserve instances on the lower end. An m3.medium is about $52/month on demand vs $35/month (amortized over 12 months with a 1-year heavy usage reservation). In this example, it becomes a question of whether it's worth saving $130'ish a year for the liability that a 1-year m3.medium heavy util reservation represents. At the lower end, that's not a huge amount of liability, but it may be a case where I just don't bother reserving m3.mediums anymore because it's a wash.
    - Aqua_Geek 13y ago
      Maybe my math is off, but I calculated $35/mo for medium utilization m3.medium vs $32/mo for heavy utilization. In that case, I don't think a heavy utilization reservation makes sense but a medium utilization reservation still might (as you're saving ~$20/mo over on-demand).
  - msmithstubbs 13y ago
    I tried to give away a heavy instance in the past but to sell on the Reserved Instance marketplace you must have a US bank account. Worth noting if you are considering heavy instances and are based outside the US. You will be stuck with them for the life of the reservation term.
- eropple 13y ago
  That's when you talk to an AWS account rep and twist their arm a bit.
  - ceejayoz 13y ago
    Hell, in my experience, you don't even have to twist much. They're usually pretty happy to do a "just this once..." sort of thing.

nkvoll 13y ago

How I'm reading this, both up-front reservation fees and the hourly rates are lower for a lot of instance types. For example: Now: m3.xlarge $1266 $0.105 per Hour $1922 $0.086 per Hour April 1st: m3.xlarge $886 $0.074 per Hour $1345 $0.06 per Hour It sounds weird if Amazon is actually going to keep charging the higher rate to existing customers, as they've already paid the higher reservation fee as well.