Docs
You are viewing:
Product Catalog 2.0
Simplify and streamline your usage-based billing process by directly ingesting usage data from Amazon S3 bucket into Chargebee Billing. With this integration, Chargebee automatically fetches and processes usage files from your Amazon S3 bucket without any manual interventions for data uploads or preparation. This ensures that Chargebee Billing always works with the most up-to-date customer usage records, helping you eliminate errors, reduce delays, and improve invoice accuracy.
This integration is ideal for businesses that generate high volumes of usage data such as IoT, SaaS, or API-driven services, and store that data in S3. By automating the data pipeline between S3 and Chargebee, your team can focus on building seamless, scalable billing workflows that support real-time usage-based billing and customer transparency.
Before you set up usage ingestion from your Amazon S3 bucket into Chargebee Billing, ensure the following prerequisites are in place:
Usabe-based Billing: You must have an active Chargebee Billing site with usage-based billing feature enabled and configured.
Amazon S3 Bucket access: Ensure you have an Amazon S3 bucket where usage data files are stored. You should have access to the bucket’s name, region, and permission to read objects.
Consistent File Naming Convention: Ensure that "/" is not used in any file_name as AWS might consider it as folders.
You can connect your Amazon S3 bucket with Chargebee Billing in four simple steps to automatically ingest usage data into your site:
This setup ensures that any new usage file uploaded to your bucket is detected and processed by Chargebee in real time. To get started with the integration, follow these steps:
Your bucket details are needed for Chargebee to whitelist your bucket and account_id in SNS topic for receiving events. On the Connect with Amazon S3 bucket page, specify the following bucket details from your AWS account:
This is the AWS region where your S3 bucket is hosted. It is required to configure the SNS topic for event notifications. Follow these steps to get it from your S3 console:
This is the name of the S3 bucket from which usage data will be fetched. You can find it in the same Buckets list in your S3 console.
This is your 12-digit AWS account ID used to identify and whitelist your account. Follow these steps to get it from your S3 console:
The ARN uniquely identifies your S3 bucket and is used to configure access policies. Follow these steps to find or construct it on your S3 console:
arn:aws:s3:::your-bucket-name
format, replacing your-bucket-name
with the actual bucket name.Once all details are entered, click Next.
This step ensures Chargebee receives a notification whenever a new usage file is uploaded.
chargebee-usage-ingest
).Once you're done, return to your Chargebee Billing site, and click Next.
To allow Chargebee to fetch data from your S3 bucket, you need to add a bucket policy. Follow these steps to add a bucket policy:
Once done, return to your Chargebee Billing site, and click Next.
To verify the integration and confirm that your connection is up and running, follow these steps:
Chargebee does the following:
You’ll be notified once each step is completed.
You can click View setup status to confirm that the connection is up to date.
Once your Amazon S3 bucket is connected, you can monitor its connection status anytime using the Health Dashboard in Chargebee Billing. This dashboard provides real-time visibility into the health of your S3 integration and helps ensure uninterrupted usage data ingestion. From the Health Dashboard, you can:
Check if your S3 connection is active and up to date.
View or update key configuration details such as bucket name, region, and policy.
Receive alerts when the connection fails, along with actionable error messages.
For example, if Chargebee is unable to access your S3 bucket due to a misconfigured bucket policy, an alert will appear on the dashboard with the reason for failure. You can review the suggested fix, update the bucket policy in your AWS console (using the policy snippet provided in Chargebee), and restore the connection.
You can disconnect your Amazon S3 bucket from Chargebee Billing site at anytime as required. Once disconnected, Chargebee Billing stops listening for event notifications from the disconnected S3 bucket and will no longer have access to your S3 bucket. To disconnect your S3 bucket, follow these steps:
[Well]
Was this article helpful?