Discovery Service AWS Application - Docs.aws.amazon

AWS ApplicationDiscovery ServiceUser Guide

AWS Application Discovery Service User GuideAWS Application Discovery Service: User GuideCopyright Amazon Web Services, Inc. and/or its affiliates. All rights reserved.Amazon's trademarks and trade dress may not be used in connection with any product or service that is notAmazon's, in any manner that is likely to cause confusion among customers, or in any manner that disparages ordiscredits Amazon. All other trademarks not owned by Amazon are the property of their respective owners, who mayor may not be affiliated with, connected to, or sponsored by Amazon.

AWS Application Discovery Service User GuideTable of ContentsWhat Is AWS Application Discovery Service? . 1More About VMware Discovery . 1Compare Connectors and Agents . 2Assumptions . 2Setting Up . 4Step 1: Sign Up for AWS . 4Step 2: Create IAM Users . 4Creating an IAM Administrative User . 5Creating an IAM Non-Administrative User . 5Discovery Agent . 6Data Collected by the Discovery Agent . 6Installation Prerequisites . 8Agent Installation on Linux . 9Requirements on Older Linux Platforms . 11Manage the Discovery Agent Process on Linux . 12Uninstall an agent . 13Agent Troubleshooting on Linux . 13Agent Installation on Windows . 14Package Signing on Windows 2003 . 16Manage the Discovery Agent Process on Windows . 16Troubleshooting on Windows . 16Agent Data Collection . 17Discovery Connector . 19Data Collected by Discovery Connector . 19Download the Discovery Connector . 22Deploy the Discovery Connector . 22Configure the Discovery Connector . 23Configure a static IP address for the connector . 24Control Data Collection . 25Disabling auto-upgrades on AWS Discovery Connector . 26Connector Data Collection . 26Troubleshooting the Discovery Connector . 27Fixing Discovery Connector cannot reach AWS during setup . 27Fixing unhealthy connectors . 28Standalone ESX host support . 29Getting additional support for connector issues . 29Import . 30Supported Import File Fields . 30Setting Up Your Import Permissions . 33Uploading Your Import File to Amazon S3 . 35Importing Data . 36Tracking Your Migration Hub Import Requests . 37View, Export & Explore Data . 39View Collected Data . 39Matching Logic . 39Export Collected Data . 40Data Exploration in Athena . 42Enabling Data Exploration in Amazon Athena . 42Working with Data Exploration in Amazon Athena . 43Console Walkthroughs . 50Main Dashboard . 50Main Dashboard . 50Navigating from the Dashboard and the Navigation Pane . 51Data Collection Tools . 52iii

AWS Application Discovery Service User GuideStarting and Stopping Data Collectors . 52Viewing and Sorting Data Collectors . 53View, Export & Explore Data . 53Viewing and Sorting Servers . 54Tagging Servers . 54Exporting Server Data . 55Data Exploration in Athena . 56Applications . 56Querying Discovered Configuration Items . 57Using the DescribeConfigurationsAction . 57Using the ListConfigurationsAction . 59Security . 69Identity and Access Management . 69Audience . 70Authenticating With Identities . 70Managing Access Using Policies . 72How AWS Application Discovery Service Works with IAM . 73IAM Managed Policies . 75Identity-Based Policy Examples . 77Understanding and Using Service-Linked Roles . 82IAM Troubleshooting . 87Logging and monitoring in AWS Application Discovery Service . 88Logging Application Discovery Service API Calls with AWS CloudTrail . 88Quotas . 91Troubleshooting . 92Stop data collection by Data Exploration . 92Remove data collected by Data Exploration . 93Fix Common issues with Data Exploration in Amazon Athena . 93Data Exploration in Amazon Athena Fails to Initiate Because Service-Linked Roles and RequiredAWS Resources Can't be Created . 94New Agent Data Doesn't show Up in Amazon Athena . 94You have Insufficient Permissions to Access Amazon S3, Amazon Kinesis Data Firehose, or AWSGlue . 95Troubleshooting Failed Import Records . 95Document History . 98AWS glossary . 100iv

