If you’re using AWS End User Messaging (SMS or Pinpoint) and notice a strange discrepancy in your billing dashboard, here’s what you need to know and how to handle it.
First, let’s understand the problem. You might see that your dashboard shows a “$0” spend under the “Spending limits” section, even though you know your team is actively sending SMS messages and incurring costs. For example, your configured spending limit might be set at $50, but the dashboard doesn’t reflect any spend at all.
This mismatch raises a big concern: is the dashboard just not updating in real-time, or is there a bigger issue? If the “Current spend” isn’t showing your actual usage, AWS might not be accurately enforcing your spending limits. This could mean your account is at risk of overspending because the system isn’t fully aligned with backend data.
If you’re seeing this across multiple accounts, it’s likely a widespread problem rather than a one-off bug.
Here’s what you can do:
-
Verify Actual Usage: Check your CloudWatch metrics and billing reports directly in the AWS Billing Dashboard to confirm how much you’ve actually spent on SMS. This helps determine if the issue is truly display-related or if there’s a deeper problem.
-
Review the Enforced Limit: Make sure your spending limit is set correctly in the console. If it’s at $50, but the dashboard shows $0, that’s a sign of a UI bug rather than an actual limit issue.
-
Contact AWS Support: Since a support case has already been opened without a clear answer, follow up with AWS support and insist on an investigation into the dashboard’s data synchronization. Provide details about where you see mismatches.
-
Stay Informed: Keep an eye on announcements from AWS. Sometimes, these display issues are known bugs scheduled for fix in upcoming updates.
Remember, even if the dashboard shows $0 spend, always check your actual billing and usage reports to prevent unexpected charges. Until the display sync is fixed, rely on direct billing data to monitor your costs and ensure your spending limits are working as intended.
In summary, discrepancies between the AWS messaging console and actual billing data can happen, but verified billing will always be the ultimate guide. Stay proactive, keep records, and work with AWS support to resolve the issue quickly.