{"id":15361,"date":"2014-09-01T13:38:48","date_gmt":"2014-09-01T08:08:48","guid":{"rendered":"https:\/\/2thenew.xyz\/blog\/?p=15361"},"modified":"2014-09-01T13:40:39","modified_gmt":"2014-09-01T08:10:39","slug":"alarms-deletion-at-server-termination","status":"publish","type":"post","link":"https:\/\/2thenew.xyz\/blog\/alarms-deletion-at-server-termination\/","title":{"rendered":"Alarms Deletion at server termination"},"content":{"rendered":"

Whenever Autoscaling server terminates it leaves its alarms which later goes into insufficient state. This blog will guide you how to delete all those alarms of autoscaling server when it terminates. In order to do so, I’ve written a small shell script, I’m assuming that you already have aws cli installed if not you can click here<\/a> to follow amazon documentation to install it<\/p>\n

[js]#!\/bin\/bash \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 \u00a0 ########### she bang
\nINST_ID=`ec2metadata –instance-id` \u00a0 \u00a0 ############## to store instance id of a autoscaling server in a variable INST_ID
\nalarm_name=`aws cloudwatch describe-alarms –query ‘MetricAlarms[*].[Dimensions[0].Value,AlarmName]’ |awk ‘\/’"$INST_ID"’\/ {print $2}’` ### to store alarm names that are attached to the server
\nfor i in `alarm_name`
\ndo
\naws cloudwatch delete-alarms –alarm-names $i \u00a0 \u00a0 \u00a0 \u00a0##### to delete alarms
\ndone
\n[\/js]<\/p>\n

Now move this script to \/etc\/init.d\/ and create a symbolic link to \/etc\/rc0.d\/. The symlink name should begin with a “S” or “K”.
\nFiles that begin with K are run to terminate (kill) a system service. Files that begin with S are run to start a system service.
\nIf you analyze scripts in \/etc\/rcX.d\/ directory, they starts with “S” or “K” followed by a number. These numbers decide their priority in which these scripts will run, for example, S23 runs before S34.<\/p>\n

I’ve created a script in \/etc\/init.d\/delete_alarms<\/p>\n

and then made its symbolic link in \/etc\/rc0.d\/<\/p>\n

ln -s \/etc\/init.d\/delete_alarms \/etc\/rc0.d\/K00delete_alarms<\/p>\n

Please pick you priority number carefully as wrong priority number might crash your system and it wont boot again. My script name has started with K00 as autoscaling server has only one life, so I don’t have to be worried about starting that again<\/p>\n","protected":false},"excerpt":{"rendered":"

Whenever Autoscaling server terminates it leaves its alarms which later goes into insufficient state. This blog will guide you how to delete all those alarms of autoscaling server when it terminates. In order to do so, I’ve written a small shell script, I’m assuming that you already have aws cli installed if not you can […]<\/p>\n","protected":false},"author":124,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":5,"footnotes":""},"categories":[1174],"tags":[],"class_list":["post-15361","post","type-post","status-publish","format-standard","hentry","category-aws-2"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t