New default start month for AWS bill connects created through the API

Summary

Beginning August 4, 2026, we're rolling out a change to how new AWS bill connects handle the optional 'effectiveFrom' field.

If you create an AWS bill connect through the API and leave 'effectiveFrom' blank, 'effectiveFrom' will now be defaulted to the current month (UTC). Previously, leaving it blank imported all available historical billing data.

Existing bill connects are not affected.

If your integration depends on historical data, set 'effectiveFrom' when creating the connection.

Does this affect me?

You're affected if all of the following apply:

• You create new AWS bill connects through the FinOps Onboarding API using the IAM Role or IAM User endpoints
• Your requests don't include the 'effectiveFrom' field
• You expect those new connections to import historical billing data

You're not affected if:

• Your bill connects already exist. Connections created before this change keep their current behavior. Those without an 'effectiveFrom' value will continue to import all available billing months. Nothing changes retroactively.
• You already set 'effectiveFrom' in your requests. Explicit values work exactly as before.
• You use a cloud provider other than AWS. This change applies to AWS bill connects only.
• Updating an existing bill connect is also unchanged. This only affects what happens at creation.

What to do

1. Review any scripts or automation that create AWS bill connects.
2. If you need historical data, add 'effectiveFrom' to your create request with the earliest month you want, in YYYY-MM format. For example: "effectiveFrom": "2024-01". Any month from 2014-01 up to the current month is accepted.
3. Already created a connection and missing history? You can update its 'effectiveFrom' to an earlier month at any time to import the additional months.

If you create bill connects in the Flexera One UI

You'll now see an Effective From field when setting up an AWS bill connect, pre-filled with the current month.

Adjust it before saving if you want historical data. No more guessing where ingestion will start.

Why we're making this change

An unset start month made it unclear when data ingestion would begin, and often triggered years of unintended historical import.

Defaulting to the current month makes every new connection's start point explicit and predictable, and you stay in control by setting the value yourself.