Module types

Data structures used by operation inputs/outputs.

Modules

• builders
  Builders
• error
  Error types that AWS Data Exchange can respond with.

Structs

• Action

  What occurs after a certain event.

• ApiGatewayApiAsset

  The API Gateway API that is the asset.

• AssetDestinationEntry

  The destination for the asset.

• AssetDetails

  Details about the asset.

• AssetEntry

  An asset in AWS Data Exchange is a piece of data (Amazon S3 object) or a means of fulfilling data (Amazon Redshift datashare or Amazon API Gateway API, AWS Lake Formation data permission, or Amazon S3 data access). The asset can be a structured data file, an image file, or some other data file that can be stored as an Amazon S3 object, an Amazon API Gateway API, or an Amazon Redshift datashare, an AWS Lake Formation data permission, or an Amazon S3 data access. When you create an import job for your files, API Gateway APIs, Amazon Redshift datashares, AWS Lake Formation data permission, or Amazon S3 data access, you create an asset in AWS Data Exchange.

• AssetSourceEntry

  The source of the assets.

• AutoExportRevisionDestinationEntry

  A revision destination is the Amazon S3 bucket folder destination to where the export will be sent.

• AutoExportRevisionToS3RequestDetails

  Details of the operation to be performed by the job.

• CreateS3DataAccessFromS3BucketRequestDetails

  Details of the operation to create an Amazon S3 data access from an S3 bucket.

• CreateS3DataAccessFromS3BucketResponseDetails

  Details about the response of the operation to create an S3 data access from an S3 bucket.

• DataGrantSummaryEntry

  Information about a data grant.

• DataSetEntry

  A data set is an AWS resource with one or more revisions.

• DataUpdateRequestDetails

  Extra details specific to a data update type notification.

• DatabaseLfTagPolicy

  The LF-tag policy for database resources.

• DatabaseLfTagPolicyAndPermissions

  The LF-tag policy and permissions for database resources.

• DeprecationRequestDetails

  Extra details specific to a deprecation type notification.

• Details

  Information about the job error.

• Event

  What occurs to start an action.

• EventActionEntry

  An event action is an object that defines the relationship between a specific event and an automated action that will be taken on behalf of the customer.

• ExportAssetToSignedUrlRequestDetails

  Details of the operation to be performed by the job.

• ExportAssetToSignedUrlResponseDetails

  The details of the export to signed URL response.

• ExportAssetsToS3RequestDetails

  Details of the operation to be performed by the job.

• ExportAssetsToS3ResponseDetails

  Details about the export to Amazon S3 response.

• ExportRevisionsToS3RequestDetails

  Details of the operation to be performed by the job.

• ExportRevisionsToS3ResponseDetails

  Details about the export revisions to Amazon S3 response.

• ExportServerSideEncryption

  Encryption configuration of the export job. Includes the encryption type in addition to the AWS KMS key. The KMS key is only necessary if you chose the KMS encryption type.

• ImportAssetFromApiGatewayApiRequestDetails

  The request details.

• ImportAssetFromApiGatewayApiResponseDetails

  The response details.

• ImportAssetFromSignedUrlJobErrorDetails

  Details about the job error.

• ImportAssetFromSignedUrlRequestDetails

  Details of the operation to be performed by the job.

• ImportAssetFromSignedUrlResponseDetails

  The details in the response for an import request, including the signed URL and other information.

• ImportAssetsFromLakeFormationTagPolicyRequestDetails

  Details about the assets imported from an AWS Lake Formation tag policy request.

• ImportAssetsFromLakeFormationTagPolicyResponseDetails

  Details from an import AWS Lake Formation tag policy job response.

• ImportAssetsFromRedshiftDataSharesRequestDetails

  Details from an import from Amazon Redshift datashare request.

• ImportAssetsFromRedshiftDataSharesResponseDetails

  Details from an import from Amazon Redshift datashare response.

• ImportAssetsFromS3RequestDetails

  Details of the operation to be performed by the job.

• ImportAssetsFromS3ResponseDetails

  Details from an import from Amazon S3 response.

