User Guide-AWS Migration Portfolio Assessment
AWS Migration Portfolio Assessment- User Guide -
AWS Migration Portfolio Assessment: User GuideAWS Migration Portfolio Assessment: User GuideCopyright 2018 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 not Amazon's, in anymanner that is likely to cause confusion among customers, or in any manner that disparages or discredits Amazon. All othertrademarks not owned by Amazon are the property of their respective owners, who may or may not be affiliated with,connected to, or sponsored by Amazon.v2.9.1 (October 2021)2
AWS Migration Portfolio Assessment: User GuideTable of ContentsGETTING STARTED WITH AWS MIGRATION PORTFOLIO ASSESSMENT . 5ARE YOU A FIRST-TIME USER OF AWS PORTFOLIO ASSESSMENT? .5WHEN TO USE AWS MIGRATION PORTFOLIO ASSESSMENT? .5ASSUMPTIONS .5PORTFOLIO ANALYSIS USER FLOW . .7.6.8.6.9.7.7.1.7.2.7.3.7.4.Gather Customer Portfolio Data .6Create a new portfolio .8Manage the Portfolio Data .9Import Data (from files) .9Import Data from ADS .11Data Validation .12Add Shared Storage and Network Bandwidth Data .14Visualize the Portfolio .15Analyze the Portfolio .16Application Prioritization .17Application Grouping .18Migration Wave Planning .19Total Cost of Ownership (TCO) .20Migration Strategy .25Migration Cost .26Migration Cash Flows .27Validate and Refine the MPA Assumptions .28Compare Assessments .33Portfolio management.34Share a Portfolio.34Edit a Portfolio.34Copy a Portfolio .35Delete a Portfolio .35DEEPER DIVE INTO MPA ASSESSMENTS . 3.2.3.3.3.4.3.5.5.EC2 recommendations (shared and dedicated instance) .36EC2 sizing .36EC2 cost estimation .39On-prem cost estimation .40Troubleshooting .42Dedicated Host recommendations .43Dedicated Host sizing .43Dedicated Host cost estimation .44Dedicated Host – 3rd party license estimation .45VMC recommendations .46VMC sizing .47VMC cost estimation .48Database recommendations .49RDS sizing .49RDS cost estimation .51On-premises database cost estimation .52Licensing .52Troubleshooting .53SQL Server Optimization .54v2.9.1 (October 2021)3
AWS Migration Portfolio Assessment: User Guide6.Application cost.556.1.AWS costs estimation .566.2.On-premises costs estimation .577.Mainframe workloads assessments .597.1.Mainframe workloads annual cost (On-premises costs estimation) .607.2.Migration cost .617.3.AWS annual cost .62APPENDIX . 651.PDM steps to issue partner access codes .65v2.9.1 (October 2021)4
AWS Migration Portfolio Assessment: User GuideGetting Started with AWS Migration PortfolioAssessmentAWS Migration Portfolio Assessment (MPA) is a web application that simplifies the assessment process ofthe on-premises portfolio in preparation for the migration to AWS.Portfolio assessment is the discovery, identification, classification and grouping of on-premises computeinfrastructure by application in order to determine the feasibility, effort, cost, tools and resources, allleading to a Migration Effort Analysis and Migration Priority Pipeline that can guide the customer inplanning their migration to Amazon Web Services.In the current version, MPA consolidates the portfolio data in one place, helps in migration planning andprovides the information required for validating the migration business case: On-Premises and equivalentAWS cost estimation, EC2 recommendations, migration strategy and migration project cost.Are You a First-Time User of AWS Portfolio Assessment?You can access AWS Migration Portfolio Assessment at AWS Migration Portfolio Assessment.AWS Employees can login through Midway Authentication, and as such an YubiKey is needed.AWS Partners can sign in with AWS Partner Central, hence use their APN Portal credentials.It's important to note that only Select, Advanced and Premier tiers are allowed access to MPA. ForRegistered, access can be granted (ex: for training purposes) through access codes.Partner Delivery Managers can issue access codes for their partners, see Appendix for details.When to use AWS Migration Portfolio Assessment?AWS Migration Portfolio Assessment can be used during the early stage of the migration discussion whenthe customer’s portfolio data is available. The target architecture on AWS may differ from the on-premisesarchitecture, this application can be used to have a directional sense in the beginning of the process withoutgetting into the details.AssumptionsIn this document, the following are assumed: You are either an AWS employee or an AWS Partner with the migration experience. You have either a customer’s CMDB extract or their portfolio discovery results, which can be inform of files, or stored in ADS (AWS Application Discovery Service). You have authorization to store the customer’s on-premise infrastructure data in AWS MigrationPortfolio Assessment. It is recommended to also have the customer’s agreement as you will see intheat the bottom of every MPA page and also accessible directly here. You are at the early stage of the migration discussion and actual planning has not yet started.v2.9.1 (October 2021)5
AWS Migration Portfolio Assessment: User GuidePortfolio Analysis User flow1. Gather Customer Portfolio DataServer DataOn-Premises portfolio data is the prerequisite to use MPA. Gather on-premises server data, shared storage data andnetwork bandwidth to compare the estimated on-premises cost with the estimated AWS usage cost. Save server datain a excel or comma-separated values (CSV) format prior to attempting data import. Below is the list of commonlyseen issues that can cause a validation failure or give an erroneous result.1.Check for data type mismatch in Server Data.Storage Size, RAM/Memory Size, CPU Count, Cores per CPU, Threads per CPU, CPU Utilization Percentage,RAM Utilization Percentage, Server Usage Percentage, Storage Utilization Percentage and IOPS are numericattributes. Excel formulas may result in values such as “#N/A” or “#Error”. Please remove the invalid values.2.Check for return characters in file. Some data files may contain additional return characters which can result inerroneous import.3.Check for mandatory attributes.Server ID - The Server ID attribute does not need to be the actual ID; it could be the server hostname or IP. Incase there are duplicate server IDs, the import process will show the duplicate servers and request that you toselect the valid ones.OS Name – OS Name and OS Version can be in separate data attributes or in one attribute.Processor – CPU Count, Cores per CPU and Threads per Core. MPA assumes a value of 1 for thecorresponding attribute if the CPU Count, or the number of Cores per CPU or the number of Threads per Coreis not provided. For finding the best AWS match, MPA computes the total of the number of processors timesnumber of cores per CPU times number of threads per core. For Physical servers MPA (more exactly theMigration Hub EC2 recommendations service) also multiplies the result with 2 in order to account for the factthat physical CPUs are generally more powerful than virtual threads.RAM - RAM Size is required to recommend EC2 instance type and On-Premises RAM cost.4.Check for other important attributes.Peak CPU Utilization - Peak utilization data helps to recommend target EC2 instance type. In case it is notavailable, MPA uses a default value. You can change the default value and rerun the estimation.Peak RAM Utilization - Peak utilization data helps to recommend target EC2 instance type. In case it is notavailable, MPA uses a default value. You can change the default value and rerun the estimation.Server Usage % (Server Uptime) - Server Uptime is required to recommend the payment type (Std 3 AU vs OnDemand) that cost least to the customer.Physical/Virtual - For the portfolio that has both virtual and physical servers, this attribute is mandatory.Otherwise, MPA assumes all the servers are physical server.Hypervisor - Hypervisor helps to estimate on-premises hypervisor license cost. At this moment applicationsupport - Xen, Hyper-V, and VMWare. In case MPA can't find the match, it uses “VMWare” as a default andestimates the cost.Note: You can download the sample CSV file from MPA application.v2.9.1 (October 2021)6
AWS Migration Portfolio Assessment: User GuideBusiness Application DataApplication data is required for migration planning that includes – Application Grouping, Wave Planning andApplication Prioritization. Save application data in an Excel workbook sheet or comma-separated values (CSV)format prior to attempting data import. Prior to collecting the application data, identify the migration’s businessdriver and capture data attributes that can categorize the applications based on migration’s business driver. If acustomer wants to migrate applications based on business criticality, then Service Level Agreement, BusinessCriticality, Number of Users can be used to identify the business criticality of an application. Application ID,Application Name, SLA, Business Criticality, Business Owner’s Name, Business Owner’s Email, Number of Users,Revenue Impact are some of attributes that may be useful for application data.Mapping (Server to Application) DataApplication-Server Mapping data has list of servers required for an application to function and one server may beused by more than one application. This information is used to infer application dependencies. Save mapping data inan Excel workbook sheet or comma-separated values (CSV) format prior to attempting data import. Application IDand Server ID are the two fields required for mapping data. Mapping data alone without server communication datacan be used to infer application dependencies.Server Communication DataServer communication is used to infer server dependencies and finally application dependencies. Savecommunication data in an Excel workbook sheet or comma-separated values (CSV) format prior to attempting dataimport. Source Server ID, Source Server IP, Port, Target Server ID, Target Server IP, Target Server Port,Communication protocol, Number of connections are the fields required for server communication data.Database DataDatabase data is required for AWS Database Recommendations and Database TCO. Gather on-premises databasedata, including details of the servers each database resides on. Specify the Target AWS DB Service, else MPA willuse the one configured as default in the assumptions.Note: For accurate recommendations and on-prem cost estimations, MPA expects the below values; MPA does abest effort attempt to match input values to these, if exact value is not provided. DB Instance Engine and Target AWS DB Service: Aurora MySQL, Aurora PostgreSQL, MariaDB,MySQL, PostgreSQL, SQL Server, Oracle Enterprise / Standard Edition: Enterprise, Standard, Standard One, Standard Two, Express, Web DB Instance Deployment Plan: Multi-AZ, Single-AZ License Model: Bring your own license, License included, No license requiredNote: MPA relies on the computing and memory specifications of the corresponding server in order to make theoptimal RDS recommendation for each database. For that reason, please ensure that: the database points to a server id that exists in the servers list and the CPU, cores, threads and RAM total size of that server don't exceed the maximum supported values forRDS instances. For physical servers, MPA multiplies the total number of threads by 2, hence the enterednumber of CPUs times number of Cores times number of Threads should be 2x less than the maximumsupported by RDS instances. See here the list of RDS instance types.Application Dependency and Database to Application DataMPA uses these data to further enrich the Application Grouping functionality by inter-linking applications andlinking applications to databases and further to the servers those databases belong to.v2.9.1 (October 2021)7
AWS Migration Portfolio Assessment: User Guide2. Create a new portfolioOnce you are logged into the application, you will see the landing page of MPA. The landing page hasinformation about the tool.Click onempty.Click onportfolio creation.to view the list of portfolios. If you have not created a portfolio in the past, the list will beto create a new portfolio. Customer Name and Portfolio Name are mandatory fields forAWS Partner users can search for existing customer account or create a new customer account. It isrecommended to not duplicate the customer accounts, create a customer account once and use for all portfolioof that customer.The next step will take you to MPA’s server data import wizard.v2.9.1 (October 2021)8
AWS Migration Portfolio Assessment: User Guide3. Manage the Portfolio DataAfter gathering the customer data, you will import the data into an MPA portfolio. You can later add more datathrough imports, delete some of the existing records, bulk update them or update them on by one with in-line edit.Throughout your handling of the portfolio data, MPA keeps an eye on the quality of the data and gives you asummary on the Assets pages.3.1.Import Data (from files)The data import flow is specific to the different entities (assets and dependencies) that MPA expects. For this reason,you will have to upload a separate file for each data entity. You can download demo and template files on the mainimport page itself – while these contain all entities in a file, remember you will need to upload separate files.Server DataServer Data is required to recommend target EC2 instance type, estimate the AWS usage cost, estimate on-premisespurchase cost, recommend server migration pattern and estimate the migration project cost.On the Servers tab on the Assets page, click on(if no data was loaded yet) to start the import wizardprocess. If data was already loaded, you will see the Import More Data option under.Click onto select the server data file (CSV or Excel).There is link to download a sample CSV file. The sample CSV file can be used as a reference.The next page has the list of recommended and optional attributes to map between the file headers and what MPAexpects. Match the MPA schema name with the corresponding header in the file. MPA does a best effort attempt toauto-match for headers as well as units of measurement, but it is your responsibility to validate the mappings.Wherever MPA cannot find the attributes, provide a match and select the correct units.Note: notice how in the above example MPA was not able to auto-match a header to the Number of Threads per CPU-Core andinstead it has labeled it as “Do not import”. This can be because the field is missing in the file, but if the it is present, do select thecorrect value from the dropdown.v2.9.1 (October 2021)9
AWS Migration Portfolio Assessment: User GuideFor the optional header mapping MPA lists remaining file attributes and allows to select the MPA schema attributesfrom the drop down. Repeat the process of matching. Do ensure units of measurement are correctly selected as anerror in this regard can impact analysis considerably.The next page shows duplicate records. This page appears for server data that has duplicate server IDs. Select therecords that you want to ingest and ignore the duplicates.The final page in the import wizard shows the server data, click onMPA will take you to the Server Page. From thedata.to complete the import.you can ingest more data or delete the already importedApplication and Database DataBusiness application Data is not required for cost estimations but it is fundamental for grouping and migration waveplanning of a large-scale application portfolio. Database data can be used in cost estimations and also allow forbetter grouping of applications. Follow the same steps described above in the Server Data section to import data inthe Applications and Databases tabs on the Assets page.DependenciesMapping (Server to application) Data is not required for cost estimations but it is fundamental for grouping andmigration wave planning of a large-scale application portfolio. Likewise, for Server communication, Database toapplication and Application dependency data. Follow the same steps described above in Server Data section toimport data in the corresponding tabs on the Dependencies page.v2.9.1 (October 2021)10
AWS Migration Portfolio Assessment: User Guide3.2.Import Data from ADSFor those customers that have used ADS (AWS Application Discovery Service) to collect data about their serversand applications, MPA allows to pull that data from ADS itself.MPA will load from ADS the data corresponding to Servers, Applications and Server to Application dependencies.You will need the secrets of a user authorized to access the customer's AWS account where the ADS data is stored.In the Import from ADS page Portfolio data Import, enter the access key information and the specify the regionwhere the ADS data is stored in the customer’s AWS account, and press Import from ADS.Note: MPA is not part of the AWS console.Deleting data from ADS will not delete it from MPA.Importing duplicate data from ADS will overwrite the existing data in MPA.Importing duplicate data from a CSV or Excel file will overwrite the existing ADS data in MPA.Re-importing data from ADS will overwrite the existing records.You can’t import from multiple AWS accounts. Create a new portfolio if you want to import data from adifferent AWS account.As a best practice, create an IAM user with only the discovery:DescribeConfigurations anddiscovery:ListConfigurations actions and use its Access Key.v2.9.1 (October 2021)11
AWS Migration Portfolio Assessment: User Guide3.3.Data ValidationThe portfolio assessments are only as good as the quality of the data entered in the portfolios.MPA employs data validation rules in order to safeguard against common data ingestion errors and allow you theconfidence of sound outcomes.You will see the validation results on the Servers, Applications and Databases asset pages.This might feel overwhelming at first glance, but look! there are 7 rules that passed successfullyA record having failed a validation rule doesn’t mean that your analyses will not be run or that the record will beexcluded from the results. It means that some of the results will not be as accurate as they could be, should the databe corrected. MPA provides a high-level sense of the potential effect of each rule through the Impact area andassociated severity.You can scroll over each rule name for a brief description of what is intended for. For more details, you can alsoenter the edit mode by clicking the icon.You can filter the asset grid to see the records that are failing a particular rule by clicking the funnel icon on the rulerow.By default, MPA provides built-in rules that check for the commonly encountered issues – you cannot delete ormodify these rules; though not recommended, you can disable them.You can also create your own rules by selecting Add new rule from the Actions menu on the asset pages.In creating a new rule, you can specify multiple attributes from the same entity (ex: servers), but you can alsospecify attributes from different entities (ex: from servers and applications) – the rule will “scan” the records byjoining the two entities through the corresponding dependencies (see the Dependencies page).Before saving the rule, MPA does an initial validation, so clickfirst. If everything checks out, theshows up and you can save it. You can always come back and edit your own rules.You can also copy custom rules created from different portfolios you have access to – just use the Import rules in theActions menu.Download the rule results if you need to have an in-depth research or work on addressing the issues offline.You can disable rules that you have created, or delete them entirely if no longer needed.v2.9.1 (October 2021)12
AWS Migration Portfolio Assessment: User GuideRule evaluationMPA runs an assessment of the rules in your portfolio every time you open an Asset page. After you are donemaking in-page changes to the data (see Update the data below), it is a good practice to refresh the rules as well, byclicking the Refresh button in the rules box:. You can also trigger the rule refresh through theActions button.Update the dataOnce you have identified the data you want to change after reviewing the validation rules, you can update the datastraight in MPA. While you can always delete all the data and import a fresh batch, MPA makes it easy to make theupdates in the tool itself.On the data pages (corresponding tabs under Assets and Dependencies), the grid shows ingested data and allows forquick update via bulk edit as well as delete. You must select the records that you want to update using thecheckboxes on the left-hand side. For bulk update, select Edit and then the attribute you want to update; specify thenew value and click Update. By checking thebox, all records will be updated not just the selected ones.You can also update the attributes in-line, in the grid itself – just hover the field in the grid and click theNote:1. Do not import the data of physical host server data, import data of virtual servers running on the host.2. Server import validates for data type. e.g., “Number of CPU” attributes should be numeric; it should not have “#**” oralphanumeric character.3. Server OS, CPU count and RAM size is minimum requirement to use this application.4. CPU and RAM Utilization helps to better estimate the EC2 Type on AWS.5. Disk Storage without storage utilization gives incorrect financial analysis.6. Read the notes on the import page to know more about importance of various attributes.v2.9.1 (October 2021)13
AWS Migration Portfolio Assessment: User Guide4. Add Shared Storage and Network Bandwidth DataClick on thetab on the Assets page. The Storage and Network page has options to add the sharedstorage and on-premises network bandwidth data of portfolio.Click onto add shared storage. There is the option to select SAN, NAS and Object storage types.For SAN storage provide volume size and peak IOPS. IOPS information and volume size are used torecommend the EBS type.For NAS storage provide volume size and select EBS or EFS. EFS is not available in all the AWS regions;validate the AWS region before selecting EFS. EBS is the recommended storage type.For Object storage you can choose between S3Standard and S3Glacier. For S3Standard, provide volumesize and infrequent access percentage. Infrequent access percentage is part of object storage that is not usedon daily basis but used to keep data of inactive transactions.Select Usable storage whenever OS, File share system and RAID overhead has been deducted from Rawsize. For Object storage type, raw and usable are the same.Note:a. Don’t double count server disk storage with shared storage. Server disk storage that was ingested withserver data is not considered as shared storage.b. MPA allows you to enter each on-premises drive separately; if you only have the combined values,make sure you have the total IOPs as well. You can specify a description for the shared storage item; itis not used anywhere else in MPA at this point, but it is provided here for you to be able to discernbetween the different items.c. Change assumptions related to storage in Assumptions - AWS Storage, On-Pr
planning their migration to Amazon Web Services. In the current version, MPA consolidates the portfolio data in one place, helps in migration planning and provides the information required for validating the migration business case: On-Premises and equivalent AWS cost estimation, EC2 recommendations, migration strategy and migration project cost.
4 AWS Training & Services AWS Essentials Training AWS Cloud Practitioner Essentials (CP-ESS) AWS Technical Essentials (AWSE) AWS Business Essentials (AWSBE) AWS Security Essentials (SEC-ESS) AWS System Architecture Training Architecting on AWS (AWSA) Advanced Architecting on AWS (AWSAA) Architecting on AWS - Accelerator (ARCH-AX) AWS Development Training
AWS Directory Amazon Aurora R5 instance Service AWS Server Migration Service AWS Snowball AWS Deep Amazon GameLift Learning AMIs AWS CodeBuild AWS CodeDeploy AWS Database Migration Service Amazon Polly 26 26 20 40 12 0 5 10 15 20 25 30 35 40 45 2018 Q1 2018 Q2 2018 Q3 2018 Q4 2019 Q1 New Services& Features on AWS
AWS SDK for JavaScript AWS SDK for JavaScript code examples AWS SDK for .NET AWS SDK for .NET code examples AWS SDK for PHP AWS SDK for PHP code examples AWS SDK for Python (Boto3) AWS SDK for Python (Boto3) code examples AWS SDK for Ruby AWS SDK for Ruby co
AWS Migration Hub API (p. 68) AWS Migration Hub Home Region API Remember that only your migration tracking data is stored in your home region. You can migrate into any AWS Region supported by your migration tool. If you have a tool that you want to integrate with AWS
AWS instances with Nessus while in development and operations, before publishing to AWS users. Tenable Network Security offers two products on the AWS environment: Nessus for AWS is a Nessus Enterprise instance already available in the AWS Marketplace. Tenable Nessus for AWS provides pre-authorized scanning in the AWS cloud via AWS instance ID.
Splunk Portfolio of AWS Solutions AMI on AWS Marketplace Benefits of Splunk Enterprise as SaaS AMI on AWS Marketplace App for AWS AWS Integrations AWS Lambda, IoT, Kinesis, EMR, EC2 Container Service SaaS Contract Billed through Marketplace Available on Splunk Enterprise, Splunk Cloud and Splunk Light End-to-End AWS Visibility
pa/1g pa/1f pb/2f pc/2g pd/4f 156 pf/3g pf/3f pg/3g pg/3f en: pcfileur welding positions aws: 1g en: pa aws: 1f aws: 2g en: pc aws: 2f en: pb aws: 3g en: pg down en: pf up aws: 3f down en: pf aws: 4g en: pe aws: 4f en: pd 156
2.3 Gresham’s Law 2.4 Money and near money 2.5 Role of money in Capitalist, Socialist and mixed Economy 3. Money Supply and Banks (14) 3.1 Narrow and broad definition of money 3.2 Alternative measures of money supply in India and their components 3.3 Concept of High Powered Money 3.4 Definition of Bank – Functions of bank 3.5 Multiple credit creation by bank and limitations to it. 4 .
