We have important news about your account (AWS Account ID: xxxxxxxxxxxx). EC2 has detected degradation of the underlying hardware hosting your Amazon EC2 instance (instance-ID: i-xxxxxxxx) in the ap-northeast-1 region. Due to this degradation, your instance could already be unreachable. After 2017-04-25 04:00 UTC your instance, which has an EBS volume as the root device, will be stopped.
You can see more information on your instances that are scheduled for retirement in the AWS Management Console (https://console.aws.amazon.com/ec2/v2/home?region=ap-northeast-1#Events)
* How does this affect you? Your instance's root device is an EBS volume and the instance will be stopped after the specified retirement date. You can start it again at any time. Note that if you have EC2 instance store volumes attached to the instance, any data on these volumes will be lost when the instance is stopped or terminated as these volumes are physically attached to the host computer
* What do you need to do? You may still be able to access the instance. We recommend that you replace the instance by creating an AMI of your instance and launch a new instance from the AMI. For more information please see Amazon Machine Images (http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/AMIs.html) in the EC2 User Guide. In case of difficulties stopping your EBS-backed instance, please see the Instance FAQ (http://aws.amazon.com/instance-help/#ebs-stuck-stopping).
* Why retirement? AWS may schedule instances for retirement in cases where there is an unrecoverable issue with the underlying hardware. For more information about scheduled retirement events please see the EC2 user guide (http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-retirement.html). To avoid single points of failure within critical applications, please refer to our architecture center for more information on implementing fault-tolerant architectures: http://aws.amazon.com/architecture
If you have any questions or concerns, you can contact the AWS Support Team on the community forums and via AWS Premium Support at: http://aws.amazon.com/support
Sincerely, Amazon Web Services
AWS Console イベントを見ると一覧で表示されている。
AWS Console 詳細を見ると Notice が出ている。
ToDO
ボリュームタイプによって異なります。
EBS ボリューム
インスタンスの停止後、起動 (Reboot は ×)
インスタンスストアボリューム
AMI からインスタンス再作成、データ移行
今回は EBS ボリューム対応について記載してます。
対応
対象インスタンスが多かったのでローカル PC (macOS) から awscli でインスタンス停止 → 起動するシェル作成しました。 本番環境で利用されるインスタンスも含まれていた為、1 件ずつ実行することとしました。
@app.route('/') defhello(): count = redis.incr('hits') #return 'Hello World! I have been seen {} times.\n'.format(count) return'Hello from Docker! I have been seen {} times.\n'.format(count)
if __name__ == "__main__": app.run(host="0.0.0.0", debug=True)
requirements.txt 作成
pip でインストールするモジュールを列挙します。
1 2
flask redis
Dockerfile 作成
1 2 3 4 5
FROM python:3.4-alpine ADD . /code WORKDIR /code RUN pip install -r requirements.txt CMD ["python", "app.py"]
Enter file in which to save the key (/Users/kenzo_tanaka/.ssh/id_rsa): /Users/kenzo_tanaka/.ssh/terraform-test Enter passphrase (empty for no passphrase): (空のままEnter) Enter same passphrase again: (空のままEnter) ... ...
variable "key_name" { description = "Desired name of AWS key pair" }
variable "public_key_path" { description = <<DESCRIPTION Path to the SSH public key to be used for authentication. Ensure this keypair is added to your local SSH agent so provisioners can connect.
$ cd /usr/local/prometheus-server $ cat << 'EOF' > alerts.rules
# インスタンスに 5分以上(FOR) アクセスできない場合(IF up == 0) # severity = "critical" とラベル付けし通知 ALERT InstanceDown IF up == 0 FOR 5m LABELS { severity = "critical" } ANNOTATIONS { summary = "Instance {{ $labels.instance }} down", description = "{{ $labels.instance }} of job {{ $labels.job }} has been down for more than 5 minutes.", }
![AWS [Retirement Notification] 対応](https://cdn-ak.f.st-hatena.com/images/fotolife/k/kenzo0107/20170418/20170418105821.png)
