{"id":13335,"date":"2016-02-18T15:20:42","date_gmt":"2016-02-18T11:20:42","guid":{"rendered":"http:\/\/www.msp360.com\/blog\/?p=13335"},"modified":"2022-03-30T17:28:43","modified_gmt":"2022-03-30T13:28:43","slug":"how-to-configure-billing-alerts-for-your-aws-account","status":"publish","type":"post","link":"https:\/\/www.msp360.com\/resources\/blog\/how-to-configure-billing-alerts-for-your-aws-account\/","title":{"rendered":"How to Configure Billing Alerts for Your AWS Account"},"content":{"rendered":"

Amazon Web Services charge users monthly on a Pay-As-You-Go basis. Sometimes your bills can unexpectedly go high. \u00a0For example, if you\u00a0have a running, but not used \u00a0\u201ct2.medium\u201d Amazon EC2 instance, you will pay additional $51.24\/month and excessive provisioned IOPS on EBS volume can lead to an extra $120\/month.<\/p>\n

In this article we explain how to avoid unexpected bills with AWS CloudWatch Billing Alarms and SNS Notifications.<\/p>\n

Configure CloudWatch Billing Alarms and Threshold Notifications for AWS Account<\/strong><\/h2>\n

Step 1: Enable Billing Alerts for Your Account<\/strong><\/h3>\n
\n

1<\/var>Sign in to the AWS Management Console<\/a> and open the Billing and Cost Management \u0421onsole<\/a>.<\/p>\n

2<\/var>On the navigation pane, choose Preferences.<\/b><\/p>\n

3<\/var>Select the Receive Billing Alerts<\/b> check box.\"Receive<\/p>\n

4<\/var>Choose Save Preferences<\/b><\/p>\n<\/div>\n

Now, you have enabled Billing Alerts for your AWS account. Next step is to create e-mail or SMS notifications that will warn you, if the sum overcomes the desired threshold.<\/p>\n

\u00a0<\/a>\"CTA\"<\/a><\/span><\/span><\/div>\n

Step 2. Create SNS Topic and Enable Appropriate CloudWatch Alarm<\/strong><\/h3>\n

This step is also divided into three consecutive actions. First, you need to create an Amazon SNS notification list:<\/p>\n

\n

1<\/var> Open the Amazon SNS console<\/a>.<\/p>\n

2<\/var> On the navigation pane, choose SNS Home.<\/b><\/p>\n

3<\/var>In the Common actions section, choose Create Topic.<\/b>\"Create-SNS-topic-to-configure-billing-alerts-arrow\"<\/p>\n

4<\/var>In the dialog box, for Topic name<\/b>, enter the name for your notification list.<\/p>\n

5<\/var>(Optional) If you want to use this notification list to send SMS messages<\/b>, for Display name, enter the name you want to appear on your SMS messages.<\/p>\n

6<\/var>Choose Create topic.<\/b><\/p>\n

7<\/var>On the navigation pane, choose Topics<\/b> and choose the topic you\u2019ve created.<\/p>\n

8<\/var>Choose Create Subscription<\/b>, choose Email or SMS as protocol and define your address or a phone number.\"sns-topic-create-subscription\"<\/p>\n

9<\/var>Confirm an Email address by following the link in the confirmation letter from AWS.<\/p>\n<\/div>\n

If you don't confirm the email address, the subscription remains in the pending confirmation status until you do so, and does not send a message.<\/p><\/blockquote>\n

\n
\n
FREE WHITEPAPER<\/div>\n
Mastering AWS IAM for Amazon S3<\/div>\n
Learn how to effectively manage the security of your Amazon S3 account to protect your and your clients' data<\/div>\n\"CTA\"<\/a><\/span><\/span>\n<\/div>\n
\"WP<\/div>\n<\/div>\n

Enable the CloudWatch Alarm:<\/strong><\/h4>\n
\n

1<\/var>Open the CloudWatch Console<\/a>.<\/p>\n

2<\/var>If necessary, change the region on the navigation bar to US East (N. Virginia)<\/b>. The billing metric data is stored in this region, even for resources in other regions.<\/p>\n

3<\/var>On the navigation pane, under Metrics, choose Billing.<\/b><\/p>\n

4<\/var>Choose Create Alarm.<\/b>\"create-billing-alarm-amazon-cloudwatch\"<\/p>\n

5<\/var>In a new window choose Show advanced<\/b> to ensure all metrics are set correctly.\"create-billing-alarm-cloudwatch-details\"<\/p>\n

6<\/var>In the list of billing metrics, make sure the metric check box (next to currency) contains EstimatedCharges<\/b> in it.\"metric-estimatedcharges-create-alarm-threshold\"<\/p>\n

7<\/var>Set up the Name<\/b> and (optionally) a description for a new alarm.<\/p>\n<\/div>\n

Define the Alarm as Follows:<\/strong><\/h4>\n
\n

1<\/var>Set the desired sum in \u201cwhen my total AWS charges for the month exceed\u201d check box.<\/p>\n

<\/var>Note:<\/b>We recommend to set up two alarms: when achieving \u00bd of the estimated budget and when exceeding the estimated budget.<\/p>\n

2<\/var>Select an Amazon SNS notification<\/strong> list from the drop down menu or create a new list by entering email addresses in the box.\"send-notification-configuration-connect-to-sns\"<\/p>\n

3<\/var>Choose Create Alarm.<\/b><\/p>\n

To view the status of your alarm, you can go to Alarms<\/b> in the navigation pane.<\/p>\n<\/div>\n

Conclusion<\/h2>\n

Now you have enabled billing notifications for your AWS account. Each time the bill would exceed the defined budget, you will receive a notification to your email or mobile phone. This way you can always be aware of services you pay for and quickly disable them, when the bill exceeds the desired threshold.<\/p>\n","protected":false},"excerpt":{"rendered":"

Amazon Web Services charge users monthly on a Pay-As-You-Go basis. Sometimes your bills can unexpectedly go high. \u00a0For example, if you\u00a0have a running, but not used \u00a0\u201ct2.medium\u201d Amazon EC2 instance, you will pay additional $51.24\/month and excessive provisioned IOPS on EBS volume can lead to an extra $120\/month. In this article we explain how to […]<\/p>\n","protected":false},"author":2,"featured_media":28864,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[877,885],"tags":[],"class_list":["post-13335","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog-articles","category-other"],"acf":[],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/posts\/13335","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/comments?post=13335"}],"version-history":[{"count":2,"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/posts\/13335\/revisions"}],"predecessor-version":[{"id":53406,"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/posts\/13335\/revisions\/53406"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/media\/28864"}],"wp:attachment":[{"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/media?parent=13335"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/categories?post=13335"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.msp360.com\/resources\/wp-json\/wp\/v2\/tags?post=13335"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}