A title that contains the connector type and part of the error message
The error message itself, in the same color as the connector error message.
Issue: A short description of the issue.
Action: A short description of what actions need to be taken to resolve the issue.
No Objects found in bucket
Failed: No Objects found in bucket myneva-us-east-1-master-billing with prefix myneva/myneva-Daily-Cost-And-Usage-Report/202302
Issue: Each run, the connector looks for a report in a specific location, which is the bucket that is specified in the Bucket Name field in the connector settings. There, it looks for a report with the Report Prefix and Report Name as specified in the connector settings. This error is shown when no report with that specific name is found in that specific bucket. This could be caused by several things:
- The bucket is indeed empty. Nu usage and thus no report.
- There is a report, but it is not recognized because the report prefix or name set up in the management console are not identical to those in CloudBilling. This is probably due to a typo.
- The name of the bucket is not identical. Similar to 2. but now regards the bucket name.
Solution: Contact our customer and tell them that no report is found in the bucket. Help them troubleshoot the issue using the 3 checks mentioned above.
Request signature does not match the signature provides
Failed: The request signature we calculated does not match the signature you provided. Check your key and signing method.
Issue: gaat om de 'secret key'.
AWS – the following unknown columns
The following unknown columns were found in the AWS report: bill/InvoicingEntity, lineItem/NetUnblendedRate, lineItem/NetUnblendedCost, product/accountAssistance, product/architecturalReview, product/architectureSupport, product/bestPractices, product/brokerEngine, product/cacheEngine, product/caseSeverityresponseTimes, product/ciType, product/classicnetworkingsupport, product/clientLocation, product/customerServiceAndCommunities, product/dominantnondominant, product/enhancedNetworkingSupport, product/equivalentondemandsku, product/fromRegionCode, product/includedServices, product/io, product/launchSupport, product/logsDestination, product/marketoption, product/memoryGib, product/operationsSupport, product/overhead, product/platoinstancename, product/platopricingtype, product/platoprotocoltype, product/platostoragename, product/platostoragetype, product/platotrafficdirection, product/platousagetype, product/platovolumetype, product/pricingUnit, product/proactiveGuidance, product/programmaticCaseManagement, product/regionCode, product/technicalSupport, product/thirdpartySoftwareSupport, product/tickettype, product/toRegionCode, product/trafficDirection, product/training, product/usageFamily, product/vpcnetworkingsupport, product/whoCanOpenCases, pricing/LeaseContractLength, pricing/OfferingClass, pricing/PurchaseOption, pricing/RateCode, pricing/currency, reservation/NetAmortizedUpfrontCostForUsage, reservation/NetAmortizedUpfrontFeeForBillingPeriod, reservation/NetEffectiveCost, reservation/NetRecurringFeeForUsage, reservation/NetUnusedAmortizedUpfrontFeeForBillingPeriod, reservation/NetUnusedRecurringFee, reservation/NetUpfrontValue, reservation/NumberOfReservations, discount/SppDiscount, discount/TotalDiscount, savingsPlan/NetSavingsPlanEffectiveCost, savingsPlan/NetAmortizedUpfrontCommitmentForBillingPeriod, savingsPlan/NetRecurringCommitmentForBillingPeriod
Roelof Spijker: “De AWS connector werkt obv een bestand. Die is ooit gemaakt op basis van hoe dat bestand er destijds uitzag. In de tussentijd heeft AWS over tijd allerlei dingen toegevoegd aan dat bestand. We rapporteren welke kolommen we zien die we niet verwachten om een beeld te kunnen krijgen of er iets wordt toegevoegd dat wellicht interessant is. En, wanneer er iets wordt toegevoegd waar we iets mee moeten kunnen we daardoor direct een beeld krijgen van welke informatie beschikbaar is in het bestand.”
Key ID problem
How to fix: Go to connector => AWS Settings => Click on appropriate connector name => This will show you the access key (see image below). This key should be the same as the one set up in your management console. Using this setup guide, section 2.6 on page 12 you can check whether the Access Key matches. If not, we recommend the customer to go through this part of the setup guide again, as well as section 3.1.1 (not creating a new account, just the Access Key part).
Unexpected EOF
No root cause identified but the connector is like to run successfully on the next day
Failed: Unable to read data from the transport connection
How to fix: See if connector runs the next day.
A previous report generated more results () than current report () for prefix 202309-047165250495-171223843493, manual intervention required to clean up excess
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article