4 ms·

They are not rotating capacity for updates. They are patching a Xen security issue that will be announced on Oct 1. That is why they are rebooting machines and

They are not rotating capacity for updates. They are patching a Xen security issue that will be announced on Oct 1. That is why they are rebooting machines and not forcing moves off of those machines. Otherwise, I agree with the advice.

deleted 12y ago
[deleted]
coolbeans01 12y ago
Could you please confirm or provide evidence for such speculation? I don't see anything about this on google. I heard it is because they are having power issues within their datacenter.
- jabo 12y ago
  May be this: http://xenbits.xen.org/xsa/ http://xenbits.xen.org/xsa/ XSA-108 2014-10-01 12:00 (Prereleased, but embargoed)
  - coolbeans01 12y ago
    Cool speculation! Anyone with anything concrete? I still heard it is power issues.
    - reedloden 12y ago
      Not sure how power issues would affect every single region. Logic dictates it's likely a security issue.
    - jsmthrowaway 12y ago
      I'd just like to point out that you asked for concrete, then speculated based on something you heard.
    - aioprisan 12y ago
      Aren't you speculating as well?
- mdellabitta 12y ago
  Restarting an instance (not stop-start) doesn't change the hardware you're on, so I don't think this has a physical explanation.
  - tehmasp 12y ago
    all of our instances scheduled for maint. are indeed system-reboot event types; it is indeed a stop/start situation. stop/start can possibly put you on another physical - but it all depends on how aws has setup the hypervisors and their instance schedulers. this, the maint from aws, appears to be security related - but that doesn't mean that aws is not getting folks off of old hardware if they have that desire.
    - mdellabitta 12y ago
      I think it's more complicated than that. Because Amazon is claiming that if you let them handle it, you keep your instance data. That's not a stop-start (at least what we ordinary users can do). It's more like a system restart with a little downtime managed by them. You can try a stop-start yourself, but it's not guaranteed to help. And a restart yourself doesn't do anything.
- count 12y ago
  within their datacenter? Wtf? Do you have any idea how big AWS is?

deleted 12y ago

[deleted]

coolbeans01 12y ago

Could you please confirm or provide evidence for such speculation? I don't see anything about this on google. I heard it is because they are having power issues within their datacenter.

jabo 12y ago
May be this: http://xenbits.xen.org/xsa/ http://xenbits.xen.org/xsa/ XSA-108 2014-10-01 12:00 (Prereleased, but embargoed)
- coolbeans01 12y ago
  Cool speculation! Anyone with anything concrete? I still heard it is power issues.
  - reedloden 12y ago
    Not sure how power issues would affect every single region. Logic dictates it's likely a security issue.
  - jsmthrowaway 12y ago
    I'd just like to point out that you asked for concrete, then speculated based on something you heard.
  - aioprisan 12y ago
    Aren't you speculating as well?
mdellabitta 12y ago
Restarting an instance (not stop-start) doesn't change the hardware you're on, so I don't think this has a physical explanation.
- tehmasp 12y ago
  all of our instances scheduled for maint. are indeed system-reboot event types; it is indeed a stop/start situation. stop/start can possibly put you on another physical - but it all depends on how aws has setup the hypervisors and their instance schedulers. this, the maint from aws, appears to be security related - but that doesn't mean that aws is not getting folks off of old hardware if they have that desire.
  - mdellabitta 12y ago
    I think it's more complicated than that. Because Amazon is claiming that if you let them handle it, you keep your instance data. That's not a stop-start (at least what we ordinary users can do). It's more like a system restart with a little downtime managed by them. You can try a stop-start yourself, but it's not guaranteed to help. And a restart yourself doesn't do anything.
count 12y ago
within their datacenter? Wtf? Do you have any idea how big AWS is?