Get-CECostAndUsageWithResource : Hourly timePeriod is not supported for this request

[50ur48h]

Describe the bug

Running this PowerShell query and getting error for hourly granularity even though I am using Daily/Monthly granularity. Can anyone suggest whats the issue?

I am using the latest version of AWS.Tools.CostExplorer [Version: 4.1.398]

$TimePeriod = (New-Object Amazon.CostExplorer.Model.DateInterval -Property @{Start='2023-08-22'; End='2023-07-10'})
$BlendedCost = Get-CeCostAndUsage -TimePeriod $TimePeriod -Granularity DAILY -Metric 'BlendedCost'

[Error] Get-CECostAndUsageWithResource : Hourly timePeriod is not supported for this request

Expected Behavior

I am expecting it to return the cost detail for daily or monthly granularity.

Current Behavior

In all the cases Hourly/Daily/Monthly I am getting the same error as mentioned in the title.

Reproduction Steps

run the code mentioned in the bug description.

Possible Solution

No response

Additional Information/Context

No response

AWS .NET SDK and/or Package version used

AWS.Tools.CostExplorer [Version: 4.1.398]

Targeted .NET Platform

PowerShell 5.1

Operating System and version

Windows

[ashishdhingra]

Ideally this issue should have been opened in https://github.com/aws/aws-tools-for-powershell repository. But looks like CostExplorer CmdLets are auto-generated and these make underlying .NET service API call. So the issue could be narrowed down to making a service API call via .NET SDK. Most likely this is a service API issue where service doesn't support Hourly timePeriod for certain request type. Needs reproduction and investigation.

[ashishdhingra]

Tried to reproduce the issue using the below code:

using Amazon.CostExplorer;
using Amazon.CostExplorer.Model;

Amazon.AWSConfigs.LoggingConfig.LogResponses = Amazon.ResponseLoggingOption.Always;
Amazon.AWSConfigs.LoggingConfig.LogTo = Amazon.LoggingOptions.SystemDiagnostics;
Amazon.AWSConfigs.AddTraceListener("Amazon", new System.Diagnostics.ConsoleTraceListener());

var client = new AmazonCostExplorerClient();
var request = new GetCostAndUsageWithResourcesRequest()
{
    Granularity = Granularity.DAILY,
    Metrics = new List<string>() { "BlendedCost" },
    TimePeriod = new DateInterval() { Start = "2023-08-22", End = "2023-07-10" }
};

var response = await client.GetCostAndUsageWithResourcesAsync(request);
Console.WriteLine(response.HttpStatusCode);

Got the error:

...
...
Amazon Information: 1 : Process started
Amazon Information: 0 : Process ends with exitcode - 0
Amazon Error: 0 : An exception of type HttpErrorResponseException was handled in ErrorHandler., Amazon.Runtime.Internal.HttpErrorResponseException: Exception of type 'Amazon.Runtime.Internal.HttpErrorResponseException' was thrown.
   at Amazon.Runtime.HttpWebRequestMessage.GetResponseAsync(CancellationToken cancellationToken) in D:\source\CodeCommit\Repos\AWSDotNetPublic\sdk\src\Core\Amazon.Runtime\Pipeline\HttpHandler\_netstandard\HttpRequestMessageFactory.cs:line 530
   at Amazon.Runtime.Internal.HttpHandler`1.InvokeAsync[T](IExecutionContext executionContext) in D:\source\CodeCommit\Repos\AWSDotNetPublic\sdk\src\Core\Amazon.Runtime\Pipeline\HttpHandler\HttpHandler.cs:line 185
   at Amazon.Runtime.Internal.Unmarshaller.InvokeAsync[T](IExecutionContext executionContext) in D:\source\CodeCommit\Repos\AWSDotNetPublic\sdk\src\Core\Amazon.Runtime\Pipeline\Handlers\Unmarshaller.cs:line 85
   at Amazon.Runtime.Internal.ErrorHandler.InvokeAsync[T](IExecutionContext executionContext) in D:\source\CodeCommit\Repos\AWSDotNetPublic\sdk\src\Core\Amazon.Runtime\Pipeline\ErrorHandler\ErrorHandler.cs:line 99
Amazon Error: 1 : Received error response: [{"__type":"ValidationException","message":"Hourly timePeriod is not supported for this request"}], Amazon.CostExplorer.AmazonCostExplorerException: Hourly timePeriod is not supported for this request
 ---> Amazon.Runtime.Internal.HttpErrorResponseException: Exception of type 
...
...

During debugging, it was indeed confirmed that the Granularity was set as DAILY in marshalled request:

{"Granularity":"DAILY","Metrics":["BlendedCost"],"TimePeriod":{"End":"2023-07-10","Start":"2023-08-22"}}

The error is returned by the service.

Upon closer look, noticed that the user appears to use incorrect Start (2023-08-22) and End (2023-07-10). Also per GetCostAndUsageWithResources > TimePeriod, The range must be within the last 14 days (the start date cannot be earlier than 14 days ago). The start date is inclusive, but the end date is exclusive.

After flipping Start and End values, now we get error start date is too old for hourly, the max supported days for hourly granularity is 14 days. The error is expected per validation rules for TimePeriod, but it reports incorrect granularity. Changing End value for TimePeriod as 2023-07-23 still reports the same error. Looks like service API is not considering the value set for Granularity.

@50ur48h Looks like your Start and End values are incorrect and you might want to flip them over. Looks like we have an issue with service API where it is not considering DAILY granularity and always defaults to HOURLY. Even with hourly with the correct range, it is giving the said error. I will open an issue with service team to get their update.

Thanks,
Ashish

[ashishdhingra]

Transferred the issue to shared repo https://github.com/aws/aws-sdk for better management since other SDK(s) might also be impacted.

[ashishdhingra]

P97668847

[ashishdhingra]

@50ur48h Good afternoon. Just checked with service team. Looks like you are using the API incorrectly. The GetCostAndUsageWithResources mentions that TimePeriod range must be within the last 14 days (the start date cannot be earlier than 14 days ago). Take explicit note of the fact that the start date cannot be earlier than 14 days ago. Also, based on testing you would also need to have RESOURCE_ID as one of the DIMENSION in either GroupBy or Filter clause. So the below .NET SDK code appears to work:

using Amazon.CostExplorer;
using Amazon.CostExplorer.Model;

Amazon.AWSConfigs.LoggingConfig.LogResponses = Amazon.ResponseLoggingOption.Always;
Amazon.AWSConfigs.LoggingConfig.LogTo = Amazon.LoggingOptions.SystemDiagnostics;
Amazon.AWSConfigs.AddTraceListener("Amazon", new System.Diagnostics.ConsoleTraceListener());

var client = new AmazonCostExplorerClient();
var request = new GetCostAndUsageWithResourcesRequest()
{
    Granularity = Granularity.DAILY,
    Metrics = new List<string>() { "BlendedCost" },
    TimePeriod = new DateInterval() { Start = "2023-08-08", End = "2023-08-22" },
    GroupBy = new List<GroupDefinition>() { new GroupDefinition() { Type = "DIMENSION", Key = "RESOURCE_ID" } }
};

var response = await client.GetCostAndUsageWithResourcesAsync(request);
Console.WriteLine(response.HttpStatusCode);

Although I now get error Resource-level data granularity is an opt-in only feature. You can be enable this feature from the PAYER account's Cost Explorer Settings page.. This is an opt-in feature, the same has been specified as a note on GetCostAndUsageWithResources page.
Please adjust your code for using Get-CECostAndUsageWithResource accordingly based on above guidance from service team and documentation.
In case, the TimePeriod range of 14 days doesn't work for you, then kindly use GetCostAndUsage operation. This could be achieved via Get-CECostAndUsage CmdLet.

Thanks,
Ashish

[github-actions[bot]]

Hello! A team member has marked the above comment as the likely answer to this discussion thread.

• If you agree, please upvote that comment, or click on Mark as answer. I will automatically mark the comment as the answer next time I check.

• If this answer does not help you, please downvote the answer instead and let us know why it was not helpful. I will add a label to this discussion to gain attention from the team.

[github-actions[bot]]

Hello! Reopening this discussion to make it searchable.