Module aws_sdk_applicationdiscovery::types

Data structures used by operation inputs/outputs.

Modules

• builders
  Builders
• error
  Error types that AWS Application Discovery Service can respond with.

Structs

• AgentConfigurationStatus

  Information about agents that were instructed to start collecting data. Information includes the agent ID, a description of the operation, and whether the agent configuration was updated.

• AgentInfo

  Information about agents associated with the user’s Amazon Web Services account. Information includes agent IDs, IP addresses, media access control (MAC) addresses, agent or collector status, hostname where the agent resides, and agent version for each agent.

• AgentNetworkInfo

  Network details about the host where the agent/collector resides.

• BatchDeleteAgentError

  An object representing the agent or data collector that failed to delete, each containing agentId, errorMessage, and errorCode.

• BatchDeleteConfigurationTask

  A metadata object that represents the deletion task being executed.

• BatchDeleteImportDataError

  Error messages returned for each import task that you deleted as a response for this command.

• ConfigurationTag

  Tags for a configuration item. Tags are metadata that help you categorize IT assets.

• ContinuousExportDescription

  A list of continuous export descriptions.

• CustomerAgentInfo

  Inventory data for installed discovery agents.

• CustomerAgentlessCollectorInfo

  The inventory data for installed Agentless Collector collectors.

• CustomerConnectorInfo

  Inventory data for installed discovery connectors.

• CustomerMeCollectorInfo

  The inventory data for installed Migration Evaluator collectors.

• DeleteAgent

  An object representing the agent or data collector to be deleted along with the optional configurations for error handling.

• DeletionWarning

  A configuration ID paired with a warning message.

• Ec2RecommendationsExportPreferences

  Indicates that the exported data must include EC2 instance type matches for on-premises servers that are discovered through Amazon Web Services Application Discovery Service.

• ExportFilter

  Used to select which agent's data is to be exported. A single agent ID may be selected for export using the StartExportTask action.

• ExportInfo

  Information regarding the export status of discovered data. The value is an array of objects.

• FailedConfiguration

  A configuration ID paired with an error message.

• Filter

  A filter that can use conditional operators.

• ImportTask

  An array of information related to the import task request that includes status information, times, IDs, the Amazon S3 Object URL for the import file, and more.

• ImportTaskFilter

  A name-values pair of elements you can use to filter the results when querying your import tasks. Currently, wildcards are not supported for filters.

• NeighborConnectionDetail

  Details about neighboring servers.

• OrderByElement

  A field and direction for ordered output.

• ReservedInstanceOptions

  Used to provide Reserved Instance preferences for the recommendation.

• Tag

  Metadata that help you categorize IT assets.

• TagFilter

  The tag filter. Valid names are: tagKey, tagValue, configurationId.

• UsageMetricBasis

  Specifies the performance metrics to use for the server that is used for recommendations.

Enums

• AgentStatus
  When writing a match expression against AgentStatus, 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.
• BatchDeleteConfigurationTaskStatus
  When writing a match expression against BatchDeleteConfigurationTaskStatus, 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.
• BatchDeleteImportDataErrorCode
  When writing a match expression against BatchDeleteImportDataErrorCode, 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.
• ConfigurationItemType
  When writing a match expression against ConfigurationItemType, 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.
• ContinuousExportStatus
  When writing a match expression against ContinuousExportStatus, 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.
• DataSource
  When writing a match expression against DataSource, 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.
• DeleteAgentErrorCode
  When writing a match expression against DeleteAgentErrorCode, 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.
• DeletionConfigurationItemType
  When writing a match expression against DeletionConfigurationItemType, 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.
• ExportDataFormat
  When writing a match expression against ExportDataFormat, 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.
• ExportPreferences

  Indicates the type of data that is being exported. Only one ExportPreferences can be enabled for a StartExportTask action.

• ExportStatus
  When writing a match expression against ExportStatus, 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.
• ImportStatus
  When writing a match expression against ImportStatus, 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.
• ImportTaskFilterName
  When writing a match expression against ImportTaskFilterName, 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.
• OfferingClass
  When writing a match expression against OfferingClass, 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.
• OrderString
  When writing a match expression against OrderString, 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.
• PurchasingOption
  When writing a match expression against PurchasingOption, 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.
• Tenancy
  When writing a match expression against Tenancy, 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.
• TermLength
  When writing a match expression against TermLength, 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.