Page History

...

A seven-character KFS account number.
OR
A seven-character KFS account number, followed by a hyphen, followed by a sub-account number.
OR
A fully qualified KFS accounting string as outlined here: https://www.dfafinance.cornell.edu/accounting/chartofaccounts/transactionstring
- Under this scheme, the parts of the accounting string labeled as optional in the link above can be left off, but a total of six hyphens are required.

Warning

Be careful to use the correct capitalization and spacing for the "Cost Center" tag name. There is one space between "Cost" and "Center".
Be sure to use a correctly formatted KFS account number as described above. In particular "123-4567" is NOT a correctly formatted KFS account number, but "1234567" IS correctly formatted.

"Cost Center" tags with incorrect spacing or capitalization, or with invalid KFS account formats will be ignored by the automated billing system.

Optional Tags

Tags with these names are propagated to billing data. Tags with any other names are NOT propagated to billing data.

...

Note that not all AWS resource types can be tagged. Here are some examples of resource types that may appear in billing data but do not currently support tagging:

CloudTrail
Config
CloudWatch (alarms, log streams, etc)
SES
SNS
SQS
Directory Service
Lightsail

Note: The above list may not be exhaustive!

If a specific AWS resource type cannot be tagged but still incurs charges, there is no way to target those charges to a KFS account other than the default KFS account configured for the AWS account.

See AWS documentation "Tagging AWS resources".