{-# OPTIONS_GHC -fno-warn-duplicate-exports #-}
{-# OPTIONS_GHC -fno-warn-unused-imports #-}

-- |
-- Module      : Amazonka.CostAndUsageReport
-- Copyright   : (c) 2013-2021 Brendan Hay
-- License     : Mozilla Public License, v. 2.0.
-- Maintainer  : Brendan Hay <brendan.g.hay+amazonka@gmail.com>
-- Stability   : auto-generated
-- Portability : non-portable (GHC extensions)
--
-- Derived from API version @2017-01-06@ of the AWS service descriptions, licensed under Apache 2.0.
--
-- The AWS Cost and Usage Report API enables you to programmatically
-- create, query, and delete AWS Cost and Usage report definitions.
--
-- AWS Cost and Usage reports track the monthly AWS costs and usage
-- associated with your AWS account. The report contains line items for
-- each unique combination of AWS product, usage type, and operation that
-- your AWS account uses. You can configure the AWS Cost and Usage report
-- to show only the data that you want, using the AWS Cost and Usage API.
--
-- Service Endpoint
--
-- The AWS Cost and Usage Report API provides the following endpoint:
--
-- -   cur.us-east-1.amazonaws.com
module Amazonka.CostAndUsageReport
  ( -- * Service Configuration
    defaultService,

    -- * Errors
    -- $errors

    -- ** ValidationException
    _ValidationException,

    -- ** InternalErrorException
    _InternalErrorException,

    -- ** DuplicateReportNameException
    _DuplicateReportNameException,

    -- ** ReportLimitReachedException
    _ReportLimitReachedException,

    -- * Waiters
    -- $waiters

    -- * Operations
    -- $operations

    -- ** PutReportDefinition
    PutReportDefinition (PutReportDefinition'),
    newPutReportDefinition,
    PutReportDefinitionResponse (PutReportDefinitionResponse'),
    newPutReportDefinitionResponse,

    -- ** DeleteReportDefinition
    DeleteReportDefinition (DeleteReportDefinition'),
    newDeleteReportDefinition,
    DeleteReportDefinitionResponse (DeleteReportDefinitionResponse'),
    newDeleteReportDefinitionResponse,

    -- ** ModifyReportDefinition
    ModifyReportDefinition (ModifyReportDefinition'),
    newModifyReportDefinition,
    ModifyReportDefinitionResponse (ModifyReportDefinitionResponse'),
    newModifyReportDefinitionResponse,

    -- ** DescribeReportDefinitions (Paginated)
    DescribeReportDefinitions (DescribeReportDefinitions'),
    newDescribeReportDefinitions,
    DescribeReportDefinitionsResponse (DescribeReportDefinitionsResponse'),
    newDescribeReportDefinitionsResponse,

    -- * Types

    -- ** AWSRegion
    AWSRegion (..),

    -- ** AdditionalArtifact
    AdditionalArtifact (..),

    -- ** CompressionFormat
    CompressionFormat (..),

    -- ** ReportFormat
    ReportFormat (..),

    -- ** ReportVersioning
    ReportVersioning (..),

    -- ** SchemaElement
    SchemaElement (..),

    -- ** TimeUnit
    TimeUnit (..),

    -- ** ReportDefinition
    ReportDefinition (ReportDefinition'),
    newReportDefinition,
  )
where

import Amazonka.CostAndUsageReport.DeleteReportDefinition
import Amazonka.CostAndUsageReport.DescribeReportDefinitions
import Amazonka.CostAndUsageReport.Lens
import Amazonka.CostAndUsageReport.ModifyReportDefinition
import Amazonka.CostAndUsageReport.PutReportDefinition
import Amazonka.CostAndUsageReport.Types
import Amazonka.CostAndUsageReport.Waiters

-- $errors
-- Error matchers are designed for use with the functions provided by
-- <http://hackage.haskell.org/package/lens/docs/Control-Exception-Lens.html Control.Exception.Lens>.
-- This allows catching (and rethrowing) service specific errors returned
-- by 'CostAndUsageReport'.

-- $operations
-- Some AWS operations return results that are incomplete and require subsequent
-- requests in order to obtain the entire result set. The process of sending
-- subsequent requests to continue where a previous request left off is called
-- pagination. For example, the 'ListObjects' operation of Amazon S3 returns up to
-- 1000 objects at a time, and you must send subsequent requests with the
-- appropriate Marker in order to retrieve the next page of results.
--
-- Operations that have an 'AWSPager' instance can transparently perform subsequent
-- requests, correctly setting Markers and other request facets to iterate through
-- the entire result set of a truncated API operation. Operations which support
-- this have an additional note in the documentation.
--
-- Many operations have the ability to filter results on the server side. See the
-- individual operation parameters for details.

-- $waiters
-- Waiters poll by repeatedly sending a request until some remote success condition
-- configured by the 'Wait' specification is fulfilled. The 'Wait' specification
-- determines how many attempts should be made, in addition to delay and retry strategies.