• JobEntry

  AWS Data Exchange Jobs are asynchronous import or export operations used to create or copy assets. A data set owner can both import and export as they see fit. Someone with an entitlement to a data set can only export. Jobs are deleted 90 days after they are created.

• JobError

  An error that occurred with the job request.

• KmsKeyToGrant

  The Amazon Resource Name (ARN) of the AWS KMS key used to encrypt the shared S3 objects.

• LakeFormationDataPermissionAsset

  The AWS Lake Formation data permission asset.

• LakeFormationDataPermissionDetails

  Details about the AWS Lake Formation data permission.

• LakeFormationTagPolicyDetails

  Extra details specific to the affected scope in this LF data set.

• LfResourceDetails

  Details about the AWS Lake Formation resource (Table or Database) included in the AWS Lake Formation data permission.

• LfTag

  A structure that allows an LF-admin to grant permissions on certain conditions.

• LfTagPolicyDetails

  Details about the LF-tag policy.

• NotificationDetails

  Extra details specific to this notification.

• OriginDetails

  Details about the origin of the data set.

• ReceivedDataGrantSummariesEntry

  Information about a received data grant.

• RedshiftDataShareAsset

  The Amazon Redshift datashare asset.

• RedshiftDataShareAssetSourceEntry

  The source of the Amazon Redshift datashare asset.

• RedshiftDataShareDetails

  Extra details specific to the affected scope in this Redshift data set.

• RequestDetails

  The details for the request.

• ResponseDetails

  Details for the response.

• RevisionDestinationEntry

  The destination where the assets in the revision will be exported.

• RevisionEntry

  A revision is a container for one or more assets.

• RevisionPublished

  Information about the published revision.

• S3DataAccessAsset

  The Amazon S3 data access that is the asset.

• S3DataAccessAssetSourceEntry

  Source details for an Amazon S3 data access asset.

• S3DataAccessDetails

  Extra details specific to the affected scope in this S3 Data Access data set.

• S3SnapshotAsset

  The Amazon S3 object that is the asset.

• SchemaChangeDetails

  Object encompassing information about a schema change to a single, particular field, a notification can have up to 100 of these.

• SchemaChangeRequestDetails

  Extra details specific to this schema change type notification.

• ScopeDetails

  Details about the scope of the notifications such as the affected resources.

• TableLfTagPolicy

  The LF-tag policy for a table resource.

• TableLfTagPolicyAndPermissions

  The LF-tag policy and permissions that apply to table resources.

Enums

• AcceptanceStateFilterValue
  When writing a match expression against AcceptanceStateFilterValue, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• AssetType
  When writing a match expression against AssetType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• Code
  When writing a match expression against Code, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• DataGrantAcceptanceState
  When writing a match expression against DataGrantAcceptanceState, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• DatabaseLfTagPolicyPermission
  When writing a match expression against DatabaseLfTagPolicyPermission, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ExceptionCause
  When writing a match expression against ExceptionCause, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• GrantDistributionScope
  When writing a match expression against GrantDistributionScope, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• JobErrorLimitName
  When writing a match expression against JobErrorLimitName, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• JobErrorResourceTypes
  When writing a match expression against JobErrorResourceTypes, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• LakeFormationDataPermissionType
  When writing a match expression against LakeFormationDataPermissionType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• LfPermission
  When writing a match expression against LfPermission, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• LfResourceType
  When writing a match expression against LfResourceType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• LimitName
  When writing a match expression against LimitName, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• NotificationType
  When writing a match expression against NotificationType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• Origin
  When writing a match expression against Origin, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ProtocolType
  When writing a match expression against ProtocolType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ResourceType
  When writing a match expression against ResourceType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• SchemaChangeType
  When writing a match expression against SchemaChangeType, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• ServerSideEncryptionTypes
  When writing a match expression against ServerSideEncryptionTypes, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• State
  When writing a match expression against State, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• TableTagPolicyLfPermission
  When writing a match expression against TableTagPolicyLfPermission, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.
• Type
  When writing a match expression against Type, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.