web
You’re offline. This is a read only version of the page.
close

Online Help Center

  • Search
  • Support
    • For Home
    • For Business
  • English (US)
    • Bahasa Indonesia (Indonesian)
    • Dansk (Danish)
    • Deutsch (German)
    • English (Australia)
    • English (US)
    • Español (Spanish)
    • Français (French)
    • Français Canadien
      (Canadian French)
    • Italiano (Italian)
    • Nederlands (Dutch)
    • Norsk (Norwegian)
    • Polski (Polish)
    • Português - Brasil
      (Portuguese - Brazil)
    • Português - Portugal
      (Portuguese - Portugal)
    • Svenska (Swedish)
    • ภาษาไทย (Thai)
    • Tiếng Việt (Vietnamese)
    • Türkçe (Turkish)
    • Čeština (Czech)
    • Ελληνικά (Greek)
    • Български (Bulgarian)
    • Русский (Russian)
    • עברית (Hebrew)
    • اللغة العربية (Arabic)
    • 日本語 (Japanese)
    • 简体中文
      (Simplified Chinese)
    • 繁體中文
      (Traditional Chinese)
    • 繁體中文 HK
      (Traditional Chinese)
    • 한국어 (Korean)
This website uses cookies for website functionality and traffic analytics. Our Cookie Notice provides more information and explains how to amend your cookie settings.
Learn More Yes, I agree
Table of Contents
The page you're looking for can't be found or is under maintenance
Try again later or go to the home page
Go to home page
Error: AWS Marketplace billing usage data has not been successfully submitted in over 48 hours
If you are subscribed to Deep Security for AWS Marketplace with AWS Marketplace billing you might experience the following error:
"Unable to activate the Agent because AWS Marketplace billing usage data has not been submitted in 48 hours. Ensure your Deep Security Manager instance is assigned an IAM role with permission 'aws-marketplace:MeterUsage' and can reach the AWS Marketplace Billing end point."
Tip
Tip
Before you attempt to determine the cause of this problem, reboot the Deep Security Manager. After two hours, check to see if the connection has been reestablished.
Several causes can produce this error:
Cause
Description
The IAM role for the Deep Security Manager is configured incorrectly.
See Configure the IAM role for the Deep Security AMI from AWS Marketplace
The Deep Security Manager cannot reach the AWS billing service.
The Deep Security Manager communicates with the AWS billing service over port 443 at a URL corresponding with the AWS region that your Deep Security Manager runs in (for example: https://metering.marketplace.us-east-1.amazonaws.com).
To test if connectivity with the AWS billing service is the cause of the error, check if
  • Communications over port 443 or to the AWS billing service URL are restricted by either Deep Security or a third-party firewall.
  • The server on which the Deep Security Manager is running connects directly to the Internet. The Deep Security Manager can connect to the AWS billing service through a proxy or VPN. Go to Administration > Proxies to configure this setting.
The Deep Security Manager cannot reach the AWS metadata server.
To test if connectivity with the AWS metadata server is causing the error, log in to the Deep Security Manager over SSH and run the following curl command:
curl http://169.254.169.254/latest/meta-data/
Online Help Center

Support
For Home For Business


Privacy Notice
© 2025 Trend Micro Incorporated. All rights reserved.
Table of Contents
Close