- Navigation GuideYou are on a Client landing page. Commands (operations) are listed on this page. The Client constructor type is linked at the bottom.
ApplicationDiscoveryServiceClient
Amazon Web Services Application Discovery Service (Application Discovery Service) helps you plan application migration projects. It automatically identifies servers, virtual machines (VMs), and network dependencies in your on-premises data centers. For more information, see the Amazon Web Services Application Discovery Service FAQ .
Application Discovery Service offers three ways of performing discovery and collecting data about your on-premises servers:
-
Agentless discovery using Amazon Web Services Application Discovery Service Agentless Collector (Agentless Collector), which doesn't require you to install an agent on each host.
-
Agentless Collector gathers server information regardless of the operating systems, which minimizes the time required for initial on-premises infrastructure assessment.
-
Agentless Collector doesn't collect information about network dependencies, only agent-based discovery collects that information.
-
-
Agent-based discovery using the Amazon Web Services Application Discovery Agent (Application Discovery Agent) collects a richer set of data than agentless discovery, which you install on one or more hosts in your data center.
-
The agent captures infrastructure and application information, including an inventory of running processes, system performance information, resource utilization, and network dependencies.
-
The information collected by agents is secured at rest and in transit to the Application Discovery Service database in the Amazon Web Services cloud. For more information, see Amazon Web Services Application Discovery Agent .
-
-
Amazon Web Services Partner Network (APN) solutions integrate with Application Discovery Service, enabling you to import details of your on-premises environment directly into Amazon Web Services Migration Hub (Migration Hub) without using Agentless Collector or Application Discovery Agent.
-
Third-party application discovery tools can query Amazon Web Services Application Discovery Service, and they can write to the Application Discovery Service database using the public API.
-
In this way, you can import data into Migration Hub and view it, so that you can associate applications with servers and track migrations.
-
Working With This Guide
This API reference provides descriptions, syntax, and usage examples for each of the actions and data types for Application Discovery Service. The topic for each action shows the API request parameters and the response. Alternatively, you can use one of the Amazon Web Services SDKs to access an API that is tailored to the programming language or platform that you're using. For more information, see Amazon Web Services SDKs .
-
Remember that you must set your Migration Hub home Region before you call any of these APIs.
-
You must make API calls for write actions (create, notify, associate, disassociate, import, or put) while in your home Region, or a
HomeRegionNotSetException
error is returned. -
API calls for read actions (list, describe, stop, and delete) are permitted outside of your home Region.
-
Although it is unlikely, the Migration Hub home Region could change. If you call APIs outside the home Region, an
InvalidInputException
is returned. -
You must call
GetHomeRegion
to obtain the latest Migration Hub home Region.
This guide is intended for use with the Amazon Web Services Application Discovery Service User Guide .
All data is handled according to the Amazon Web Services Privacy Policy . You can operate Application Discovery Service offline to inspect collected data before it is shared with the service.
Installation
npm install @aws-sdk/client-application-discovery-service
yarn add @aws-sdk/client-application-discovery-service
pnpm add @aws-sdk/client-application-discovery-service
ApplicationDiscoveryServiceClient Operations
Command | Summary |
---|
Command | Summary |
---|---|
AssociateConfigurationItemsToApplicationCommand | Associates one or more configuration items with an application. |
BatchDeleteAgentsCommand | Deletes one or more agents or collectors as specified by ID. Deleting an agent or collector does not delete the previously discovered data. To delete the data collected, use |
BatchDeleteImportDataCommand | Deletes one or more import tasks, each identified by their import ID. Each import task has a number of records that can identify servers or applications. Amazon Web Services Application Discovery Service has built-in matching logic that will identify when discovered servers match existing entries that you've previously discovered, the information for the already-existing discovered server is updated. When you delete an import task that contains records that were used to match, the information in those matched records that comes from the deleted records will also be deleted. |
CreateApplicationCommand | Creates an application with the given name and description. |
CreateTagsCommand | Creates one or more tags for configuration items. Tags are metadata that help you categorize IT assets. This API accepts a list of multiple configuration items. Do not store sensitive information (like personal data) in tags. |
DeleteApplicationsCommand | Deletes a list of applications and their associations with configuration items. |
DeleteTagsCommand | Deletes the association between configuration items and one or more tags. This API accepts a list of multiple configuration items. |
DescribeAgentsCommand | Lists agents or collectors as specified by ID or other filters. All agents/collectors associated with your user can be listed if you call |
DescribeBatchDeleteConfigurationTaskCommand | Takes a unique deletion task identifier as input and returns metadata about a configuration deletion task. |
DescribeConfigurationsCommand | Retrieves attributes for a list of configuration item IDs. All of the supplied IDs must be for the same asset type from one of the following:
Output fields are specific to the asset type specified. For example, the output for a server configuration item includes a list of attributes about the server, such as host name, operating system, number of network cards, etc. For a complete list of outputs for each asset type, see Using the DescribeConfigurations Action in the Amazon Web Services Application Discovery Service User Guide. |
DescribeContinuousExportsCommand | Lists exports as specified by ID. All continuous exports associated with your user can be listed if you call |
DescribeExportConfigurationsCommand | |
DescribeExportTasksCommand | Retrieve status of one or more export tasks. You can retrieve the status of up to 100 export tasks. |
DescribeImportTasksCommand | Returns an array of import tasks for your account, including status information, times, IDs, the Amazon S3 Object URL for the import file, and more. |
DescribeTagsCommand | Retrieves a list of configuration items that have tags as specified by the key-value pairs, name and value, passed to the optional parameter There are three valid tag filter names:
Also, all configuration items associated with your user that have tags can be listed if you call |
DisassociateConfigurationItemsFromApplicationCommand | Disassociates one or more configuration items from an application. |
ExportConfigurationsCommand | Deprecated. Use Exports all discovered configuration data to an Amazon S3 bucket or an application that enables you to view and evaluate the data. Data includes tags and tag associations, processes, connections, servers, and system performance. This API returns an export ID that you can query using the DescribeExportConfigurations API. The system imposes a limit of two configuration exports in six hours. |
GetDiscoverySummaryCommand | Retrieves a short summary of discovered assets. This API operation takes no request parameters and is called as is at the command prompt as shown in the example. |
ListConfigurationsCommand | Retrieves a list of configuration items as specified by the value passed to the required parameter |
ListServerNeighborsCommand | Retrieves a list of servers that are one network hop away from a specified server. |
StartBatchDeleteConfigurationTaskCommand | Takes a list of configurationId as input and starts an asynchronous deletion task to remove the configurationItems. Returns a unique deletion task identifier. |
StartContinuousExportCommand | Start the continuous flow of agent's discovered data into Amazon Athena. |
StartDataCollectionByAgentIdsCommand | Instructs the specified agents to start collecting data. |
StartExportTaskCommand | Begins the export of a discovered data report to an Amazon S3 bucket managed by Amazon Web Services. Exports might provide an estimate of fees and savings based on certain information that you provide. Fee estimates do not include any taxes that might apply. Your actual fees and savings depend on a variety of factors, including your actual usage of Amazon Web Services services, which might vary from the estimates provided in this report. If you do not specify If you specify If you enable |
StartImportTaskCommand | Starts an import task, which allows you to import details of your on-premises environment directly into Amazon Web Services Migration Hub without having to use the Amazon Web Services Application Discovery Service (Application Discovery Service) tools such as the Amazon Web Services Application Discovery Service Agentless Collector or Application Discovery Agent. This gives you the option to perform migration assessment and planning directly from your imported data, including the ability to group your devices as applications and track their migration status. To start an import request, do this:
For more information, including step-by-step procedures, see Migration Hub Import in the Amazon Web Services Application Discovery Service User Guide. There are limits to the number of import tasks you can create (and delete) in an Amazon Web Services account. For more information, see Amazon Web Services Application Discovery Service Limits in the Amazon Web Services Application Discovery Service User Guide. |
StopContinuousExportCommand | Stop the continuous flow of agent's discovered data into Amazon Athena. |
StopDataCollectionByAgentIdsCommand | Instructs the specified agents to stop collecting data. |
UpdateApplicationCommand | Updates metadata about an application. |
ApplicationDiscoveryServiceClient Configuration
Parameter | Type | Description |
---|
Parameter | Type | Description |
---|---|---|
defaultsMode Optional | DefaultsMode | Provider<DefaultsMode> | The @smithy/smithy-client#DefaultsMode that will be used to determine how certain default configuration options are resolved in the SDK. |
disableHostPrefix Optional | boolean | Disable dynamically changing the endpoint of the client based on the hostPrefix trait of an operation. |
extensions Optional | RuntimeExtension[] | Optional extensions |
logger Optional | Logger | Optional logger for logging debug/info/warn/error. |
maxAttempts Optional | number | Provider<number> | Value for how many times a request will be made at most in case of retry. |
profile Optional | string | Setting a client profile is similar to setting a value for the AWS_PROFILE environment variable. Setting a profile on a client in code only affects the single client instance, unlike AWS_PROFILE.When set, and only for environments where an AWS configuration file exists, fields configurable by this file will be retrieved from the specified profile within that file. Conflicting code configuration and environment variables will still have higher priority.For client credential resolution that involves checking the AWS configuration file, the client's profile (this value) will be used unless a different profile is set in the credential provider options. |
region Optional | string | Provider<string> | The AWS region to which this client will send requests |
requestHandler Optional | __HttpHandlerUserInput | The HTTP handler to use or its constructor options. Fetch in browser and Https in Nodejs. |
retryMode Optional | string | Provider<string> | Specifies which retry algorithm to use. |
useDualstackEndpoint Optional | boolean | Provider<boolean> | Enables IPv6/IPv4 dualstack endpoint. |
useFipsEndpoint Optional | boolean | Provider<boolean> | Enables FIPS compatible endpoints. |
Additional config fields are described in the full configuration type: ApplicationDiscoveryServiceClientConfig