AWS Application Discovery Service User GuideMore About VMware DiscoveryWhat Is AWS Application DiscoveryService?AWS Application Discovery Service helps you plan your migration to the AWS cloud by collecting usageand configuration data about your on-premises servers. Application Discovery Service is integrated withAWS Migration Hub, which simplifies your migration tracking as it aggregates your migration statusinformation into a single console. You can view the discovered servers, group them into applications, andthen track the migration status of each application from the Migration Hub console in your home region.All discovered data is stored in your AWS Migration Hub home region. Therefore, you must set yourhome region in the Migration Hub console or with CLI commands before performing any discovery andmigration activities. Your data can be exported for analysis in Microsoft Excel or AWS analysis tools suchas Amazon Athena and Amazon QuickSight.Using Application Discovery Service APIs, you can export the system performance and utilization datafor your discovered servers. Input this data into your cost model to compute the cost of running thoseservers in AWS. Additionally, you can export data about the network connections that exist betweenservers. This information helps you determine the network dependencies between servers and groupthem into applications for migration planning.NoteYour home region must be set in AWS Migration Hub before you begin the process of discovery,because your data will be stored in your home region. For more information about working witha home region, see Home regions.Application Discovery Service offers two ways of performing discovery and collecting data about youron-premises servers: Agentless discovery can be performed by deploying the AWS Agentless Discovery Connector (OVAfile) through your VMware vCenter. After the Discovery Connector is configured, it identifies virtualmachines (VMs) and hosts associated with vCenter. The Discovery Connector collects the followingstatic configuration data: Server hostnames, IP addresses, MAC addresses, disk resource allocations.Additionally, it collects the utilization data for each VM and computes average and peak utilization formetrics such as CPU, RAM, and Disk I/O. Agent-based discovery can be performed by deploying the AWS Application Discovery Agent on eachof your VMs and physical servers. The agent installer is available for Windows and Linux operatingsystems. It collects static configuration data, detailed time-series system-performance information,inbound and outbound network connections, and processes that are running.Application Discovery Service integrates with application discovery solutions from AWS Partner Network(APN) partners. These third-party solutions can help you import details about your on-premisesenvironment directly into Migration Hub, without using any discovery connector or discovery agent.Third-party application discovery tools can query AWS Application Discovery Service, and they can writeto the Application Discovery Service database using the public API. In this way, you can import data intoMigration Hub and view it, so that you can associate applications with servers and track migrations.More About VMware DiscoveryIf you have virtual machines (VMs) that are running in the VMware vCenter environment, you can usethe Discovery Connector to collect system information without having to install an agent on each VM.1

AWS Application Discovery Service User GuideCompare Connectors and AgentsInstead, you load this on-premises appliance into vCenter and allow it to discover all of its hosts andVMs.The Discovery Connector captures system performance information and resource utilization for eachVM running in the vCenter, regardless of what operating system is in use. However, it cannot “lookinside” each of the VMs, and as such, cannot figure out what processes are running on each VM nor whatnetwork connections exist. Therefore, if you need this level of detail and want to take a closer look atsome of your existing VMs in order to assist in planning your migration, you can install the DiscoveryAgent on an as-needed basis.Also, for VMs hosted on VMware, you can use both the Discovery Connector and Discovery Agent toperform discovery simultaneously. For details regarding the exact types of data each discovery tool willcollect, see Data Collected by the Discovery Connector (p. 19) and Data Collected by the DiscoveryAgent (p. 6).Compare Connectors and AgentsThe following table provides a quick comparison of two primary Application Discovery Service tools:Discovery ConnectorDiscovery AgentSupported server typesVMware virtual machinePhysical serveryesnoyesyesDeploymentPer serverPer vCenternoyesyesnoCollected dataStatic configuration dataVM utilization metricsyesyesyesnononoyes (Export only)yes (Export only)noyes (Export only)Time series performanceinformationNetwork inbound/outboundconnectionsRunning processesSupported OSAny OS running in VMwarevCenter (V5.5, V6, & V6.5)For the list of supported Linuxand Windows operating systems,see Installation Prerequisites forDiscovery Agent (p. 8).AssumptionsTo use Application Discovery Service, the following is assumed: You have signed up for AWS. For more information, see Setting Up AWS Application DiscoveryService (p. 4). You have selected a Migration Hub home region. For more information, see the documentationregarding home regions.2

AWS Application Discovery Service User GuideAssumptionsHere's what to expect: The Migration Hub home region is the only region where Application Discovery Service stores yourdiscovery and planning data. Discovery agents, connectors, and imports can be used in your selected Migration Hub home regiononly. For a list of AWS Regions where you can use Application Discovery Service, see the Amazon WebServices General Reference.3

AWS Application Discovery Service User GuideStep 1: Sign Up for AWSSetting Up AWS ApplicationDiscovery ServiceBefore you use AWS Application Discovery Service for the first time, complete the following tasks:Step 1: Sign Up for AWS (p. 4)Step 2: Create IAM Users (p. 4)Step 1: Sign Up for AWSIn this section, you sign up for an AWS account. If you already have an AWS account, skip this step.When you sign up for Amazon Web Services (AWS), your AWS account is automatically signed up for allAWS services, including AWS Application Discovery Service. You are charged only for the services thatyou use.To create an AWS account1.Open low the online instructions.Part of the sign-up procedure involves receiving a phone call and entering a verification code on thephone keypad.Note your AWS account number, because you'll need it for the next task.Step 2: Create IAM UsersWhen you create an AWS account, you get a single sign-in identity that has complete access to all ofthe AWS services and resources in the account. This identity is called the AWS account root user. Signingin to the AWS Management Console using the email address and password that you used to create theaccount gives you complete access to all of the AWS resources in your account.We strongly recommend that you not use the root user for everyday tasks, even the administrative ones.Instead, follow the security best practice Create Individual IAM Users and create an AWS Identity andAccess Management (IAM) administrator user. Then securely lock away the root user credentials and usethem to perform only a few account and service management tasks.In addition to creating an administrative user you'll also need to create non-administrative IAM users.The following topics explain how to create both types of IAM users.Topics Creating an IAM Administ

Amazon's trademarks and trade dress may not be used in connection with any product or service that is not Amazon's, in any manner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All other trademarks not owned by Amazon