CreateCostCategoryDefinitionRequest
import type { CreateCostCategoryDefinitionRequest } from "https://aws-api.deno.dev/v0.4/services/costexplorer.ts?docs=full";interface CreateCostCategoryDefinitionRequest {
DefaultValue?: string | null;
EffectiveStart?: string | null;
Name: string;
ResourceTags?: ResourceTag[] | null;
Rules: CostCategoryRule[];
RuleVersion: CostCategoryRuleVersion;
SplitChargeRules?: CostCategorySplitChargeRule[] | null;
}§Properties
§
EffectiveStart?: string | null
[src]The Cost Category's effective start date. It can only be a billing start date (first day of the month). If the date isn't provided, it's the first day of the current month. Dates can't be before the previous twelve months, or in the future.
§
ResourceTags?: ResourceTag[] | null
[src]An optional list of tags to associate with the specified CostCategory.
You can use resource tags to control access to your cost category using IAM policies.
Each tag consists of a key and a value, and each key must be unique for the resource. The following restrictions apply to resource tags:
- Although the maximum number of array members is 200, you can assign a maximum of 50 user-tags to one resource. The remaining are reserved for Amazon Web Services use
- The maximum length of a key is 128 characters
- The maximum length of a value is 256 characters
- Keys and values can only contain alphanumeric characters, spaces, and any of the following:
_.:/=+@- - Keys and values are case sensitive
- Keys and values are trimmed for any leading or trailing whitespaces
- Don’t use
aws:as a prefix for your keys. This prefix is reserved for Amazon Web Services use
§
Rules: CostCategoryRule[]
[src]The Cost Category rules used to categorize costs. For more information, see CostCategoryRule.
§
RuleVersion: CostCategoryRuleVersion
[src]§
SplitChargeRules?: CostCategorySplitChargeRule[] | null
[src]The split charge rules used to allocate your charges between your Cost Category values.