--- language: "en" --- # Cloudamize Knowledgebase ## Pinned articles * ### [📘 Cloudamize MCP Server End User \& Integration Guide](https://support.cloudamize.com/kb/cloudamize-mcp-server-end-user-user-integration-gu.md) 🌐 Overview The Cloudamize MCP Server is a containerized MCP gateway that exposes Cloudamize APIs to AI tools it connects Cloudamize to AI assistants, AI agent... * ### [How to Start \& What to Expect (AWS)](https://support.cloudamize.com/kb/how-to-start-what-to-expect-aws.md) Enablement Materials Sales Enablement (Level 100) Enablement Deck Video Overview Platform Overview (Level 200) Enablement Deck Video Overview Platform Deep-Div... ## Documentation ### [Getting Started](https://support.cloudamize.com/kb/getting-started.md) ### [FAQ](https://support.cloudamize.com/kb/faq.md) ### [Guides](https://support.cloudamize.com/kb/guides.md) ### [Videos](https://support.cloudamize.com/kb/videos.md) ### [Release Notes](https://support.cloudamize.com/kb/release-notes.md) * ### [Health Status Page](https://support.cloudamize.com/kb/health-status-page.md) * ### [Marketing \& Branding Guidelines](https://support.cloudamize.com/kb/marketing-branding-guidelines.md) --- language: "en" --- # Network Discovery ## Viewing the Results: Network Discovery Inventory Settings Tab The **Network Discovery** **Inventory Settings** Tab is available under the **Discovery** Option. To access this tab, select the "Discover" option from the Cloudamize Landing Page. ![Screenshot 2026-07-21 at 11.50.28 AM-20260721-085657.png](https://support.cloudamize.com/__attachments/a_549e76e570c086031895ba65b766e9c384cb13202dfade5f982db10851cb2970/Screenshot%202026-07-21%20at%2011.50.28%E2%80%AFAM-20260721-085657.png?cb=10404255049578f506ecb465e7ed808f) Once the tool has completed its run and uploaded the data to the Cloudamize portal, you can view the results on the Network Discovery tab in the Inventory Settings page of the portal. ![image-20260225-082330.png](https://support.cloudamize.com/__attachments/a_9deb1a9d0182a7e06292969182380a018a7182537f17d9b49c2f7defa683eb5b/image-20260225-082330.png?cb=fa7562b827df511d205c90314c482f5a) Network Discovery tab before data upload ![image-20260225-082046.png](https://support.cloudamize.com/__attachments/a_5c242826b7cd0801f3d3cde10c454cf2424a71ff019a133286b9071fc425989f/image-20260225-082046.png?cb=10f81ad8baf30a0b71a844ac86db61cb) On this tab, you can view all discovered network devices and any related details that have been discovered, labeled by column. The results are searchable using the search box in the top left. The network discovery agent will collect the following * Hostname * Host(IP address) * MAC Vendor * Open Ports * OS Name * OS Confidence The "Included in Assessment" column identifies any servers that are connected to the portal by a Cloudamize data collector - Agent, Agentless, Hypervisor, or vCenter connections are all valid connections. Using this, you can identify servers that aren't currently included in the assessment and quickly add them if desired, for example, by adding their IP address to an existing Agentless Data Collector. ### **Export Network Discovery Report** The **Export Network Discovery Report** button (represented by the yellow document icon with a downward arrow) allows users to download a comprehensive summary of all discovered assets found during the network scanning process. ![image-20260225-082834.png](https://support.cloudamize.com/__attachments/a_6c422c0a54c1f5a5fa646edf886f60f25138c23b1977b39919b782afcc11637a/image-20260225-082834.png?cb=de62400a67ac67db821647a4448c3589) ### Support The Network Scanner wrapper is provided as-is. Cloudamize can offer assistance in configuring the command line for the tool, but cannot offer support for the nmap tool itself. If you have any queries, please get in touch with the helpdesk via our [++Helpdesk Portal++](https://cloudreach-software.atlassian.net/servicedesk/customer/portal/9) or by email at [++helpdesk@cloudamize.com++](mailto:helpdesk@cloudamize.com). --- language: "en" --- # Transform Cloudamize Ingestion Agent **Version:** 1.0.0 **Last Updated:** 2026-07-17 **AWS Marketplace:** [https://aws.amazon.com/marketplace/pp/prodview-xxv2mi3oqqduw?sr=0-1\&ref_=ucaf\&applicationId=AWSMPContessa](https://aws.amazon.com/marketplace/pp/prodview-xxv2mi3oqqduw?sr=0-1&ref_=ucaf&applicationId=AWSMPContessa) **Purpose** This guide explains how to deploy, configure, run, and troubleshoot the Cloudamize Data Ingestion Agent in AWS Transform. The content is structured for easy reading in Confluence and clean export to PDF. ## Overview The Cloudamize Data Ingestion Agent retrieves migration discovery data from Cloudamize and delivers it in the AWS Transform schema. It pulls server inventory, application details, dependencies, and database information from a Cloudamize plan, then returns a normalized JSON payload ready for AWS migration planning. Use this agent when you already have Cloudamize discovery data and want to bring it into AWS Transform without manual export or reformatting. ### How the solution works Two agents work together on the AWS Transform platform: * **Cloudamize Migration Orchestrator** --- the agent you interact with in the Transform chat UI. It handles credential setup and coordinates the pull workflow. * **Cloudamize Data Ingestion Agent** --- a background worker that connects to the Cloudamize MCP server, retrieves data, and normalizes it. You interact only with the orchestrator. The pull agent runs automatically behind the scenes. ### Normalized output collections | Collection | Contents | |--------------------------|---------------------------------------------------------------------| | Server Details | Hostname, operating system, CPU, RAM, storage, and utilization data | | Application Details | Application name, type, and connection counts | | Application Mapping | Mapping of applications to servers | | Database Details | Engine type, edition, and size | | Server Communications | Network flows between servers including ports and processes | | Application Dependencies | Directed dependency relationships between applications | ## Prerequisites Complete the following requirements before deployment. * An active AWS account with AWS Transform enabled * Bedrock model access enabled for `us.anthropic.claude-sonnet-4-5-20250929-v1:0` * A Cloudamize account with at least one active migration plan * A valid Cloudamize JWT token for MCP access * Your account allowlisted for the Cloudamize agents in AWS Transform * Visibility of `cloudamize-data-ingestion-agent` and `cloudamize-migration-orchestrator` in the Transform configuration flow * IAM permissions to deploy CloudFormation stacks, create IAM roles, and manage Secrets Manager secrets ### Container images The pre-built container images are shared with your AWS account from the Cloudamize production registry. The default image URIs in the CloudFormation template already point to the production account. You do not need to build or push images. **Note** If your account lacks access to the agent's images and you do not see it in the partner agent list, contact Cloudamize support. ### Network access requirements The agent containers require outbound HTTPS access to the following endpoints: * `mcp.cloudamize.com` on port `443` * AWS Secrets Manager API endpoints * AWS CloudWatch Logs API endpoints * Amazon ECR endpoints for image pulls * Bedrock model inference endpoints * AWS Transform Agentic API endpoints If deploying in VPC mode, ensure egress is available through a NAT gateway or equivalent routing path. ## Subscription ### Step 1: Subscribe via AWS MarketPlace 1. Product market place listing: [https://aws.amazon.com/marketplace/pp/prodview-xxv2mi3oqqduw?sr=0-1\&ref_=ucaf\&applicationId=AWSMPContessa](https://aws.amazon.com/marketplace/pp/prodview-xxv2mi3oqqduw?sr=0-1&ref_=ucaf&applicationId=AWSMPContessa) 2. Click on View Purchase Options ![Screenshot 2026-07-29 at 5.18.38 PM.png](https://support.cloudamize.com/__attachments/a_d9452eb2b08cde351d9c22f7d5da5f88efdb3d8866889885999d120ee4b89eef/Screenshot%202026-07-29%20at%205.18.38%E2%80%AFPM.png?cb=e5554f7e073be7d618c459a35c2f7e3c) 3. Click on Subscribe ![Screenshot 2026-07-29 at 5.19.37 PM.png](https://support.cloudamize.com/__attachments/a_616a93c1c373387b7fe57195ce7fdbd2f715c78c004d0f965228b00ffb02ce73/Screenshot%202026-07-29%20at%205.19.37%E2%80%AFPM.png?cb=7fcfd8c1a79ff8378396c9bdcb10b393) ## Installation: Deployment uses a single CloudFormation template that creates both agent runtimes, IAM roles, and optionally the JWT secret. ### [cloudamize-agents-marketplace.yaml](https://support.cloudamize.com/__attachments/a_68cd44600b823f4246210ff76864209afff044dae20a8dce27eb0d83e0b17ce2/cloudamize-agents-marketplace.yaml.md?cb=4d056a2aadc5fec6d6447b78481ca380) ### Deployment through the AWS Console #### Step 1: Deploy the CloudFormation stack(using Admin access credentials) 1. Open the AWS CloudFormation console in `us-east-1`. 2. Select **Create stack** and choose **With new resources (standard)**. ![create stack with new resources.png](https://support.cloudamize.com/__attachments/a_8a1a61b93860fce4f3850e2a756fec9186e05c129684d548a8a21c252f9dcbde/create%20stack%20with%20new%20resources.png?cb=e3718ee4b15fba2d6fe7c4b531f4750f) 3. Upload the template file `deployments/cloudformation/cloudamize-agents.yaml`. ![upload the CF Template.png](https://support.cloudamize.com/__attachments/a_ab44c5f48b327d5ba744fa2cfd5aeef513d0e9281fba6346493822319d82a710/upload%20the%20CF%20Template.png?cb=2d8d729c9848a4f5b15eafe1e619e2d0) 4. Enter the required and optional parameters shown below. 5. Acknowledge IAM resource creation and submit the stack. 6. Wait until the stack reaches `CREATE_COMPLETE`. ![Screenshot 2026-08-12 at 6.46.51 PM.png](https://support.cloudamize.com/__attachments/a_eff19b48e9ff863f3130923ccf19832f19bc0cef06256dd983c6debb3b780617/Screenshot%202026-08-12%20at%206.46.51%E2%80%AFPM.png?cb=298648cfb93c37e66552baffccb97adb) ### Deployment through the CLI Use the following commands if you prefer command-line deployment. #### Deploy using an existing JWT secret Bash aws cloudformation deploy \ --region us-east-1 \ --stack-name cloudamize-agents \ --template-file deployments/cloudformation/cloudamize-agents-marketplace.yaml \ --capabilities CAPABILITY_NAMED_IAM \ --parameter-overrides \ JwtSecretArn=arn:aws:secretsmanager:us-east-1::secret: #### Deploy and let the stack create the secret Bash aws cloudformation deploy \ --region us-east-1 \ --stack-name cloudamize-agents \ --template-file deployments/cloudformation/cloudamize-agents-marketplace.yaml \ --capabilities CAPABILITY_NAMED_IAM \ --parameter-overrides \ CloudamizeJwtToken= \ JwtSecretName=cmz/auth/token #### Reuse existing IAM roles Bash CreateAgentCoreExecutionRole=false \ ExistingAgentCoreExecutionRoleArn=arn:aws:iam:::role/ \ CreateAWSTransformAgentInvokeRole=false \ ExistingAWSTransformAgentInvokeRoleArn=arn:aws:iam:::role/ #### Validation commands Bash aws cloudformation describe-stacks --stack-name cloudamize-agents \ --query 'Stacks[0].StackStatus' aws logs describe-log-streams \ --log-group-name /aws/bedrock-agentcore/ \ --order-by LastEventTime --descending --limit 5 \ --region #### JWT secret options **Option A --- Let the stack create the secret** | Parameter | What to enter | |----------------------|-----------------------------------------------------| | `JwtSecretArn` | Leave blank | | `JwtSecretName` | Name for the new secret, typically `cmz/auth/token` | | `CloudamizeJwtToken` | Paste your Cloudamize JWT token | **Option B --- Use an existing Secrets Manager secret** | Parameter | What to enter | |----------------------|---------------------------------| | `JwtSecretArn` | Full ARN of the existing secret | | `JwtSecretName` | Ignored when an ARN is provided | | `CloudamizeJwtToken` | Ignored when an ARN is provided | If you use an existing secret, its value must contain either a plain-text JWT string or a JSON object with the key `CLOUDAMIZE_JWT_TOKEN`. ### JWT token requirement Generate a cloudamize JWT token . [cmz-auth.sh](https://support.cloudamize.com/__attachments/a_0e49c332358fb5a663d9fff738dcd805f9dc1c1ba1c9f2260a48710c475bf9cd/cmz-auth.sh.md?cb=24a2f20910f73fb761595e56ec81c8ed) #### How to Use `cmz-auth.sh` 1. **Save the script** as `cmz-auth.sh` in your working directory. 2. **Make it executable:** bash chmod +x cmz-auth.sh 3. **Run the script** with your credentials: bash API_USER='your-email@example.com' API_PASS='your-password' ./cmz-auth.sh 4. **If multiple engagements are found** , the script lists available Customer IDs --- enter the relevant **Customer ID** when prompted. 5. **Token is returned** on stdout **Important** JWTs expire after 12 hours. If the token has expired, the job will fail until the secret is updated with a fresh token. ***NOTE: Prior running the AWS job please make sure to update the JWT Token AWS secret manager*** #### Step 2: Record stack outputs After deployment completes, capture the following values from the **Outputs** tab. | Output Key | Used for | |----------------------------------|-----------------------------------| | `DataIngestionRuntimeArn` | Runtime binding in AWS Transform | | `OrchestratorRuntimeArn` | Runtime binding in AWS Transform | | `AWSTransformAgentInvokeRoleArn` | Runtime binding in AWS Transform | | `CloudamizeJwtSecretArn` | JWT secret rotation and reference | #### Step 3: Bind runtimes in AWS Transform ***(Note: Admin access is mandatory for this action)*** 1. Open AWS Transform and navigate to agent configuration. ![Screenshot 2026-08-11 at 6.01.11 PM.png](https://support.cloudamize.com/__attachments/a_dc864d30bb30ebae581c019098b601f74687946e779a38b83a2216bd6dd62d61/Screenshot%202026-08-11%20at%206.01.11%E2%80%AFPM.png?cb=49580b393bf5e4b1a81ecfe139b091db) 2. Select **Cloudamize Migration Orchestrator**. 3. Enter the `OrchestratorRuntimeArn` and `AWSTransformAgentInvokeRoleArn`. 4. `OrchestratorRuntimeArn ` can be fetched from **Amazon Bedrock AgentCore** \>**Build** \>**Runtime** \>**cloudamize_migration_orchestrator** \>copy **Runtime ARN** 5. `AWSTransformAgentInvokeRoleArn` IAM\>**AWSTransformAgentInvokeRole**\>copy ARN Then configure them ![configure agent.png](https://support.cloudamize.com/__attachments/a_4a63ee523f031baf282fd26a9ca5d42e8027b1e9a9bbf2355efcf39ad1080e17/configure%20agent.png?cb=ac215ed615ba602929a29ab7be900d4e) 6. Repeat for **Cloudamize Data Ingestion Agent** using `DataIngestionRuntimeArn`. 7. Save the configuration. **Result** After the runtime bindings are saved, the agents are ready for use. Runtimes start automatically when a Transform job invokes them. **Important** Runtime bindings must be configured manually for both console and CLI deployments. ## Running a Transform Job ### Start a job 1. Open AWS Transform, go to workspace, and create a job option on the chat UI. 2. Select the **Cloudamize Data Ingestion** agent. ![Screenshot 2026-08-11 at 6.12.03 PM.png](https://support.cloudamize.com/__attachments/a_e50bd7c8476c525510bfd732bbf13f8d79a412ebde965e649df6c15c28b53a17/Screenshot%202026-08-11%20at%206.12.03%E2%80%AFPM.png?cb=c57e6f09ce9fea8c407ef47c0fad6cf6) 3. Start chatting or executing workflow with sample prompts * Pull the migration portfolio assessment for plan 5 * List my Cloudamize plans * Get server and application data from Cloudamize plan 12 ### Connect credentials On the first request in a job, the orchestrator prompts you to connect your Cloudamize credentials. 1. Select an existing Secrets Manager connector, or create a new one. 2. Provide the **Secret ARN** for the secret holding your JWT. 3. Optionally provide the **KMS key ARN** if the secret uses a customer-managed key. 4. Submit the form. The agent resolves the JWT securely and caches it for the remainder of the job. Reference: ![Screenshot 2026-07-17 at 4.30.05 PM.png](https://support.cloudamize.com/__attachments/a_5b0c8d2296008402c84e0f1a81c36aea8d85f8be5d21f00fbe31da11cbab9d80/Screenshot%202026-07-17%20at%204.30.05%E2%80%AFPM.png?cb=0e5c53e775c644d06088c18f79246ff9) ### Find a plan ID If you do not know the plan ID, ask the orchestrator to list available Cloudamize plans. It returns plan IDs and display names so you can choose the correct plan. ![Screenshot 2026-07-17 at 4.47.12 PM.png](https://support.cloudamize.com/__attachments/a_778b179d3abf3ee6675ca864b20bec98bf42f8944b5b20cd6c5f27971f56fc06/Screenshot%202026-07-17%20at%204.47.12%E2%80%AFPM.png?cb=07a799a69cfe63ca2d24a4109bef8fd4) ### Retrieve assessment data After credentials are resolved and a plan ID is provided, the workflow performs these actions: 1. Launches a subagent instance 2. Connects to the Cloudamize MCP server 3. Retrieves the full Migration Portfolio Assessment for the plan 4. Normalizes the data into the AWS Transform schema 5. Returns the result in chat ![Screenshot 2026-07-17 at 4.49.42 PM.png](https://support.cloudamize.com/__attachments/a_38adb6c0b6a7b0c47ad7ff5672b6663eb3ccd1c18d027345aa41325321659ca5/Screenshot%202026-07-17%20at%204.49.42%E2%80%AFPM.png?cb=fec2f063e0d6e54ffdd4e0e0cd1a399a) This process typically takes from 30 seconds to a few minutes depending on portfolio size. ### **FSxN recommendations in the pulled output** When the plan includes EBS-attached disks eligible for NetApp ONTAP conversion, the pulled recommendations now include FSxN cost/savings details: ![Screenshot 2026-09-10 at 7.27.33 PM-20260910-142033.png](https://support.cloudamize.com/__attachments/a_a725c6556acad2f9d1915a0ccda1870f1338d7e5930f7baff3984686affb00a5/Screenshot%202026-09-10%20at%207.27.33%E2%80%AFPM-20260910-142033.png?cb=1841f8e3b4ce49ca59332c3a6ad56228) Full details for all instances, including FSxN entries, are also available in the generated JSON artifact in the workspace panel. ### Timeout behavior | Step | Timeout | Behavior if exceeded | |-----------------------------|------------|-------------------------------------------------| | Credential form completion | 30 minutes | The job fails and a new job must be started | | Subagent data retrieval | 10 minutes | The job fails with a timeout error | | Cloudamize MCP HTTP request | 10 minutes | The request retries automatically up to 3 times | ## Configuration Reference ### Environment variables The CloudFormation template sets required environment variables to runtime automatically. In most deployments, no manual changes are needed. #### Automatically set variables | Variable | Value | Purpose | |----------------------------|---------------------------|---------------------------| | `AWS_REGION` | Deployment region | AWS SDK region targeting | | `CLOUDAMIZE_JWT_SECRET_ID` | Secret ARN from the stack | References the JWT secret | | `STAGE` | `prod` | API endpoint resolution | ### Using existing IAM roles | Parameter | Value | |------------------------------------------|------------------------------------| | `CreateAgentCoreExecutionRole` | `false` | | `ExistingAgentCoreExecutionRoleArn` | ARN of the existing execution role | | `CreateAWSTransformAgentInvokeRole` | `false` | | `ExistingAWSTransformAgentInvokeRoleArn` | ARN of the existing invoke role | Your existing roles must provide the same permissions as the roles created by the deployment template. ### IAM permission model **AgentCoreExecutionRole** is used by Bedrock AgentCore to run agent containers and requires permissions to: * Read the JWT secret from Secrets Manager * Write logs to CloudWatch under `/aws/bedrock-agentcore/` * Invoke Bedrock models * Pull images from ECR * Call AWS Transform Agentic APIs **AWSTransformAgentInvokeRole** is used by AWS Transform and requires permissions to: * Invoke your Bedrock AgentCore runtimes * Get runtime status * Get runtime endpoint information Both roles use source-account and source-ARN conditions to reduce cross-account misuse risk. ## Updating and Maintenance ### JWT rotation 1. Generate a new token from the Cloudamize MCP Server Admin console. 2. Update the secret value in AWS Secrets Manager. 3. No redeployment is required. The next job uses the updated token. ### Container image updates 1. Cloudamize publishes updated images to the production registry. 2. Update the CloudFormation stack if a new image URI or tag is provided. 3. The runtimes pull the updated image on the next invocation. ### Changing network mode 1. Update the CloudFormation stack. 2. Change the `NetworkMode` parameter. 3. If switching to VPC mode, ensure outbound internet access is available. ### Deleting the deployment 1. Unbind the runtimes in AWS Transform. 2. Delete the CloudFormation stack. 3. Optionally delete the Secrets Manager secret if it is no longer needed. ## Troubleshooting ### Where to view logs Agent logs are available in CloudWatch Logs under `/aws/bedrock-agentcore/`. Logs are structured as JSON and sensitive values are redacted automatically. **Go to AWS Bedrock Agentcore \> Runtime \> cloudamize_migration_orchestrator or cloudamize_data_ingestion_agent** Click on logs , you will be redirected to Cloudwatch Log groups ![Screenshot 2026-07-17 at 3.18.06 PM.png](https://support.cloudamize.com/__attachments/a_9e0df268222c57bd7f700459c7a0609043b881861dc91682e783fdcd998c7bd6/Screenshot%202026-07-17%20at%203.18.06%E2%80%AFPM.png?cb=624947cf0152618109f487e004db8a30) ### Key log events | Log Event | Meaning | |----------------------------------------|-----------------------------------| | `environment.audit` | Agent startup configuration | | `orchestrator.get_credentials.success` | Credentials resolved successfully | | `orchestrator.get_credentials.failed` | Credential resolution failed | | `mcp.tools.call.completed` | Cloudamize MCP call succeeded | | `mcp.tools.call.failed` | Cloudamize MCP call failed | | `schema.map.completed` | Data normalization completed | ### Common issues and resolutions #### Agent fails to start **Symptom:** Runtime never reaches a healthy state. **Resolution:** 1. Check CloudWatch logs for `environment.audit`. 2. Verify `CLOUDAMIZE_JWT_SECRET_ID` points to a valid secret ARN. 3. Confirm the execution role includes `secretsmanager:GetSecretValue`. 4. Confirm Bedrock model access is enabled for `us.anthropic.claude-sonnet-4-5-20250929-v1:0`. #### Credential form does not appear **Symptom:** Connector selection UI is blank or missing. **Resolution:** 1. Verify you are running agent version 1.0.0 or later. 2. Check that the Transform job created a valid HITL step. 3. Contact AWS Transform support if the connector form does not render. #### No CLOUDAMIZE_JWT_TOKEN present **Symptom:** Job fails because the JWT could not be resolved. **Resolution:** 1. Verify the secret exists at the configured ARN. 2. Verify the secret contains either a plain JWT string or JSON with the key `CLOUDAMIZE_JWT_TOKEN`. 3. Confirm the execution role can read the secret. 4. Check for `orchestrator.get_credentials.success` in logs. #### Cannot connect to Cloudamize MCP server **Symptom:** Connection failures to `mcp.cloudamize.com`. **Resolution:** 1. Verify outbound HTTPS access on port `443`. 2. If using VPC mode, confirm NAT or routing supports internet egress. 3. Verify DNS resolution for `mcp.cloudamize.com`. 4. Check whether proxy settings block the connection. #### Subagent reached terminal status FAILED **Symptom:** The orchestrator reports a subagent failure. **Resolution:** 1. Review the subagent CloudWatch logs. 2. Verify the JWT is valid and not expired. 3. Confirm the plan ID exists in Cloudamize. 4. Confirm network connectivity to `mcp.cloudamize.com`. #### Timeout after 600 seconds waiting for subagent **Symptom:** The job fails after 10 minutes. **Resolution:** 1. Large portfolios may take longer to retrieve and normalize. 2. Check network connectivity. 3. Check Cloudamize MCP server health. 4. For plans with more than 10,000 servers, contact Cloudamize support. #### Zero records returned **Symptom:** The job succeeds but `record_counts` are all zero. **Resolution:** 1. Verify the selected plan contains discovery data. 2. Check logs for `schema.map.completed`. 3. Look for `schema.map.empty_payload` warnings. #### Credential step keeps repeating **Symptom:** The orchestrator asks for credentials repeatedly. **Resolution:** 1. Verify you are using version 1.0.0 or later. 2. Start a new Transform job if the issue persists. ### Error reference | Error Message | Likely Cause | Recommended Fix | |--------------------------------------------------------|-----------------------------------------------------------|------------------------------------------------------------| | `No CLOUDAMIZE_JWT_TOKEN present` | JWT missing from the secret or stored in the wrong format | Check the secret contents and expected format | | `Failed to load Cloudamize JWT from Secrets Manager` | Missing IAM permissions | Grant `secretsmanager:GetSecretValue` on the secret ARN | | `Cloudamize MCP returned HTTP 5xx` | Cloudamize service-side issue | Retry after a short wait; transient retries are automatic | | `Cannot connect to Cloudamize MCP server` | Network egress is blocked | Check security groups, NAT, routing, and DNS | | `plan_id must be positive integer` | Invalid plan ID input | Use a positive integer and list plans first if needed | | `subagent reached terminal status FAILED` | Subagent runtime error | Review subagent CloudWatch logs | | `timeout after 600s waiting for subagent` | Large payload or network delay | Check connectivity and contact support for large plans | | `HITL step did not yield a Connector_Id` | Connector form was cancelled or failed | Start a new job and complete the connector step | | `Secret value is empty or malformed` | Secret content is invalid | Store a plain JWT or JSON with `CLOUDAMIZE_JWT_TOKEN` | | `credentials not resolved; call get_credentials first` | Workflow order issue | Start a new job and let the orchestrator handle sequencing | ## Frequently Asked Questions ### General **Do I need a Cloudamize subscription?** Yes. You need a Cloudamize account with active migration plans and MCP access. **What regions are supported?** The agent is tested in `us-east-1`. Other regions may work but have not been validated. **How do I find my plan ID?** Ask the orchestrator to list your Cloudamize plans and select the required ID from the returned list. ### Security and operations **How often should I rotate the JWT?** Cloudamize tokens expire after 12 hours. Update the secret before each working session or automate rotation. **Is the JWT visible to the AI model?** No. The JWT is removed before the LLM processes the message and is redacted from logs. **Can I use a customer-managed KMS key?** Yes. Supply the KMS key ARN when creating or selecting the Secrets Manager connector. **What Bedrock model does the agent use?** `us.anthropic.claude-sonnet-4-5-20250929-v1:0`. **How do I update the JWT without redeploying?** Update the value in AWS Secrets Manager. The next job uses the new token automatically. **What happens if the Cloudamize MCP server is unavailable?** The agent retries transient failures such as HTTP 408, 429, and 5xx responses up to three times with exponential backoff. ## Known Limitations * 10-minute timeout on subagent processing * 30-minute timeout on credential form completion ## Security Summary * Your Cloudamize JWT is stored in your own AWS Secrets Manager account * The JWT is never exposed to the AI model and never appears in logs * All communication with Cloudamize uses HTTPS * IAM roles follow least-privilege design scoped to your resources * Trust policies include source-account conditions to reduce cross-account misuse * Sensitive values in logs are automatically redacted * **Cloudamize support** --- Contact your Cloudamize account team for JWT generation, MCP connectivity, and plan-related issues at helpdesk@cloudamize.com * **AWS Transform support** --- Use for platform issues, runtime binding problems, or HITL UI issues --- language: "en" --- # Inventory Settings * [Instances](https://support.cloudamize.com/kb/instances.md) * [Assets](https://support.cloudamize.com/kb/assets.md) * [Removed Instances](https://support.cloudamize.com/kb/removed-instances.md) * [Network Discovery](https://support.cloudamize.com/kb/NetworkDiscovery.md) --- language: "en" --- # Access Shared Folder Troubleshooting When adding Windows remote hosts to an Agentless Data Collector, you may encounter the error: **Failed to access the shared folder on Agentless Data Collector from the remote host**. This article outlines the key troubleshooting steps to resolve this error. ## **Shared Folder Access Error** When the remote Windows host cannot access the shared folder in the Agentless Data Collector machine, the following message will appear in the following format in Cloudamize ADC output: AutoIt Failed to access the shared folder on Agentless Data Collector from the remote host ## ++Troubleshooting steps-++ ### Step 1: Authentication \& Manual Connectivity Before diving into protocol configurations, verify that the basic network path and credentials are functional. * **Credential Matching:** You **must** log in to the target machine using the same **User ID and Password** that you provided in the ADC configuration to add that machine. * **Manual Access Test:** From the target machine, open File Explorer and attempt to browse to the ADC share manually: `\\\C\\ProgramData\CloudamizeAgentlessDc\HOST_SHARE` * **Identify the Error Type:** \* **Access Denied:** Usually indicates a credential mismatch, a locked account, or insufficient NTFS/Share permissions. * **Network Related Error (e.g., "Network Path Not Found"):** Usually indicates a firewall blockage, the "Client for Microsoft Networks" being disabled, or an SMB protocol mismatch. > **Note:** If you encounter either of these errors during the manual test, you must resolve them using before the ADC can successfully scan the host. ### **Step 2: Share Permissions:** 1. Navigate to `C:\ProgramData\CloudamizeAgentlessDc\HOST_SHARE`. 2. Right-click \> **Properties** \> **Sharing** tab \> **Advanced Sharing** \> **Permissions**. 3. Add **Everyone** and ensure they have appropriate access. ### **Step 3: Phase 3: SMB Protocol Alignment** If the network path is not found, there is likely an SMB version mismatch. #### **Scenario A: Enable SMBv2 on Remote Host (Best Practice)** Use these commands if the remote host is outdated but supports SMBv2. |------------------------|--------------|-----------------------------------------------------------------------------------------------------------------------------| | **OS Version** | **Action** | **PowerShell Command** | | **Win Server 2012+** | Enable SMBv2 | `Set-SmbServerConfiguration -EnableSMB2Protocol $true` | | **Win Server 2008 R2** | Enable SMBv2 | `Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters" SMB2 -Type DWORD -Value 1 -Force` | #### **Scenario B: Enable SMBv1 on ADC Machine (Legacy Support)** Use these only if the remote host is very old (e.g., Windows Server 2003) and cannot use SMBv2. * **Win Server 2012+:** `Set-SmbServerConfiguration -EnableSMB1Protocol $true` * **Win Server 2008 R2 \& Below:** `Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters" SMB1 -Type DWORD -Value 1 -Force` ### Step 4: NTLM \& Security Policies If credentials are correct but access is still denied, NTLM traffic may be restricted. 1. **On the Remote Host (Outgoing):** * Go to `Local Security Policy` \> `Local Policies` \> `Security Options`. * Set **Network Security: Restrict NTLM: Outgoing NTLM traffic to remote servers** to **Allow all**. 2. **On the ADC Machine (Incoming):** * Go to `Local Security Policy` \> `Local Policies` \> `Security Options`. * Set **Network Security: Restrict NTLM: Incoming NTLM traffic** to **Allow all** . ### Step 5: **From the ADC machine** , run the following in PowerShell: 1. `Get-WmiObject -Class Win32_OperatingSystem -ComputerName -Credential (Get-Credential)` 1. **Note**: When prompted for credentials, please ensure that you include the domain when specifying the user. 2. This command should succeed and print out some information about the remote machine. Please take a screenshot of the output and provide it to us. 2. `Invoke-WmiMethod -Class Win32_Process -Name Create -ArgumentList "cmd.exe /c echo hello" -ComputerName -Credential (Get-Credential)` If the command is executed successfully, it should print out information like the process ID and return value (which would be 0 on success, 2 would be AccessDenied). Please take a screenshot of the output and provide it to us. ### **Step 6: Review DCOM Permissions.** The user account used by the Cloudamize ADC to connect to the remote server needs specific DCOM permissions. 1. On the remote host, run `dcomcnfg` to open **Component Services**. 2. Navigate to **Computers** -\> **My Computer** , right-click, and select **Properties**. 3. Go to the **COM Security** tab. 4. Under "Access Permissions" and "Launch and Activation Permissions," ensure the account has "Remote Access" and "Remote Launch and Activation" rights. ![image-20250822-221317.png](https://support.cloudamize.com/__attachments/a_0946bfaf3f31ade0404b25c2c793a321b26b656185ef2a33733b683f754a677c/image-20250822-221317.png?cb=82dce070a5b510d2f9ba0827a93c4ac7) ### **Step 7: Review** **WMI security permissions** . a. On the remote host, run `wmimgmt.msc` b. Right-click "WMI Control" and select "Properties" c. Navigate to "Security Tab" d. Select CIMV2 and Click Security e. Ensure the account (or its group) has all the permissions (Except Special Permissions may be unchecked) ![image-20250822-221850.png](https://support.cloudamize.com/__attachments/a_5e51acd6ac2932fd24bfd91911e9800fe170903d7bad6bc879c17504fc0d02da/image-20250822-221850.png?cb=273440f47a3d2248de718feef866cdbd) It may also be helpful to check the **EventViewer** on the **target machine** for any entries related to WMI, DCOM, or logon failures. In addition, **under Microsoft-\>Windows-\>WMI-Activity**, there is an "Operational" log that can be utilised to check for errors around the execution time. The log might need to be enabled to collect events. ### **Step 8: Review Group Policy Objects (GPOs).** If you apply the manual fixes and they do not work or if they revert back, it is likely a Domain GPO overriding your changes. **Check for Overriding Policies:** 1. On the target machine, run `rsop.msc` (Resultant Set of Policy) or `gpresult /h report.html` to see which policies are actually being applied by the Domain Controller. 2. **Verify SMB Restrictions:** Ensure no GPO is disabling SMBv2 or forcing "Digitally sign communications (always)" which can interfere with older agents. 3. **Verify NTLM Restrictions:** Check `Computer Configuration > Windows Settings > Security Settings > Local Policies > Security Options`. Ensure no GPO is set to **"Deny all"** for NTLM traffic. 4. **Verify Firewall GPOs:** Ensure a Domain-level firewall policy isn't blocking **Inbound Port 445**, even if the local firewall shows it as open. ### **Step 9: Review Server Hardening.** Hardening benchmarks (like CIS or NIST) often disable legacy communication methods. Check these specific settings if the manual access test fails. 1. **SMB Packet Signing:** Hardened environments often require **SMB Packet Signing**. If the ADC and target machine have mismatched signing requirements (e.g., one requires it, the other has it disabled), the connection will drop. * *Check:* `Local Security Policy > Local Policies > Security Options > Microsoft network server: Digitally sign communications (always)`. 2. **LAN Manager Authentication Level:** If the hardening policy is set to "Send NTLMv2 response only. Refuse LM \& NTLM," it may block the ADC if it uses an older authentication handshake. * *Check:* `Local Security Policy > Local Policies > Security Options > Network security: LAN Manager authentication level`. 3. **UAC Restrictions (Remote Restrictions):** By default, Windows restricts local administrative accounts from connecting via SMB. If the target machine is being accessed via a hostname and you are **not** using the built-in "Administrator" account (but rather another account that belongs to the Administrators group), remote access will be denied due to **Remote UAC** . **Note:** Disabling Remote UAC is not recommended for security reasons. However, if it is necessary for the ADC to function, you must set the following registry entry to **1** . If the entry does not exist, you must create it: * *Fix:* Ensure the `LocalAccountTokenFilterPolicy` registry key is set to **1** if using a local admin account. ### **Step 10: Additional key instructions for the shared folder access issue:** * Go to the remote host via Remote Desktop Connection using the account provided by the customer in ADC UI. * Run Command Prompt. Don't run it as Administrator. * Run the following command * NET USE \\\\ADC_ip_address\\Cloudamize_HOST_SHARE /user:ADC_host_name\\CloudamizeAgentless "Password for the account CloudamizeAgentless" * E.g., NET USE \\\\10.0.0.10\\Cloudamize_HOST_SHARE /user:MYADC\\CloudamizeAgentless "myPassword" * Please send us the output of the command above. * To retrieve the password for the CloudamizeAgentless account, run CloudamizeRetrieval.exe as Administrator on Command Prompt in the ADC machine. The customer needs both files (CloudamizeRetrieval.exe and Utility.dll). [CloudamizeRetrieval.exe](https://support.cloudamize.com/__attachments/a_8443af1d639d9a02824fc6f722e3f516343802e4dc3a1657f5f947d04cdb8ab4/CloudamizeRetrieval.exe.md?cb=5f303c4575e54488d171cc9e99a46a1c)[Utility.dll](https://support.cloudamize.com/__attachments/a_7ed82d294da7e363736835ad53409d5b68e608049a8495cfaac89466bf848a1c/Utility.dll.md?cb=d8d46fa6565fb476fe79caa9b755570d) If the issue persists, please capture a screenshot of the error outputs requested and collect the `log_backup.txt` file from the following directory on the Cloudamize Agentless DC: `C:\Program Files (x86)\CloudamizeAgentlessDc\log_backup.txt` Please attach both the screenshot and the log file in an email to [**helpdesk@cloudamize.com**](mailto:helpdesk@cloudamize.com) for further investigation. If you have any queries, please get in touch with the helpdesk via our Helpdesk Portal or by email at [helpdesk@cloudamize.com](mailto:helpdesk@cloudamize.com). --- language: "en" --- # Add and Configure Hosts ## **Overview** This guide will walk you through how to use the Cloudamize Agentless Data Collector, including how to add and configure hosts, change credentials for a set of machines, and view any error messages pertaining to your infrastructure. Please contact [helpdesk@cloudamize.com](mailto:helpdesk@cloudamize.com) if you have any questions. ### **Launching the UI** First, you will need to open the Cloudamize Agentless Data Collector. This can be done from the Windows taskbar. ## Add and Configure Hosts ![image-20230522-051053.png](https://support.cloudamize.com/__attachments/a_3b44da4e8dc9f071725e19128fb0f7c9f1c95632e2a5d9691501da0b7452a896/image-20230522-051053.png?cb=f81374b4d411851897d07276ae2b9e26) Follow the instructions contained in the above image to open the collector. Once you have clicked Open, you will see the UI. ![image-20240605-010546.png](https://support.cloudamize.com/__attachments/a_e2e46728eaa51d0759327406877db8876b01c7780b8f3bf49e688dfcff0daaf4/image-20240605-010546.png?cb=2a36a4d4724d8cb393aad545ef785603) ### **Adding Hosts** ### Adding a Remote Host You can add a Windows, Linux, or NetApp host using the 'Add Host' menu as follows- ![image-20240605-010647.png](https://support.cloudamize.com/__attachments/a_029a5839127265d873c005cb2f1e2a0cca74ec2473df19428a98eddd844111f6/image-20240605-010647.png?cb=804e7d502722f45ceac868e3b26de240) You will now need to add the hosts that you would like to monitor. You may enter IP addresses individually (10.1.1.2), as a range (10.1.1.2-50), or as a subnet (10.1.4.0/24). You may use any combination of these formats separated by commas. Once the IP addresses have been entered, click Add Host(s). ![image-20230522-145701.png](https://support.cloudamize.com/__attachments/a_c6a0acc4ddf9b7746b9db126d6e6de457de175c743e828419e6cadd52ff7e110/image-20230522-145701.png?cb=1d8895820d6c45285c777cc6da822581) The screenshot above shows that two Windows hosts have been added successfully. This will open another window that will check the WMI connection to each host and report Success or Failure. A summary will be printed at the bottom displaying the number of hosts that succeeded, failed, and were not checked. Hosts will not be checked if Cancel is clicked during the checking process. ### Instructions for adding a Linux host. A Linux host uses **SSH** and may use either a password or an **SSH Key**. We recommend providing the key in PuTTY's ppk format; however, PEM and OpenSSH-style keys will attempt to be converted automatically. If an authentication error occurs, you should manually convert the key to a ppk format and try again. Passwords are stored encrypted via a local application encryption key, whereas SSH keys are protected only by Windows ACLs. **Step 1:** Click **Add Host** , and then select **Add Linux Host** , as shown in the screenshot below. The **Add Linux Host** window opens, where you can enter the required host details. ![Screenshot 2026-08-21 at 2.57.40 PM-20260821-092748.png](https://support.cloudamize.com/__attachments/a_dfc1aae3241dd6eb1475639f3b74689d3b3237f1562f36fb8125acf13f576c60/Screenshot%202026-08-21%20at%202.57.40%E2%80%AFPM-20260821-092748.png?cb=a306c8ebee0a9b2652d133bdf60c087b) **Step 2** : Enter the **IP Address** of the host and the corresponding **Account Name** . Under **SSH Key** , click **Browse** and select the required SSH key. Once all the required details are entered, click **Add Host**. The host will be added successfully and displayed in the host list, as shown in the screenshot below. **Note:** Ensure that the SSH key is saved on the machine where the **ADC (Agentless Data Collector)** is installed. ![Screenshot 2026-08-21 at 3.00.53 PM-20260821-093059.png](https://support.cloudamize.com/__attachments/a_04802073cd1e9da528b8f1ea0b27d64ac12772044217903cdaa8978f24208451/Screenshot%202026-08-21%20at%203.00.53%E2%80%AFPM-20260821-093059.png?cb=93316d71d74c755fac40bfd45a1e891e) ![Screenshot 2026-08-21 at 3.07.04 PM-20260821-093806.png](https://support.cloudamize.com/__attachments/a_12135bbb78118e10eb0ef52d821ad19d2bff9383b2f2dcdf3b04384aced6e3c1/Screenshot%202026-08-21%20at%203.07.04%E2%80%AFPM-20260821-093806.png?cb=328c3604ac0edee9903f42197f08597b) ![Screenshot 2026-08-21 at 3.09.22 PM-20260821-093938.png](https://support.cloudamize.com/__attachments/a_32edd7ed6a95b0ed4dc3dc838283d30b73764e4856916f08dd300f797c5088e6/Screenshot%202026-08-21%20at%203.09.22%E2%80%AFPM-20260821-093938.png?cb=f6e7a1a65bb22940a0a3467c4d68dc95) #### Bulk Onboarding for Linux Hosts (Multi-Server Batch Addition) You can onboard multiple target Linux servers simultaneously in a single operation, provided they share identical SSH authentication credentials. * **Multi-Server Batch Addition:** Multiple Linux targets utilizing the same SSH key pair (or standard root/sudo credentials) can be uploaded and configured together during a single Agentless Data Collector (ADC) onboarding workflow. ![image-20260825-084737.png](https://support.cloudamize.com/__attachments/a_8d22a579759bfeca7d9b6a3fbafa3534dd59b9d4d8e017ded0c69a06ac3ca7a0/image-20260825-084737.png?cb=6cade15965beb5f87fdc15c51d1f46f8) IMPORTANT NOTE ON SSH KEYS: If your target Linux servers utilize different SSH keys, they must be added individually in separate operations. The Cloudamize ADC interface allows you to browse and select only one SSH key file per onboarding operation. Multiple distinct SSH key files cannot be uploaded simultaneously in a single batch. ### Instructions for adding a NetApp host. ![image-20240605-011008.png](https://support.cloudamize.com/__attachments/a_87c355151809e8985bd8a14d8baa8acf5c4e01b98ed823b32c02d6fd012f94b9/image-20240605-011008.png?cb=e5b8de2e53f0f4a8ce5cc47a80d1d983) ### Adding and updating credentials in bulk When there are a lot of hosts to add, you can add credentials in bulk by uploading a .csv file containing the following information in this order: * IP Address * OS Type * Account Name * Password ![image-20240605-011441.png](https://support.cloudamize.com/__attachments/a_fbc0e502090a3a79f414340ab712b3982e6598cd6963f50481021b1fac9efc12/image-20240605-011441.png?cb=9cef05364831ee9a5cb2403ec31e0f25) If you are having any issues adding hosts, please send the following log file to [helpdesk@cloudamize.com](mailto:helpdesk@cloudamize.com) with a description of the errors as reported in the UI: * C:\\Program Files (x86)\\CloudamizeAgentlessDC\\log_backup.txt **Example csv file**: [Sample file.csv](https://support.cloudamize.com/__attachments/a_f18f17ccd417b5a1d8d7b704dd9a10ca09933c2d652874fd19091e6b60297c15/Sample%2520file.csv.md?cb=e759321c7cc75d1e1366e248caf61550) ### **View Error Messages** If the WMI connection fails for any reason, the Status column of the UI will display "Error". You can click on the Show error button to the right of Status to learn more. ![image-20220112-191415.png](https://support.cloudamize.com/__attachments/a_4ce537cc9549ab20cdedc6ad4fc72353d99453661f47174629ee607c6227360d/image-20220112-191415.png?cb=2dde791a0090f6673f33d9774860dcd9) Another window will open with more information about the error. Please refer to [this page](https://msdn.microsoft.com/en-us/library/aa822854(v=vs.85).aspx) for troubleshooting WMI connection issues. You can review the information in the pop-up window and attempt to fix the error or contact [helpdesk@cloudamize.com](mailto:helpdesk@cloudamize.com) for assistance. ### **Change Access Credentials** You can edit the credentials of a host by clicking the checkbox on the left of the row and selecting Change Credentials at the bottom of the UI. ![image-20220112-191421.png](https://support.cloudamize.com/__attachments/a_30abe1396c8f825019cef12eae5c72be93fcdb35ae32d16ba60824a1468c42d8/image-20220112-191421.png?cb=6b50a3f2d7d32402abbe3f3aa2855318) The changes made to the credentials will now be displayed in the UI. If the Change Credentials process is running, you will not be able to close the window until the process is stopped by the user canceling the process or the process completes on its own. ![image-20220811-182320.png](https://support.cloudamize.com/__attachments/a_9b5d6eab41ef6367de4d41db1f5ded4e2344856544280766d028adf180e34e35/image-20220811-182320.png?cb=d8647de6bdae4b0e6f3b23cd3502e1ff) You can retry credentials without having to open the **Change Credentials** window ![image-20220811-182008.png](https://support.cloudamize.com/__attachments/a_f41d6515c8bb2b56e355bcd830587b70469fa9a86b116b75cc631542ab61008d/image-20220811-182008.png?cb=104f5623fd42b85264e38ada3f425196) ### **Deleting a Remote Host** ![image-20230522-152327.png](https://support.cloudamize.com/__attachments/a_13e481046235627456980a22f76580b7376cc857bd3203e64f59f36cebecf132/image-20230522-152327.png?cb=198dbeb99a8f184b9cb6c6db3c377ceb) To delete one or more remote hosts, select the host(s), click the Delete button, and click the OK button on the confirmation pop-up window. ## Parameter Setup ![image-20230522-150902.png](https://support.cloudamize.com/__attachments/a_3e4f69f427cd0d0b803d25e21b753a2045fb84624e9606ffc6d29e3869586742/image-20230522-150902.png?cb=751e55369be6534f13093ae2262f57bd) You can set up the max. number of remote hosts. The default value is 500, and we suggest 500. If you want to increase it, computer resources need to be increased too (e.g., number of hardware threads). ## Error Message ### Adding Hosts More Than Limit The default limit of adding hosts per Agentless Data collector is 500 to protect ADC well in terms of resources, and if you try to add hosts more than the limit (e.g., 500 hosts), the following error message will appear. ![image-20220728-194859.png](https://support.cloudamize.com/__attachments/a_9f38c735d79ff07ce095119df3d0d19c325cafcd907faf968ca50aaf53d4b3a8/image-20220728-194859.png?cb=b7c9f7caf605beff30b07d737654d19e) If you have any queries, please get in touch with the helpdesk via our Helpdesk Portal or by email at [helpdesk@cloudamize.com](mailto:helpdesk@cloudamize.com). --- language: "en" --- # Advance SQL Error - Installing the NuGet package provider ## **Overview** When the Cloudamize Windows Agent or Agentless Data Collector (ADC) attempts to collect **Advanced SQL Data** , it may need to install the `SqlServer` PowerShell module. This process requires the **NuGet package provider** . If the system cannot reach the required Microsoft repositories, the following error will appear in the **MS SQL Data Collection Status** column: `Exit code = 1. Output: Installing the NuGet package provider. WARNING: Unable to download from URL 'https://go.microsoft.com/fwlink/?LinkID ~~~ Check your internet connection.` ### **Root Cause** The collector is unable to download the NuGet provider because the connection to Microsoft's package delivery endpoints is blocked by a firewall, proxy, or lack of internet access on the target machine. ## **Troubleshooting Steps option 1:** ### **Firewall \& Proxy Whitelisting** Ensure the target server (or the ADC machine) has outbound access to the following URLs: * `https://go.microsoft.com` * `https://onegetcdn.azureedge.net` **To verify the second URL specifically:** Run the following PowerShell command with the verbose flag to see exactly where the connection is failing: Install-PackageProvider -Name 'NuGet' -MinimumVersion '2.8.5' -Scope CurrentUser -Verbose ### **Manual Installation via PowerShell** If the automatic installation fails, you can manually trigger the installation while ensuring the correct security protocols (TLS 1.2) are active. #### **Scenario A: Direct Internet Connection (No Proxy)** Run this command in an elevated PowerShell window: [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12; Install-PackageProvider -Name 'NuGet' -MinimumVersion '2.8.5' -Scope CurrentUser -Force -ErrorAction Stop; #### **Scenario B: Behind a Proxy Server** If your environment uses a proxy, you must define it within the session: [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12; # Set your proxy details below $proxyUrl = "http://your_proxy.com:8443" [System.Net.WebRequest]::DefaultWebProxy = New-Object System.Net.WebProxy($proxyUrl, $true); [System.Net.WebRequest]::DefaultWebProxy.Credentials = [System.Net.CredentialCache]::DefaultNetworkCredentials; # Install using the proxy flag Install-PackageProvider -Name 'NuGet' -MinimumVersion '2.8.5' -Proxy $proxyUrl -Scope CurrentUser -Force -ErrorAction Stop; *** ** * ** *** ## Troubleshooting Steps Option 2 If standard troubleshooting (TLS settings/Proxy) does not work, you must manually sideload the NuGet provider DLL into the Windows file system. ### **Manual "Offline" Installation of NuGet Provider** Follow these steps if your security policy blocks the automated SSL handshake or if you receive a "No match found" error when trying to point to a local `.exe` or `.zip` file. #### **Step 1: Download the Provider DLL** 1. On a machine with internet access, download the official Microsoft NuGet provider DLL: [Microsoft.PackageManagement.NuGetProvider-2.8.5.208.dll](https://www.google.com/search?q=https://onegetcdn.azureedge.net/provision/microsoft.packagemanagement.nugetprovider-2.8.5.208.dll) 2. Transfer this `.dll` file to the target server using your approved file transfer method. #### **Step 2: Create the Required Directory Structure** PowerShell requires the provider to exist in a specific versioned folder hierarchy. You must create this manually: 1. Open **File Explorer** as an Administrator. 2. Navigate to (or create) the following path: `C:\Program Files\PackageManagement\ProviderAssemblies\` 3. Inside **ProviderAssemblies** , create a subfolder named `nuget`. 4. Inside **nuget** , create another subfolder named `2.8.5.208`. 5. **Final Path:** `C:\Program Files\PackageManagement\ProviderAssemblies\nuget\2.8.5.208\` #### **Step 3: Place, Rename, and Unblock the File** 1. Move the downloaded `.dll` into the `2.8.5.208` folder. 2. **Rename** the file to exactly: `Microsoft.PackageManagement.NuGetProvider.dll` 3. **Unblock the File:** Right-click the `.dll` file \> **Properties** \> Check the **Unblock** box at the bottom \> **OK**. *(Note: If you skip this, Windows security will prevent PowerShell from loading the provider.)* #### **Step 4: Verify the Installation** Open a new PowerShell window as an Administrator and run: Get-PackageProvider -Name NuGet If successful, the NuGet provider will be listed with version **2.8.5.208**. ### **Step 5: Install the SQL Server Module (Offline Method)** Now that the NuGet "engine" is installed, you can install the `SqlServer` module from a local directory if the server remains offline: 1. Place your downloaded `SqlServer.nupkg` into a folder (e.g., `C:\LocalRepo`). 2. Register the folder as a trusted source: Register-PSRepository -Name LocalSource -SourceLocation "C:\LocalRepo" -InstallationPolicy Trusted 3. Install the module: Install-Module -Name "SqlServer" -Repository LocalSource If the issue persists, please capture a screenshot of the error output and collect the `log_backup.txt` file from the directory: For ADC: `C:\Program Files (x86)\CloudamizeAgentlessDc\log_backup.txt` For Agent: `C:\Program Files (x86)\Cloudamize\log_backup.txt` Please attach both the screenshot and the log file in an email to [++**helpdesk@cloudamize.com**++](mailto:helpdesk@cloudamize.com) for further investigation. If you have any queries, please get in touch with the helpdesk via our [++Helpdesk Portal++](https://cloudreach-software.atlassian.net/servicedesk/customer/portal/9) or by email at [++helpdesk@cloudamize.com++](mailto:helpdesk@cloudamize.com). --- language: "en" --- # Agent (Recommended) * [Linux](https://support.cloudamize.com/kb/linux.md) * [Windows](https://support.cloudamize.com/kb/windows.md) * [Mass Agent Deployment](https://support.cloudamize.com/kb/mass-agent-deployment.md) --- language: "en" --- # Agent Installation Prerequisites ## **Windows Installation Prerequisites for Agent** You can download the Windows installer file in your assessment from the **Agent Setup \> Assess** tab. You can download the MSI file or copy the command to be run from an elevated command prompt. The command pictured below shows options for a proxy server with authentication required. These options are also available in the MSI file but not required to install the agent. * Access to our servers at **am.cloudamize.com for US infrastructure, am-de.cloudamize.com for EU infrastructure, or** [**am-ae.cloudamize.com**](http://am-ae.cloudamize.com/)**for UAE infrastructure**over port 443 directly or through a corporate proxy. * If your system locally caches DNS resolution, you may need to resolve [am.cloudamize.com](http://am.cloudamize.com/) to **35.171.170.26** or [am-de.cloudamize.com](http://am-de.cloudamize.com/) to **18.194.12.63**to allow egress traffic. This feature is not currently available for our UAE region. * **One of the following OSes:** * Windows Server 2022 * Windows Server 2019 * Windows Server 2016 * Windows Server 2012 R2 * Windows Server 2008 R2 and Server 2003 R2 are no longer officially supported, but if sufficiently up to date may be compatible. * .NET Framework version 3.5 or above * 2 GB persistent storage * Requirement for Agent to Collect SQL Data from a remote machine(If SQL data is required) * The Agent will collect the Basic SQL data as no PowerShell script is utilized for this. * PowerShell 5.1 is required to collect additional SQL Server data on the remote machine. The Agent will also install the NuGet packet and SqlServer PowerShell module to collect the Advanced SQL details, below are the links that need to be whitelisted to allow the Agent to download the packages. NuGet packet installation: [https://go.microsoft.com](https://go.microsoft.com/fwlink/?LinkID=627338&clcid=0x409%27) and [++https://onegetcdn.azureedge.net++](https://onegetcdn.azureedge.net/) SqlServer PowerShell module installation: [https://www.powershellgallery.com](https://www.powershellgallery.com/api/v2/package/SqlServer/22.3.0) and [https://psg-prod-eastus.azureedge.net](https://psg-prod-eastus.azureedge.net/packages/sqlserver.22.3.0.nupkg) * .NET Framework 3.5 is the minimum requirement on the remote machine. Server Core for each of the above OSs is also supported The ***Cloudamize windows Machine Agent*** requires 2% of available CPU and 3% of memory while running. If the agent takes more than the allotted CPU and memory the watchdog process will stop the agent process and begin again once it's able to run below the thresholds. Windows installation and troubleshooting Procedures can be found [here](https://support.cloudamize.com/kb/windows.md). ## **Linux Installation Prerequisites for Agent** You can access the Linux installer command and customer key in your assessment from the **Agent Setup \> Assess** tab. The command pictured below displays options for a proxy server that requires authentication. These options are not required and can be installed without a corporate proxy, provided port 443 is open to our data collection server. * The Install script requires ***wget*** to retrieve content and ***curl*** to test/verify access to our data collection servers at **am.cloudamize.com for US infrastructure, am-de.cloudamize.com for EU infrastructure, or** [**am-ae.cloudamize.com**](http://am-ae.cloudamize.com/)**for UAE infrastructure** over port 443, either directly or through a corporate proxy. * If your system locally caches DNS resolution, you may need to resolve [am.cloudamize.com](http://am.cloudamize.com/) to **35.171.170.26** or [am-de.cloudamize.com](http://am-de.cloudamize.com/) to **18.194.12.63**to allow egress traffic. This feature is not currently available for our UAE region. * Root and/or wheel access * **One of the following OSes:** * Red Hat Enterprise Linux Server release 7.0 or higher * Oracle Linux 6.5 or higher * Ubuntu 16.04 or higher * CentOS release 7 or higher * Debian GNU/Linux 8.0 or higher * Amazon Linux AMI release 2013.03 or higher * Fedora release 12 or higher * Suse Linux 11 or higher * A [supported](https://openssl-library.org/policies/releasestrat/) version of OpenSSL * The Cloudamize Agent can be installed on the RHEL 7.0 or higher systems that have **OpenSSL version 1.0.2k** and is capable of handling TLS 1.2 secure communication protocol. * Root and/or wheel access * 350 MB persistent storage * The Install script requires *wget* to retrieve content, and *curl* to test/verify access to our data collection servers (see above) over port 443, either directly or through a corporate proxy The ***Cloudamize Linux Agent*** requires 3% of available CPU and 5% of memory while running. If the agent takes more than the allotted CPU and memory, the watchdog process will stop the agent process and begin again once it's able to run below the thresholds. Linux installation and troubleshooting Procedures can be found [here](https://support.cloudamize.com/kb/linux.md). ## **Supported Chipsets for all installation types** * Intel Xeon * AMD Opteron * Pentium 4 * Pentium D * Pentium M * Some Intel Core 2 \*\* \*\*Best effort will be given to support these chipsets ### **Note:** The **Cloudamize Windows and Linux Agents** are designed exclusively to support the **x64 machine architecture** . * This means the agents **do not support** other architectures, including **AArch64 (ARM64)** , **ARM32**, If you have any queries, please get in touch with the helpdesk via our [++Helpdesk Portal++](https://cloudreach-software.atlassian.net/servicedesk/customer/portal/9) or by email at [++helpdesk@cloudamize.com++](mailto:helpdesk@cloudamize.com). --- language: "en" --- # Agentic AI * [📘 Cloudamize MCP Server -- Admin \& Setup Guide](https://support.cloudamize.com/kb/cloudamize-mcp-server-admin-setup-guide.md) * [📘 Cloudamize MCP Server End User \& Integration Guide](https://support.cloudamize.com/kb/cloudamize-mcp-server-end-user-user-integration-gu.md) * [Transform Cloudamize Ingestion Agent](https://support.cloudamize.com/kb/Transform-Cloudamize-Ingestion-Agent.md) --- language: "en" --- # Agentless * [Agentless Setup Instructions](https://support.cloudamize.com/kb/setup-instructions-and-troubleshooting.md) * [Agentless Overview](https://support.cloudamize.com/kb/agentless-overview.md) * [Add and Configure Hosts](https://support.cloudamize.com/kb/add-and-configure-hosts.md) * [Using Sudo to Grant Privileges For Linux Servers](https://support.cloudamize.com/kb/using-sudo-to-grant-privileges-for-linux-servers.md) * [Agentless Troubleshooting](https://support.cloudamize.com/kb/agentless-troubleshooting.md) --- language: "en" --- # Agentless Installation Prerequisites ## **Windows Installation Prerequisites for Agentless Data Collector** The table below lists the relevant ports for machine discovery and communication to the Cloudamize servers. Please note the following rules for each class of machine: * Machine with Cloudamize Agentless Data Collector installed * TCP port **445 is** open **inbound** * TCP ports **443** and a proxy server port if a proxy is being used (e.g.,**8080** , **80** ) open **outbound** to our servers at **am.cloudamize.com (for US infrastructure), am-de.cloudamize.com (for EU infrastructure), or am-ae.cloudamize.com (for UAE infrastructure).** * If your system locally caches DNS resolution, you may need to resolve am.cloudamize.com to **35.171.170.26** or am-de.cloudamize.com to **18.194.12.63**to allow egress traffic. This feature is not currently available for our UAE region. * Each Windows endpoint * TCP ports **135** and the dynamic RPC port ranges open **inbound**, appropriate for your OS versions: * Windows Server 2008 and later: TCP ports **49152 to 65535 open inbound** * Windows Server 2003 and earlier: TCP ports **1025 to 5000 open inbound** * TCP port **445** open **outbound**to the machine with the Agentless Data Collector installed * Each Linux endpoint * TCP port **22** open **inbound** |--------------|-------------|------------------------------------------------------------| | **Protocol** | **Port** | **Usage** | | TCP | 22 | SSH to access Linux servers | | TCP | 135 | Windows RPC | | TCP | 445 | Microsoft-DS Active Directory and SMB, Windows shares | | TCP | 1025-5000 | RPC dynamic port range for Windows Server 2003 and earlier | | TCP | 49152-65535 | RPC dynamic port range for Windows Server 2008 and later | | TCP | 443 | SSL to communicate with the Cloudamize servers | ***Fig. 2 Ports relevant to the Cloudamize Agentless Data Collector*** ## **Authentication requirements to machines from an Agentless Data Collector** * Windows machines require an account in the Administrators group (Domain Admin Account) * Linux machines require Root or Wheel access * Linux machines cannot have requiretty = true in sudo * **Agentless Data Collector connects to Linux servers via SSH using password authentication or SSH key-based (public key) authentication**. Ensure that the required SSH private key is available on the machine where the Agentless Data Collector is installed and that the corresponding public key is configured on the target Linux machine. * All other Windows and Linux system requirements apply ## **Minimum System Requirements for Agentless Installer** The Cloudamize Agentless Data Collector will need to be installed on a physical or virtual Windows machine meeting the following minimum requirements: * Dedicated 64-bit Windows Server 2012 R2 or higher * .NET Framework version 4.0 * 8 CPU cores * 16 GB RAM * 5 GB persistent storage * Requirement for Agentless Data Collector to Collect SQL Data from a remote machine(If SQL data is required) * PowerShell 2.0 is required to collect basic SQL Server data on the remote machine. * PowerShell 5.1 is required to collect additional SQL Server data on the remote machine. The Agentless will also install the NuGet packet and SqlServer PowerShell module to collect the Advanced SQL details, below are the links that need to be whitelisted to allow the Agent to download the packages. NuGet packet installation: [https://go.microsoft.com](https://go.microsoft.com/fwlink/?LinkID=627338&clcid=0x409%27) and [++https://onegetcdn.azureedge.net++](https://onegetcdn.azureedge.net/) SqlServer PowerShell module installation: [https://www.powershellgallery.com](https://www.powershellgallery.com/api/v2/package/SqlServer/22.3.0) and [https://psg-prod-eastus.azureedge.net](https://psg-prod-eastus.azureedge.net/packages/sqlserver.22.3.0.nupkg) * .NET Framework 3.5 is the minimum requirement on the remote machine. * For additional data collection, the account used to add the nodes to the ADC UI should have permission to access MS SQL instances on the remote host. If not, add the account to Security/Logins in SQL Server Management Studio on the remote host. If you have any queries, please get in touch with the helpdesk via our [++Helpdesk Portal++](https://cloudreach-software.atlassian.net/servicedesk/customer/portal/9) or by email at [++helpdesk@cloudamize.com++](mailto:helpdesk@cloudamize.com). --- language: "en" --- # Agentless Overview ## **General Information** The Cloudamize Agentless Data Collector can be used to discover and assess physical and virtual machines without installing software agents on each machine throughout your infrastructure. The collector is deployed on a physical Windows server or Windows virtual machine and can be used to discover and assess both Windows and Linux machines. Each collector can be used to monitor up to 500 machines. Additional collectors can be installed on additional machines to monitor larger infrastructures. Example: 1-500 machines = 1 collector 501-1000 machines = 2 collectors 1001-1500 machines = 3 collectors The Cloudamize Agentless Data Collector uses SSH to discover and communicate with Linux machines on the subnet, and WMI/RPC to discover and communicate with Windows machines. The collector then sends the TLS v1.3 encrypted data to the Cloudamize servers for processing. MFA (Multi-Factor Authentication) is not supported for connections to Windows or Linux nodes from the Agentless Data Collector. ## Agent-Based VS Agentless There are advantages and disadvantages to utilizing the Cloudamize Agentless Data Collector as opposed to installing software agents throughout the infrastructure. One obvious advantage will be in the case of high-security compliant infrastructures, which are not permitted to install software and communicate out to remote servers from each machine in the infrastructure. The Cloudamize Agentless Data Collector can be installed on one machine in cases like this, and the entire infrastructure being assessed will send that data to this one machine over WMI (Windows) and SSH (Linux). All of this communication happens on the internal network, and data will only leave the network from the machine with the collector installed. The table below highlights the feature comparison between agent-based and agentless data collection. ![image-20220112-190338.png](https://support.cloudamize.com/__attachments/a_b19812493342972a07b7399240e27404d5c57724d52de25e241cd4ae2e32dc87/image-20220112-190338.png?cb=4672f7881f1a94cec9466f015969f989) *Note: The details on the Basic and Advanced SQL Data collected are available* [*here*](https://support.cloudamize.com/kb/basic-and-advanced-ms-sql-collected-by-agent-based)*.* ### Disadvantages of agentless Without having software agents installed on each machine, there are also disadvantages in a few areas. The following table shows a set of metrics and the impact that taking an agentless approach will have. |-------------------------------|----------------------------------------------------------------------------------------------------------| | **Metric** | **Impact** | | Short-lived connections | If a connection is short-lived, it is not captured, and that may result in missed inter-connectivity | | Lower performance resolutions | The monitoring window is every 5 minutes rather than every 30 seconds. Possible to miss short-term peaks | | Performance Throttling | Agentless monitoring does not have a performance controlling mechanism on the monitored host | ### Supported MS SQL data collected by Agent-Based and Agentless | **Data** | **Agent** | **Agentless** | |-------------------------------------------------------------------------------------------------------------------------------|-----------|---------------| | MS SQL Server instance id (e.g. MSSQL11.MSSQLSERVER) | ✔ | ✔ | | MS SQL Server instance name (e.g. MSSQLSERVER) | ✔ | ✔ | | Server edition (e.g. Standard Edition) | ✔ | ✔ | | Server edition type (e.g. Standard Edition) | ✔ | ✔ | | Server version (e.g. 9.4.5000.00) | ✔ | ✔ | | Server patch level | ✔ | ✔ | | Server service pack (e.g. 4) | ✔ | ✔ | | SQL Server binary directory with full path (e.g. C:\\Program Files\\Microsoft SQL Server\\MSSQL12.MSSQLSERVER\\MSSQL\\Binn) | ✔ | ✔ | | Information for each database (e.g. "database name (e.g. LicensingService), database total size in MB (e.g. 40)) | ✔ | ✔ | | Database file location (e.g. C:\\Program Files\\Microsoft SQL Server\\MSSQL12.MSSQLSERVER\\MSSQL\\DATA\\LicensingService.mdf) | ✔ | ✔ | | Active or passive in clustered SQL servers | ✔ | ✔ | | SQL Server data path (e.g., C:\\Program Files\\Microsoft SQL Server\\MSSQL12.MSSQLSERVER\\MSSQL\\DATA) | ✔ | ✔ | | Error log file with full path, e.g., C:\\Program Files\\Microsoft SQL Server\\MSSQL12.MSSQLSERVER\\MSSQL\\Log\\ERRORLOG) | ✔ | ✔ | | Instance SQL Linked Servers | ✔ | ✔ | | Cluster name | ✔ | ✔ | | Cluster state | ✔ | ✔ | | Feature list | ✔ | ✔ | | SQL Server product information | ✔ | ✔ | | SQL Server license info | ✔ | ✔ | | Instance SQL Version | ✔ | ✔ | | Instance SQL Version Number | ✔ | ✔ | | Instance SQL Edition | ✔ | ✔ | | Instance SQL in a Failover Cluster is clustered | ✔ | ✔ | | Instance SQL is HA-DR | ✔ | ✔ | | Instance SQL Cluster Name | ✔ | ✔ | | Instance SQL Quorum Type | ✔ | ✔ | | Instance SQL Availability Group | ✔ | ✔ | | Instance Is the SQL Availability Group Primary | ✔ | ✔ | | Instance SQL Availability Group Primary | ✔ | ✔ | | Instance SQL Availability Group Replicas | ✔ | ✔ | | Instance SQL Availability Group Role | ✔ | ✔ | | Instance Is a SQL Availability Group Readable Secondary | ✔ | ✔ | | Instance SQL Availability Group Using Synchronous Replication | ✔ | ✔ | | Instance SQL Availability Group Failover Mode | ✔ | ✔ | | Instance SQL FileStream Status | ✔ | ✔ | | Instance SQL PolyBase Status | ✔ | ✔ | | Instance SQL FullText Status | ✔ | ✔ | | Instance SQL PerfMonMode | ✔ | ✔ | | Instance Lic SQL By | ✔ | ✔ | | Instance SQL Collation | ✔ | ✔ | | Instance SQL Max Server Mem in MB | ✔ | ✔ | | Instance SQL XP Cmd Shell Status | ✔ | ✔ | | Instance SQL CLR Status | ✔ | ✔ | | Instance SQL DB Count | ✔ | ✔ | | Instance SQL DB Encryption Present | ✔ | ✔ | | Instance SQL DB Mirroring Present | ✔ | ✔ | | Instance SQL DB Replication Present | ✔ | ✔ | | Instance SQL Total DB Size MB | ✔ | ✔ | If you have any queries, please get in touch with the helpdesk via our Helpdesk Portal or by email at [helpdesk@cloudamize.com](mailto:helpdesk@cloudamize.com). --- language: "en" --- # Agentless Troubleshooting * [Windows Agentless Troubleshooting](https://support.cloudamize.com/kb/windows-agentless-troubleshooting.md) * [Linux Agentless Troubleshooting](https://support.cloudamize.com/kb/linux-agentless-troubleshooting.md) --- language: "en" --- # AI Augmented wave-group ## Overview The AI Move Group mechanism significantly advances large-scale cloud migration planning. It analyzes extensive dependency graphs to automatically cluster machines into logical move groups. By optimizing these groups based on interdependencies and size constraints, the AI generates sequential Migration Waves, transforming complex server lists into structured, manageable units for execution. This process streamlines migration efforts, reduces risk, and speeds up time-to-cloud by eliminating manual, server-by-server planning. AI Move Groups uses a combination of * Graph cleaning and clustering. * Deterministic community detection. * AI-based reasoning for migration prioritization. ### AI Move Group Strategic Clustering Modern cloud migration requires careful planning to minimize downtime and risk. Moving individual servers is inefficient when dependencies exist between them. The AI Move Group addresses this challenge by converting chaotic server lists into logical, manageable migration units. Its primary function is to balance the size and quality of migration clusters, ensuring efficiency and generating optimized Migration Waves to enhance the success of large-scale environment shifts. #### **Key Principles of AI Clustering** * **Inefficiency of Single Servers:** Migration planning is inefficient for single servers because one machine is often better grouped with related machines to streamline the process. * **Optimal Clustering Goal:** The AI Move Group works to maximize the number of clusters that fall within an optimal size range. * **Avoiding Large Clusters:** The strategy is designed to prevent overly large clusters, which are difficult to manage and schedule, thus increasing migration risk. * **Core Mechanism:** The grouping mechanism dynamically balances the goal of maximizing optimal-sized clusters with maintaining high cluster quality (which is based on the strength of machine interdependency). * **Balancing Act \& Wave Output:** The primary objective is to balance the number of clusters and cluster quality to create manageable, logically grouped units. These resulting groups are the Migration Waves that minimize risk and accelerate the migration process. #### **Auto-Grouping 2.0 Enhancements** Cloudamize has enhanced its AI-augmented auto-grouping capabilities to make server grouping and wave planning more interactive, transparent, scalable, and easier to manage. #### Improved Visualizations Auto-grouping visualizations are now more interactive and provide deeper visibility into server communication relationships. Enhancements include: * Visibility into intra-group machine connectivity, enabling users to identify all machines connected within a target move group. * Interactive grouping views for easier exploration and analysis. ![Screenshot 2026-05-14 at 3.54.40 PM-20260514-102446.png](https://support.cloudamize.com/__attachments/a_b1a784e2a93ff4b4d62738fc409118f1cc31597e91e714b7dcc3d313aa444e1d/Screenshot%202026-05-14%20at%203.54.40%E2%80%AFPM-20260514-102446.png?cb=ae825f1c519b1db3a6636c7b4689a19a) * Rich contextual details displayed in the side panel when selecting servers or communication links. * An **Out of Scope Peer (No Agent Communications)** toggle that allows users to show or hide servers without agent-based communication, reducing visual clutter during analysis. ![Screenshot 2026-05-14 at 4.00.37 PM-20260514-103134.png](https://support.cloudamize.com/__attachments/a_c7636b94308e8b534b2aa80208059922553e027c661f8d5bb236df15501ecd3f/Screenshot%202026-05-14%20at%204.00.37%E2%80%AFPM-20260514-103134.png?cb=b17870af6ca2d3c7ea2676bd2fe18a75) ![Screenshot 2026-05-14 at 4.02.58 PM-20260514-103304.png](https://support.cloudamize.com/__attachments/a_eed9506533e5131ff57cb1a3b32007533d4e2365f7914ece53437b39646d11cd/Screenshot%202026-05-14%20at%204.02.58%E2%80%AFPM-20260514-103304.png?cb=4588c0f7e0d3674a90c958bad227f90b) #### Connection Density, Details, and Server Insights Cloudamize now provides deeper visibility into communication relationships and server dependencies. Enhancements include: * Source-to-target process-level communication details. * A **Times Seen** connection density metric that shows how frequently relationships occur between servers. * Availability of connection insights across both graphical visualization and table views. * Detailed server and dependency insights displayed in the right-side panel when selecting nodes or communication links. ![Screenshot 2026-05-14 at 4.13.18 PM-20260514-104416.png](https://support.cloudamize.com/__attachments/a_bf46e7c72617b782864208d9260637de1a3c70516e420f35bd12c9a8ea215bf0/Screenshot%202026-05-14%20at%204.13.18%E2%80%AFPM-20260514-104416.png?cb=247610505448eb029135ab4320f13d7d) #### Export Capabilities Users can now export reports for: * Cloudamize AI-generated recommended groups * Custom wave groupings created by users or partners ![Screenshot 2026-05-14 at 4.30.04 PM-20260514-110044.png](https://support.cloudamize.com/__attachments/a_e6e165ea270871a8a1e0cb9b09b788345e9f3f48c9a2d998c23a22e31ff69e02/Screenshot%202026-05-14%20at%204.30.04%E2%80%AFPM-20260514-110044.png?cb=28aafeb0c5361224dd5a6194ecae7add) ![Screenshot 2026-05-14 at 4.31.17 PM-20260514-110200.png](https://support.cloudamize.com/__attachments/a_fe033c8653eee49032f957cb8a90be7e7ded3ab0d29dc459715c680711e72fca/Screenshot%202026-05-14%20at%204.31.17%E2%80%AFPM-20260514-110200.png?cb=b3fd954ab34470fa0ed1bfcb9c398150) Sample Migration-MoveGroup-Wave-Report [Migration-MoveGroups-Waves-Report.xlsx](https://support.cloudamize.com/__attachments/a_90162f2aa11932db1d9210320b2fab133c75b2c3f142ae3c49b7462d30c3434e/Migration-MoveGroups-Waves-Report.xlsx.md?cb=0b7caa60c06891d5e7d3f72f2651d108) #### Grouping Logic Auto-grouping logic has been refined to improve readability and operational usability. Enhancements include: * Servers without dependencies are grouped separately and displayed at the bottom for easier identification. * Servers with no agent communication are grouped together for simplified inspection and analysis. * Group sizing optimizations based on real-world migration feedback to improve manageability. #### Performance Improvements Cloudamize has introduced multiple scalability and performance optimizations to improve large-scale migration planning. Enhancements include: * LLM-side optimizations, including streaming token counting during model execution. * Improved responsiveness and scalability for larger assessments. * Support for processing approximately 150 groups across 1,200+ servers per assessment. #### Wave Tag Synchronization Across the Application Wave tags are now synchronized across the Cloudamize application to ensure consistency between auto-grouping workflows and application tagging. Enhancements include: * Tags applied during auto-grouping automatically reflected in application-level tagging. * Application-tagged servers synchronized back into auto-grouping workflows. * Improved consistency between migration grouping decisions and application tagging. ### **Accessing AI Move groups** The **AI Wave Groups** feature is part of the overall planning functionality within the Cloudamize platform. The steps to initiate the process are: * **Log in to the Cloudamize Console** (if you are not already logged in) [https://console.cloudamize.com](https://console.cloudamize.com/) * **Click the Plan Tile:** Click on the **Plan** tile. ![Screenshot 2026-07-22 at 1.08.22 PM-20260722-073857.png](https://support.cloudamize.com/__attachments/a_db82f2e57337e59dcb925947bca28e1aad4dfef9eaae59949478a656371b369e/Screenshot%202026-07-22%20at%201.08.22%E2%80%AFPM-20260722-073857.png?cb=76c65137fc56f1493e5553830e531a4a) * Click on the **AI Augmented wave-group** highlighted in the screenshot below. ![image-20260210-063931.png](https://support.cloudamize.com/__attachments/a_d4ec86ffacababcb837a0fc6943d358b8827fb1ac49c941ea4c3c54856a61418/image-20260210-063931.png?cb=9a863c0664ef00af3da97f52f9d2f669) Once you click on the **AI Augmented wave-group**, you will see a screen displaying all the AI-created Groups and Waves. ![image-20251210-125104.png](https://support.cloudamize.com/__attachments/a_0d41a08ea55b4885d3d800e9535908de15f84732555a4d59f0dc42e9a2f900d1/image-20251210-125104.png?cb=457a0259da0c02dd60bd4446f18039a8) ### **Waves** The **Waves** section at the top of the **AI Augmented Move Groups \& Waves** interface serves as a dynamic filter, displaying only the AI Move Groups assigned to the current migration batch via the "Select a wave" dropdown. Expanding a wave shows the scheduled groups, while expanding an assigned AI Move Group reveals the individual **servers** within that group. Unscheduled groups remain unlisted or in the **Backlog** until assigned. Users can **lock** waves to prevent accidental changes, requiring an **unlock** to edit assignments. ![image-20251210-125243.png](https://support.cloudamize.com/__attachments/a_f03286a60d0216aefa72d4f619da33db440d91495cdffdcec1f9f191fb659b03/image-20251210-125243.png?cb=1d6db7c434495db5aaed89776190e479) ### Creating Custom Waves In addition to using the pre-populated waves (Backlog, Wave 1, Wave 2, etc.), users can now create custom waves to better align with their specific migration project timelines. * **How to Add a New Wave:** 1. Locate a move group in the **AI Move Groups Recommendations** list. 2. Click the **Wave Dropdown** menu (currently showing "Select a wave" or an assigned wave). 3. Scroll to the bottom of the dropdown list and click **+ Add New Wave**. ![image-20260210-063659.png](https://support.cloudamize.com/__attachments/a_a159c9f20f1df2d37a39e9f2d4b1253ca0dc84818d70287692e7e7739bfd3abd/image-20260210-063659.png?cb=ee9b50941bcb39e23f902e43f458562d) * **Automatic Naming:** To maintain a consistent migration sequence, the system will automatically name the new wave using the next available number in the series (e.g., creating a wave after "Wave 1" will automatically generate "**Wave 2**"). * **Visibility:** The newly created wave will immediately appear in the **Waves summary section** at the top of the interface, where you can lock/unlock it or track its total machine count. ![image-20260210-064338.png](https://support.cloudamize.com/__attachments/a_be39bf85d89aeb9064c2eb61dc4db05caf1044778e348c74afe072ec017d9250/image-20260210-064338.png?cb=379389d232085cfccd56b6d12555251d) **Note:** New waves are created in the unlocked state by default, allowing you to immediately assign additional move groups to them. ### AI Move Groups Recommendations The **AI Move Groups Recommendations** section lists groups automatically created by the AI engine. These groups consist of machines that communicate or depend on each other. Each recommended group is numbered to indicate the suggested execution order. Users must use the adjacent dropdown menu to **"Select a wave"** , assigning the group to a specific migration batch. Clicking the group name reveals individual servers, while the info icon explains the AI's grouping rationale, which may include factors like dependency density or risk. Users can also open the **Move panel** by selecting machines within a group to manually reassign servers to a different target group or wave. ![image-20251210-131222.png](https://support.cloudamize.com/__attachments/a_ba7619293360baa933d302d6783fc01d374247ecf419b080b97e8f180d1d6560/image-20251210-131222.png?cb=295704e45860192de3c03eca30f7fc14) The screenshot below shows that selecting machines within a group enables the **Move panel** to open, allowing manual reassignment of servers to a different target group. ![image-20251210-130725.png](https://support.cloudamize.com/__attachments/a_03683ef99ce09ee03ea13684ad68b4ff21ed110a560bf1ec44eed09fb5f82b35/image-20251210-130725.png?cb=46861dd1832487662de60ec452eb6ba2) #### No Dependency \& Externally Dependent Servers In the **Auto Grouping** section, for handling machines with no active or verified dependencies and to provide better granularity for your infrastructure analysis, the system now categorizes these machines into specific groups based on their communication profiles. Please note that these groups are currently assigned the **lowest priority** in the auto-grouping order, and a standard reason is automatically appended whenever they are generated to ensure clarity. Group Classification Logic Depending on the total volume of servers, the system will either split them into two distinct categories or merge them into a single group. 1. **Split Groups (Combined Total \>= 15 Machines)** If the combined count of machines meeting the criteria below is **15 or greater**, the system will generate two separate groups: * **Retain/Retire/Standalone** **Criteria:** Contains machines that have no identified dependencies, instances where all active processes are set to be ignored, or machines that are *only* talking to other machines marked for ignore. * **Externally Dependent (Unverified Dependencies)** **Criteria:** Contains machines that communicate *exclusively* with **No Agent Machines (** Machines with no Cloudamize agent installed**)**. ![image-20260617-091646.png](https://support.cloudamize.com/__attachments/a_150ca4cfb9b1b23a007f3ebc43680032103da07eda096b723c9e2c8a54fdbc4f/image-20260617-091646.png?cb=15976ecb4f384e3d5c6c6fca9d0bd7a7) **Retain/Retire/Standalone** ![image-20260617-091752.png](https://support.cloudamize.com/__attachments/a_200fdbef378b396cb8fc8ab2e6bef9dc67a5c9e8f45ad56df79bfc9f33aca6f4/image-20260617-091752.png?cb=5c3d341044a3c2336d1e125b1e5af73a) **Externally Dependent (Unverified Dependencies)** 2. **Merged Group (Combined Total \< 15 Machines)** To prevent cluttering the interface with small, fragmented groups, an automatic merger occurs if the total machine count is low. * **Externally Dependent (Unverified Dependencies)/Retain/Retire/Standalone** **Criteria:** This combined group is created **only** when the total sum of machines from *both* of the above categories is **less than 15** (Count \< 15). ![image-20260617-092014.png](https://support.cloudamize.com/__attachments/a_ae5ef29f0209f3d3c8dbf00f0099c8633b33721ba540dbc1e2fe8128f35426a0/image-20260617-092014.png?cb=1038196c3d4d19b6136fb2e6b15269ac) **Externally Dependent (Unverified Dependencies)/Retain/Retire/Standalone** ### Wave Tag Synchronization (Auto-Grouping to App Tagging) To streamline migration planning, Cloudamize now features **Wave Tag Sync**, ensuring that tags applied within the AI-Augmented Auto-Grouping section are automatically propagated to App Tagging. * **Move Group Tagging:** When a Wave Tag is applied to an entire Move Group within the Auto-Grouping section, the system automatically cascades this tag to: * Every Machine within that Move Group. * All associated processes are linked to those machines. * *Note: This action will override any existing Wave Tags on these entities to ensure consistency. These updates are reflected instantly in the App Tagging Grid.* * **Machine Movement \& Reassignment:** If a Machine is moved from one Move Group to another that already has an assigned Wave Tag: * The target Move Group's Wave Tag is automatically applied to the moved Machine and its processes. * Any previously assigned Wave Tag is overridden. * The updated status is synchronized and visible within the App Tagging Grid. ![image-20260212-092557.png](https://support.cloudamize.com/__attachments/a_1c914a598d0f9546f6b7c89f34055ee3c22e1ce6feceb1743669e91b56dd7857/image-20260212-092557.png?cb=5b7c884c82210daca1ff90991d1d7bb4) Currently part of Wave1 ![image-20260212-092822.png](https://support.cloudamize.com/__attachments/a_559b8151bafc9b8304f4623bf01442ce8cb51283409046eb11b84815665692a6/image-20260212-092822.png?cb=6b8fe040c0c62e08f967be1782de69b8) Selected Wave2 in AI Augmented Move Groups and Waves ![image-20260212-130226.png](https://support.cloudamize.com/__attachments/a_16b20986892f29373598e6c5070be15999df55afe19917b08d92b9b142b3727a/image-20260212-130226.png?cb=613bddf8f2bb92297e67685e27adebc7) ### Wave Tag Synchronization (App Tagging to Auto Grouping) When a **Wave tag** isapplied to a **Move Group**, and then * Navigate to **App Tagging** anytime and apply a **different Wave tag** to any **Process** on a machine that belongs to Move Group, the updated Wave tag will automatically be applied to: * The corresponding **Move Group** * All machines within that Move Group and its respective processes .(*This ensures consistency of Wave tags between App Tagging and Auto Grouping.*) * Machines or processes that were **not tagged via a Move Group** will continue to behave as before, with no change in their existing tagging behavior. ![Screenshot 2026-03-05 at 2.26.14 PM-20260305-085620.png](https://support.cloudamize.com/__attachments/a_1b75ebfed2c75d3a26f5a8aa8ee3615e6d0d76113737a551f0471719cbdd7137/Screenshot%202026-03-05%20at%202.26.14%E2%80%AFPM-20260305-085620.png?cb=1c8a5d974a5e06a8534bc4a4b5652c2d) Selected Wave1 in AI Augmented Move Groups and Waves ![Screenshot 2026-03-05 at 1.13.16 PM-20260305-074423.png](https://support.cloudamize.com/__attachments/a_587f00f516826adaa5222a1c63b0fb0983ffa367d86ecfd0651e12bcc4d2624a/Screenshot%202026-03-05%20at%201.13.16%E2%80%AFPM-20260305-074423.png?cb=2bb041d3d4efa2c2d1560d8f09ea7235) Currently part of Wave1 ![Screenshot 2026-03-05 at 1.16.19 PM-20260305-075753.png](https://support.cloudamize.com/__attachments/a_39f704d8bab35f7af70c21c4cf07b0b772e9f3328d6e6be7cc99b03869cbf322/Screenshot%202026-03-05%20at%201.16.19%E2%80%AFPM-20260305-075753.png?cb=7451a775bb29f0676d1096f595766bfd) Selected Wave2 in App Tagging and applied ![Screenshot 2026-03-05 at 1.18.24 PM-20260305-074954.png](https://support.cloudamize.com/__attachments/a_04e6287b629f4dbefd79735a552f004aaef01f440670ef7660f4d9821a519422/Screenshot%202026-03-05%20at%201.18.24%E2%80%AFPM-20260305-074954.png?cb=0cb698fe407555f4d7aadda8115ac662) Changed to Wave2 in App Tagging ![Screenshot 2026-03-05 at 1.21.29 PM-20260305-075151.png](https://support.cloudamize.com/__attachments/a_816a7b7a7b242d938c587221c7791a4cdbb0bea65322ebc90b38710ac06f32ff/Screenshot%202026-03-05%20at%201.21.29%E2%80%AFPM-20260305-075151.png?cb=1c49073c4e3e3c31c8fe6318ad1e1d62) Reflecting under Wave2 under Waves ![Screenshot 2026-03-05 at 2.09.10 PM-20260305-083957.png](https://support.cloudamize.com/__attachments/a_0a9b636b97b08a321901643e00ae485ff75ff711caf8fe6091ba58b9e14a3c47/Screenshot%202026-03-05%20at%202.09.10%E2%80%AFPM-20260305-083957.png?cb=4d9fc5f9d76ef24a02423a2217e50f26) Changed to Wave2 in AI Augmented Move Groups and Waves ![Screenshot 2026-03-05 at 1.24.24 PM-20260305-075518.png](https://support.cloudamize.com/__attachments/a_9ce4075722d1906935a9ceeebb4320c6c63b73471d16092e58269588dd325274/Screenshot%202026-03-05%20at%201.24.24%E2%80%AFPM-20260305-075518.png?cb=f88422a9e7c1c8c0f9bdd14094fcea9c) Updated Wave tag automatically applied to other machine within that Move group ### **Network Connectivity Icon** The **Network Connectivity icon** next to each AI Move Group recommendation lets users view the group's dependencies instantly. Clicking this icon opens a new screen, such as the **"Connectivity for Group"** view, which visually illustrates how the applications and servers within that group communicate with each other and with external entities. This visualization helps users validate the AI's grouping logic and understand the communication flow both within and between groups. ![image-20251210-131826.png](https://support.cloudamize.com/__attachments/a_14a525e4a4546d124a7a513800a8d6522d0c39556ec6d62fad4c6abb640b5d2b/image-20251210-131826.png?cb=b651c5f61ab69b84196bccc4e0f907bd) **Connectivity for AI Group** ![Screenshot 2026-04-10 at 10.36.31 AM.png](https://support.cloudamize.com/__attachments/a_43d66c35e349c281e07be5475a3d7094a594d6576a1b87ed141171ff97001f70/Screenshot%202026-04-10%20at%2010.36.31%E2%80%AFAM.png?cb=a9dc2098fdf8ba41348bdd24d5a8f1fe) **Info Icon** The **Info Icon** reveals the **"Reason for Recommendation"** and **"Confidence Score"** for the AI Move Group, explaining *why* the machines were clustered together. This pop-up often details specific running services and connectivity metrics (e.g., zero internal connectivity). This crucial feature helps users validate the AI's grouping logic against their migration strategy. ![image-20251210-132446.png](https://support.cloudamize.com/__attachments/a_fc40883b9039a97d1b59c68d3d81d6df8c67b0dfad9c32c534123fd143655041/image-20251210-132446.png?cb=580bab563c9e25a644ebb894ff982e9c) ### **Machine and Connectivity Details Overlay** (Green Icon) This enables seamless interaction with both machine nodes and connection edges, allowing users to explore and access detailed information directly within the graph interface. For every Group in a cluster, a **Green interconnectivity button** is available on the right of the row. Clicking this button opens the **Group-Centric Network Connectivity** panel ![Screenshot 2026-04-10 at 10.22.01 AM-20260410-045253.png](https://support.cloudamize.com/__attachments/a_c15620a0962493313eaf9dd145ac67478dd35d817ea7a0b050802e375356882e/Screenshot%202026-04-10%20at%2010.22.01%E2%80%AFAM-20260410-045253.png?cb=443d2c724246e6bd4b74d44f0a67fe3c) Clicking on any **machine node or connection edge** opens a right-side overlay panel with relevant details. * **For machine nodes:** It shows connectivity with other machines along with the direction of those connections, and displays host name, IP addresses, application name, and number of times seen. ![Screenshot 2026-04-10 at 10.44.39 AM-20260410-051603.png](https://support.cloudamize.com/__attachments/a_5527e673f995b13c4e561e0795664496f09d4ef93c4e68084b2c2e34ee1db5d8/Screenshot%202026-04-10%20at%2010.44.39%E2%80%AFAM-20260410-051603.png?cb=d47897e8e2f8a7b0feee542b9ef86fd7) ![Screenshot 2026-04-10 at 10.35.16 AM-20260410-050647.png](https://support.cloudamize.com/__attachments/a_adbcec12ee4b8451182d25c2a959af866e64a336aa53f4757ac5ef68e575c82f/Screenshot%202026-04-10%20at%2010.35.16%E2%80%AFAM-20260410-050647.png?cb=d0fc846ba67ee58c23e4e51aea71d7b8) * **For connection edges:** It displays connection direction, number of times seen, and source/target details across all supported types (Machine\<-\>Machine, Group\<-\>Group, Machine\<-\>Group). ![Screenshot 2026-04-10 at 10.47.56 AM-20260410-051913.png](https://support.cloudamize.com/__attachments/a_b9fbe3b4497cda14fea614d7f64efe4c430cf98a449da1dda029bd3faea7c3ab/Screenshot%202026-04-10%20at%2010.47.56%E2%80%AFAM-20260410-051913.png?cb=45b099cff647aabd407f5997684fd6ff) ![Screenshot 2026-04-10 at 10.39.05 AM-20260410-051027.png](https://support.cloudamize.com/__attachments/a_e08e930ff98b32630a0254eef81e80faaa265a560a2e7a003063dc9eb9aa714c/Screenshot%202026-04-10%20at%2010.39.05%E2%80%AFAM-20260410-051027.png?cb=087b80d4bc8c65f12ce142e4608a2b71) ### **Machine Interconnectivity Tool (White Icon)** For every machine in a cluster, a **white interconnectivity button** is available on the far right of the row. Clicking this button opens the **Application Connectivity** panel, providing critical technical data for migration validation: * **Connectivity Summary:** View the total number of unique connections associated with the machine. * **Directional Categories:** Traffic is categorized into **Inbound** (clients connecting to this host), **Outbound** (servers this host depends on), and **Self** (internal loopback traffic). * **Observation Frequency:** The panel displays the exact number of times each unique connection was observed by the Cloudamize agent during the collection period. This helps distinguish between high-frequency application dependencies and infrequent administrative tasks. * **Operating System Visibility:** Identifies the OS of connected peers to assist in security group planning and compatibility checks. ![image-20260121-095429.png](https://support.cloudamize.com/__attachments/a_331ac90dd27c3142e86b1601996d15f166a9460ad0ef81ddee411dede40da834/image-20260121-095429.png?cb=289edc67c6b92bd5d60945a113e09ea2) ### The Guide Section The **Guide** panel on the right side of the interface serves as a contextual help resource. It explains key concepts, including **AI Augmented Move Group Suggestions** , **Waves** , and **Assigning a Wave** . Additionally, it provides instructions for advanced actions like **Moving Machines** between groups. The guide features a section on **Tips** for optimizing the migration plan, such as checking wave assignments for key dependencies, keeping early waves small to reduce risk, and using filters to identify unusual machines. ![image-20251210-132735.png](https://support.cloudamize.com/__attachments/a_7c8cf3d4ed21061ada641bdd81239d9015fc90f622bb973770da701f3dd5f266/image-20251210-132735.png?cb=78638f31e233f3a9663fa4e205a33b08) #### **Reset All** and **Collapse All** buttons Located at the top-right of the **AI Augmented Move Groups \& Waves** workspace, the **Reset All** and **Collapse All** buttons provide essential global controls for managing large-scale migration environments. The **Reset All** function serves as a project-wide refresh, instantly reverting any unsaved wave assignments or temporary drag-and-drop changes to their last state, which is ideal for correcting complex planning errors. The **Collapse All** control optimizes the visual workspace by minimizing all expanded clusters and waves. This hides granular machine-level details---such as host names, IP addresses, and connectivity icons---allowing planners to quickly scan high-level group headers and navigate extensive environments without excessive scrolling. ![image-20260121-095956.png](https://support.cloudamize.com/__attachments/a_7abd49c665bcf4e6ce6c624042811fb79f293ddd8410eeee058913e25db5f90c/image-20260121-095956.png?cb=94899ca889471c129ea3b3f632e53486) If you have any queries, please get in touch with the helpdesk via our [++Helpdesk Portal++](https://cloudreach-software.atlassian.net/servicedesk/customer/portal/9) or by email at [++helpdesk@cloudamize.com++](mailto:helpdesk@cloudamize.com). --- language: "en" --- # AI augumented Move Groups & Waves ## Overview The AI-Augmented Move Groups \& Waves capability within Cloudamize enhances migration planning by automatically organizing servers and applications into intelligent migration groups and execution waves. Using AI-driven analysis and mathematically modeled dependency mapping, Cloudamize helps customers reduce manual planning effort while improving migration efficiency, sequencing and operational alignment. This functionality analyzes infrastructure relationships, communication patterns and network dependencies to recommend optimal migration groupings. The result is a more structured and data-driven migration strategy that minimizes risk, reduces complexity and accelerates cloud adoption initiatives. **Steps to navigate to the AI Augmented Move Groups \& Waves Report:** 1. Log in to the console 2. Navigate to the Plan page of your completed assessment. ![Screenshot 2026-07-22 at 1.08.22 PM-20260722-073857.png](https://support.cloudamize.com/__attachments/a_0906a27d48cfee2dd23a10a4daa90720251994893da4e3c37841614a3c52ec59/Screenshot%202026-07-22%20at%201.08.22%E2%80%AFPM-20260722-073857.png?cb=76c65137fc56f1493e5553830e531a4a) 3. Click on the Reports Section as shown in the screenshot below under the Plan section. 4. Click on **AI Augmented Move Groups \& Waves** → **Detailed** to download the report. ![Screenshot 2026-05-14 at 5.36.07 PM-20260514-120712.png](https://support.cloudamize.com/__attachments/a_c25f8301fe2409697e4ebedaebb02f3756ab06530800bb783c01910d09f7e41e/Screenshot%202026-05-14%20at%205.36.07%E2%80%AFPM-20260514-120712.png?cb=0c97223ff4a17d8802ae113f3e512aef) ## Servers | **Column Name** | **Description** | |-----------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Order | Sequential identifier representing the migration group execution or processing order. Used to identify the recommended migration sequence. | | Move Group | Name of the migration group containing related or interdependent servers/applications that should be migrated together to avoid dependency or connectivity issues. | | Wave | Migration wave or phase assigned to the server/group. This helps organize migrations into batches or timelines. A value of "-" indicates that the wave has not yet been assigned. | | Server Name | Hostname or system name of the individual server included in the migration group. | | Ip Address | IP address associated with the server for network identification and connectivity purposes. | | Type | Technology stack, application category, or server role associated with the server. Multiple values separated by semicolons indicate that the server supports multiple functions or technologies. | ## Move Groups |------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Column Name | Description | | Order | Sequential identifier indicating the recommended order in which move groups should be migrated. | | Move Group | Name of the migration group representing a set of interconnected systems, applications, or services that should be migrated together. | | Reasoning | Detailed explanation describing why the systems were grouped together, including dependency analysis, connectivity, migration strategy, infrastructure relationships, and risk considerations. | | Confidence Score | A percentage-based confidence level indicating how strongly the migration grouping and sequencing recommendation is supported by the dependency and connectivity analysis. Higher percentages indicate greater confidence in the grouping accuracy. | Example Report: [Migration-MoveGroups-Waves-Report-2026-05-14 12_11_48.xlsx](https://support.cloudamize.com/__attachments/a_e79abd62aa52525aa54be1e9162e2e068620cd6df23bf3e08f4f7b415761b77d/Migration-MoveGroups-Waves-Report-2026-05-14%252012_11_48.xlsx.md?cb=abb0b90375b61581bbaffd988474c597) If you have any queries, please get in touch with the helpdesk via our [++Helpdesk Portal++](https://cloudreach-software.atlassian.net/servicedesk/customer/portal/9) or by email at [++helpdesk@cloudamize.com++](mailto:helpdesk@cloudamize.com). --- language: "en" --- # Alternate (non-agent) Data Collection Methods * [Hyper-V](https://support.cloudamize.com/kb/hyper-v.md) * [vCenter](https://support.cloudamize.com/kb/vcenter.md) --- language: "en" --- # Amazon FSx for NetApp ONTAP Recommendations (FSxN) ## **Overview** The AWS FSx service offers fully managed, high-performance file systems designed to replace or extend customers' on-premises file storage. Cloudamize provides advanced analytics to automatically analyze your on-premises environment and generate optimized migration recommendations for **Amazon FSx for NetApp ONTAP (FSxN)**. This page describes the **FSxN tab** , which appears in every assessment and compares FSxN vs. EBS pricing for your EC2 data volumes based on standard Agent/Agentless telemetry. This is different from the separate [**FSx Recommendation for NetApp Report**](https://support.cloudamize.com/kb/fsx-recommendation-for-netapp-report), which requires a dedicated NetApp ONTAP data collection (via the Agentless Data Collector connecting directly to your NetApp ONTAP systems) and sizes a full migration of your on-premises NetApp environment to FSxN. If you're not sure which one you're looking at, see the comparison below. | | FSxN tab | FSx Recommendation for NetApp Report | |--------------------------------------|-------------------------------------------------------------------------------------------------|-----------------------------------------------------------------------------| | Data source | Standard Agent/Agentless telemetry | Agentless Data Collector connected directly to NetApp ONTAP systems (v9.6+) | | Included in every assessment? | Yes | No, requires separate NetApp data collection | | Scope | Data volumes on servers already in the assessment (root/boot volumes excluded must stay on EBS) | Can include NetApp storage even if not otherwise part of the assessment | | Sizing basis | Used capacity and performance demand of the volume, as observed | Current on-premises NetApp system configuration | | Requires a confirmed NetApp backend? | No | Yes | ## **What is Supported?** Cloudamize evaluates qualifying on-premises storage workloads---such as **Linux/Unix file systems (NFS)** , **high-performance NAS environments** , block storage via **iSCSI** , and existing **NetApp configurations**---and generates optimized storage recommendations for FSxN deployments. ## **Data Collection** Cloudamize collects all necessary performance and telemetry data for FSxN migrations using its standard Agent and Agentless Data Collectors. No additional configuration, specialized tooling, or separate tracking permissions are required. ## **How it Works** 1. **Workload Identification:** On-premises volumes and file shares matching NetApp ONTAP deployment profiles are automatically flagged for FSxN analytics. 2. **TCO Optimization:** Recommendations are formulated by mapping performance profiles, capacity requirements, IOPS, and throughput characteristics against AWS FSxN architecture constraints. 3. **Reporting:** The final Total Cost of Ownership (TCO) results model these services side-by-side with standard EC2 compute and storage pricing to identify structural cost savings. ## **What it Looks Like** The Assessment Details screen and its corresponding downloadable reports feature structural layouts optimized for usability. **Column-level filters** are available across all tables, allowing users to quickly segment, search, and parse assets. ### Dashboard Visibility The **Analyze** dashboard summary panel dynamically updates overall project TCO and storage metrics based on your selected **Design Profile** ![image-20260916-051204.png](https://support.cloudamize.com/__attachments/a_a91401c8229ada582db8d9935bfc3b8b80ed53d14f248726e1536dbee8a0f104/image-20260916-051204.png?cb=2029a34124ccbe804ab72da4d1bede1b) ### FSxN Savings Callout \& Direct Navigation When eligible storage volumes are identified under the active design profile, a dedicated savings highlight card appears on the left summary panel directly beneath the **Total Annual Cost** donut chart: ![image-20260916-051325.png](https://support.cloudamize.com/__attachments/a_46ab112ec66240142f921b544441db96d5596dfe7494cd530dad947e99a06539/image-20260916-051325.png?cb=b0acf001cfe28c04ee2d77cd6e5db71c) * **TCO Impact Badge:** Displays baseline TCO struck through next to the newly optimized annual spend (e.g., `~$376k $370k -1.8%`). * **Net Savings Summary:** Highlights the net financial savings and total storage footprint reduced (e.g., `↓ $6.7k and 14 TB saved with FSxN`). * **Direct Navigation (** `View details →`**):** Clicking the `View details →` link on the savings callout automatically opens the **FSxN Tab** in the main content area, providing immediate access to volume-level recommendations, Single-AZ/Multi-AZ deployment types, observed occupancy, and individual disk savings calculations. **Note on Design Selection:** Changing the selected **Design Profile** from the top menu toolbar instantly recalculates volume eligibility, refreshes the left panel TCO callout, and updates the detailed inventory rows within the **FSxN Tab**. ### No Eligible Volumes Detected If no storage volumes within the assessed infrastructure meet the qualification criteria for FSxN under the selected design profile: * **Status Message:** The summary panel displays the message: `No FSxN-eligible volumes --- all storage priced on EBS` * **Storage Line Item Impact:** Under the **Storage** category breakdown, a sub-label clarifies: `ⓘ Cost shown is all EBS`. ![image-20260916-051741.png](https://support.cloudamize.com/__attachments/a_5a55376f34ff68554062752c387aac45cb55a52fab8484db95e34763a753fbc3/image-20260916-051741.png?cb=906fc0ded04cbe30c3d8c6eee6e211a0) You can also directly select the **FSxN** tab to view the comprehensive asset and performance metrics as shown below. ![Screenshot 2026-06-25 at 10.44.11 AM-20260625-051503.png](https://support.cloudamize.com/__attachments/a_460dab9fed55b838e53b48599997b5a8e1570aa5c05cb2a92e290d169193aff3/Screenshot%202026-06-25%20at%2010.44.11%E2%80%AFAM-20260625-051503.png?cb=8bea5d5a17d79c31330e416096f887b0) ![Screenshot 2026-06-25 at 10.45.48 AM-20260625-051553.png](https://support.cloudamize.com/__attachments/a_504542990a7725f6d3ee26c9f3673eabb3d0dd86556b316fb47f9186454959ad/Screenshot%202026-06-25%20at%2010.45.48%E2%80%AFAM-20260625-051553.png?cb=4ba0fded68aff644add0595c0e14049d) ### **Include volumes with negative savings** * By default, the **Include volumes with negative savings** option is unchecked. In this state, the **Annual Cost** is calculated using only volumes that generate positive FSxN savings compared to EBS. * When the **Include volumes with negative savings** option is selected, volumes where FSxN costs more than EBS are also included in the calculation. The **Annual Cost** is then recalculated to reflect both positive and negative savings volumes. * The **Savings** column is fixed (frozen) in the table view, ensuring it remains visible while scrolling horizontally across other columns. * Positive and negative savings values are visually distinguished through highlighting, making it easier to identify increases and decreases at a glance. ![Screenshot 2026-06-25 at 10.51.22 AM-20260625-052544.png](https://support.cloudamize.com/__attachments/a_8ca1e41e237253029ffecb69bb0f80eb0f2a0d7adfd189f6c584ab549b12ed12/Screenshot%202026-06-25%20at%2010.51.22%E2%80%AFAM-20260625-052544.png?cb=99f9465a88e52191516fb7eee896abcc) ![Screenshot 2026-06-25 at 11.23.13 AM-20260625-055650.png](https://support.cloudamize.com/__attachments/a_933686ccc6051b36b4b410701c48212388f19b9e5b3476fcbd30dac55a1118f2/Screenshot%202026-06-25%20at%2011.23.13%E2%80%AFAM-20260625-055650.png?cb=4f879034ff189d497c42036022339300) **Column Definitions \& Data Dictionary** |--------------------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------| | Column Name | Description | | Server Name | The machine's hostname is associated with the analyzed workload. | | Disk | The specific identifier or path of the analyzed on-premises disk/volume. | | Single-AZ/Multi-AZ | Indicates whether the recommended FSxN deployment is Single-AZ (within one Availability Zone) or Multi-AZ (highly available across two AZs). | | Compression/Deduplication % | The estimated percentage of storage savings derived from NetApp ONTAP's native data efficiency features. | | Observed Disk Capacity (GB) | The total raw storage capacity allocated to the disk on-premises. | | Observed Disk Occupancy (GB) | The actual used/occupied storage space is measured on the disk during the assessment period. | | FSxN Volume Id | The unique identification number assigned by Cloudamize to map this recommendation. | | FSxN Generation | Specifies the underlying hardware/software deployment generation recommended for the architecture. | | Total Recommended Storage (GB) | The combined recommended total storage footprint (SSD + Capacity Pool) for the target FSxN volume. | | SSD Storage (GB) | The portion of recommended storage allocated to the high-performance SSD tier (Primary tier). | | Capacity Pool Storage (GB) | The portion of recommended storage allocated to the cost-optimized Capacity Pool tier (Cold/infrequently accessed data). | | Throughput (MBps) | The expected throughput bandwidth provisioned for the FSxN file system in megabytes per second. | | Included IOPS | The baseline SSD IOPS are automatically included with the provisioned storage capacity at no extra charge. | | Additional IOPS | The amount of extra, custom-provisioned IOPS required to sustain peak workload demands beyond the baseline. | | SSD Storage Cost ($) | The estimated monthly cost for the high-performance SSD storage tier. | | Capacity Pool Storage Cost ($) | The estimated monthly cost for the capacity pool storage tier. | | Throughput Cost ($) | The monthly cost associated with provisioning the recommended throughput capacity. | | Additional IOPS Cost ($) | The monthly cost incurred from provisioning additional IOPS beyond the baseline allotment. | | Total FSxN Cost ($) | The total estimated monthly cost of the entire optimized Amazon FSxN deployment (Sum of SSD, Capacity Pool, Throughput, and Additional IOPS costs). | | Total EBS Cost ($) | The comparative monthly cost baseline if this storage workload were provisioned using traditional Amazon EBS block storage volumes. | | Savings ($) | The projected net monthly cost savings achieved by migrating the workload to FSxN instead of traditional block storage (Total EBS Cost - Total FSxN Cost). | **Summary** |--------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Total FSxN Savings ($) | Total estimated annual cost savings achieved by using Amazon FSx for NetApp ONTAP compared to the current storage and infrastructure costs. Calculated as the difference between current annual costs and projected FSxN costs. | | Total Annual Cost ($) | Total current annual infrastructure cost, including compute, storage, networking, licensing, and other applicable expenses. | | Total Compute ($) | Total cost associated with compute resources (servers, virtual machines, CPU, and memory) required to support the workload. | | Total Network ($) | Total cost related to network usage and connectivity, including data transfer, bandwidth, and networking infrastructure charges. | | Total License ($) | Total software licensing costs associated with the workload, such as operating systems, database licenses, and storage management software. | | Total FSxN Cost ($) | Total projected annual cost of running the workload on Amazon FSx for NetApp ONTAP, including storage, throughput, backups, and any associated FSxN service charges. | | Total EBS for Root Volumes ($) | Total cost of Amazon Elastic Block Store (EBS) volumes used as root (boot) disks for compute instances supporting the workload. | | Total Storage Cost ($) | Total cost of storage resources, including primary data storage, backups, snapshots, and other storage-related services. | If you have any queries, please get in touch with the helpdesk via our [++Helpdesk Portal++](https://cloudreach-software.atlassian.net/servicedesk/customer/portal/9) or by email at [++helpdesk@cloudamize.com++](mailto:helpdesk@cloudamize.com). --- language: "en" --- # AMD Cloud Design Standards ## Overview Cloudamize provides automated design profiles tailored for migrating and optimizing workloads on **AMD-powered cloud instances**. These design standards enable organizations to leverage the high per-core performance, increased memory bandwidth, and cost-efficiency of modern AMD EPYC™ processors. By selecting an AMD design profile, Cloudamize automatically evaluates your discovered infrastructure against all available AMD instance families across target providers to calculate the optimal cloud placement. ### AMD Cloud Design Profiles Users can select from two specialized AMD design profiles: ![image-20260901-061042.png](https://support.cloudamize.com/__attachments/a_aea6aec853ea747647c1c7b4c6a30f4523440cffda59b3380927f8d3f0d92ef6/image-20260901-061042.png?cb=9b64b5e229c8accfc60aed0e7f30d886) #### 1. AMD Modernize \& Downsize * **Description:** Downsizes the target workload to a smaller, faster AMD instance family to cut overall compute costs. * **Sizing Logic \& Strategy:** Evaluates observed CPU, RAM, and storage utilization. Leverages the higher per-core performance of modern AMD processors to safely downsize vCPU allocations while sustaining or improving workload performance. * **Primary Business Outcome:** **Cost Reduction \& Efficiency.** Maximizes savings by reducing the instance size footprint without sacrificing operational stability. #### 2. AMD Modernize * **Description:** Performs a same-size upgrade to faster, next-generation AMD hardware for higher overall performance. * **Sizing Logic \& Strategy:** Maintains the equivalent vCPU and memory footprint as the source asset (or baseline target), upgrading directly to current-generation AMD instance families. * **Primary Business Outcome:** **Maximum Performance \& Throughput.** Boosts processing speed, IOPS, and application performance for mission-critical or compute-heavy workloads without altering core allocation ratios. ### AMD Benchmark Mapping \& Workload Logic The recommendation engine leverages specialized AMD performance benchmarks to accurately right-size target compute environments: * **Specific Workload Benchmarks:** Sizing calculations use dedicated AMD benchmark profiles for target applications running **NGINX, Stream, Java, FFmpeg, PostgreSQL, Redis, and MySQL**. * **Generalized Workload Baseline:** For all other application and OS workload types not explicitly listed in the benchmark matrix, Cloudamize applies a standardized **averaged AMD benchmark** calculation. * **Fallback \& Instance Selection:** The engine first attempts to retrieve source benchmarks within the active OLA plan. If source benchmarks are missing or unlisted, Cloudamize enforces all available AMD instance families across the target cloud provider to determine the best fit. **Note on Benchmark Precision:** Workloads running NGINX, Stream, Java, FFmpeg, PostgreSQL, Redis, or MySQL are mapped against precise workload-specific AMD benchmarks. All other workloads seamlessly utilize an averaged AMD benchmark profile to ensure accurate sizing across the entire inventory. If you have any queries, please get in touch with the helpdesk via our [++Helpdesk Portal++](https://cloudreach-software.atlassian.net/servicedesk/customer/portal/9) or by email at [++helpdesk@cloudamize.com++](mailto:helpdesk@cloudamize.com). --- language: "en" --- # Analyze, Projected Annual Cloud Costs This dashboard serves as the initial landing page for the "Analyze" section of the Cloudamize platform. It provides a concise summary of a completed cloud assessment, providing a high-level overview of the on-premise or existing infrastructure and a top-line projection of the annual cost to migrate to a specific cloud provider. ![image-20250925-064615.png](https://support.cloudamize.com/__attachments/a_c7e2c5044308a80e308314f40c1de69be36a4ff6dfb0ce4825dcedde93225692/image-20250925-064615.png?cb=bdbd80ae021673a26336c3548ef2e4ce) ## **Infrastructure Summary** Here at a glance, you can see the summary of the assessed infrastructure's key metrics: * **Compute:** Displays the total number of compute nodes (servers, VMs) that were discovered and analyzed. * **Storage:** Shows the total storage capacity, in terabytes, that was assessed. * **Network:** Indicates the total network traffic analyzed every month, measured in gigabytes. * **Assessment:** Indicates the status of assessment completion. The delivered assessment will show a `Completed` status and the delivery date of the assessment. ## **Projected Annual Cost** The Projected Annual Cost provides the Total Cost of Ownership (TCO) outcome of the cloud assessment for the IaaS provider selected. A contextual note explains the basis of the projection: "The Workload Mapping is the plan that finds IaaS configuration based on your workload usage for the pay-as-you-go pricing model." This means the cost is not a simple lift-and-shift estimate but is dynamically calculated based on actual observed workload performance data. * A horizontal bar chart visualizes the projected annual cost for **IaaS migration** to **AWS** , **Azure** , or **GCP**. * The chart clearly shows the **Cloud Provider** , **Target Region** (e.g., US East, West Europe, etc.), and the **Estimated Annual Cost**. * Clicking the **"View Details"** button takes you to the screen with a granular, per-service or per-asset breakdown of the projected costs. ## **Report Access** * **Observed Data Report:** Located at the bottom right, this button provides access to the full report. This report likely contains the raw performance data, utilization metrics, and detailed assumptions that were used to generate the cost projection. * **Comparison Report:** The **Comparison Report** is a key feature that provides a detailed, side-by-side analysis of projected annual costs across major cloud providers. It acts as a critical tool for IT and financial stakeholders to make informed, data-driven decisions on cloud migration strategy. The **Analyze Landing Page** is designed to provide a clear and immediate understanding of the assessment's findings, facilitating initial conversations and decisions about cloud migration strategy and cost. It is a stepping stone to the more detailed analytical views available within the Cloudamize platform. If you have any queries, please get in touch with the helpdesk via our [++Helpdesk Portal++](https://cloudreach-software.atlassian.net/servicedesk/customer/portal/9) or by email at [++helpdesk@cloudamize.com++](mailto:helpdesk@cloudamize.com). --- language: "en" --- # Analyze V2 Layout – Enhanced Navigation and User Experience ## Overview Analyze V2 introduces a redesigned user interface that improves the overall usability of the Analyze workspace, especially for assessments containing large infrastructure inventories. The new experience replaces the traditional horizontal tab layout with a left-hand navigation panel, allowing users to navigate more efficiently while keeping infrastructure cost information visible throughout the analysis process. **Note:** Analyze V2 is an interface enhancement only. No assessment calculations, recommendations, or costing logic have changed. ## Benefits of Analyze V2 Analyze V2 provides several usability improvements over the classic Analyze experience. ### Improved Navigation The previous horizontal navigation tabs have been replaced with a left-hand navigation panel, allowing users to move between analysis sections more efficiently without losing context. ### Better Cost Visibility Users can see infrastructure costs for each major section directly in the navigation panel, making it easier to identify cost-intensive areas before drilling into detailed data. ### Improved Workspace The navigation panel can be collapsed, providing additional screen space for reviewing large infrastructure tables, recommendations, and reports. ### Entity-focused Overview Each infrastructure category now presents an overview tailored to the selected entity, allowing users to quickly move from high-level costs to detailed infrastructure information. ## What's New in Analyze V2 | Area | Enhancement | |-------------------|------------------------------------------------------------------------------------------------------------------------| | Navigation | Horizontal tabs replaced with a left-side navigation panel | | Cost Visibility | Section-level costs are displayed directly within the navigation menu | | Savings Indicator | Overall savings percentage displayed at the top of the navigation panel using Lift \& Shift as the comparison baseline | | Overview | Entity-specific overview pages for Compute, Storage, Network, and other supported entities | | Workspace | Collapsible navigation panel for additional viewing space | | Menu Organization | Compute, Storage, Network, License, Designer, and Reports moved into the left navigation panel | ## Analyze V2 Navigation The left navigation panel serves as the primary navigation area for the Analyze workspace. Instead of displaying multiple tabs across the top of the page, all major analysis sections are consolidated into a single navigation menu. The available sections include: * Summary * Compute * Storage * Network * License * Designer * Reports This navigation model provides a consistent experience across assessment types while supporting future enhancements. Scope and compatibility **In scope:** layout redesign, left-panel navigation with cost-per-section, updated menu options, savings indicator, collapsible panel, and analysis overview. **Compatibility:** Analyze V2 is an optional user interface enhancement and does not replace the classic Analyze experience. Users can switch between the two interfaces at any time using the **Analyze V2** toggle. ### User-Level Toggle Users can enable or disable Analyze V2 from the user profile menu using the **Analyze V2** toggle. This allows users to: * Experience the redesigned interface. * Switch back to the classic Analyze page whenever needed. * Compare both interfaces during the transition period. ![Screenshot 2026-07-22 at 12.55.00 PM-20260722-072617.png](https://support.cloudamize.com/__attachments/a_052acc6128e10c6f72c5dd4434182a961ce34b34d31a3b7867518b8954681851/Screenshot%202026-07-22%20at%2012.55.00%E2%80%AFPM-20260722-072617.png?cb=da3eeef45332a1c690b8e6b11d155b13) ^Home screen Analyze V2^ ### **Analyze V2 Home Screen** The redesigned Analyze page moves the primary navigation to the left-hand panel and displays infrastructure costs alongside each navigation section. The expanded navigation panel provides full visibility into available analysis sections, while the collapsible view maximizes workspace for reviewing larger infrastructure inventories. The right side of the page displays data for the selected section. For example, the **Summary** and **Compute** pages present infrastructure information in a table that includes: * Search * Filters * Export * Refresh * Pagination These capabilities make Analyze V2 suitable for both high-level infrastructure reviews and detailed analysis. ![Screenshot 2026-07-09 at 10.32.55 AM-20260709-050300.png](https://support.cloudamize.com/__attachments/a_a006aed6d6abf1145e35759d9e2ebca5cfe5eed7f29bbcfcbf8bb9130f9ed251/Screenshot%202026-07-09%20at%2010.32.55%E2%80%AFAM-20260709-050300.png?cb=fca758726fc70397a8a93d309351578f) ^Analyze V2 Home Screen^ ### **Classic Analyze banner** The classic Analyze page shows a banner that invites users to try the new Analyze experience. This provides a gradual migration path: users can discover Analyze V2 from the existing workflow, try the new layout, and still return to the classic view through the profile setting if needed. ![Screenshot 2026-07-09 at 10.42.31 AM-20260709-051325.png](https://support.cloudamize.com/__attachments/a_33c370531bcf4ea800572963edf0bc0fbd1a1ab2ff4f668f9fce3e47bec8f3f2/Screenshot%202026-07-09%20at%2010.42.31%E2%80%AFAM-20260709-051325.png?cb=a7a0649f8621c7ec2133f1cdfb0e12b4) ^Try it out option to switch to Analyze V2^ ![Screenshot 2026-07-09 at 10.53.24 AM-20260709-052329.png](https://support.cloudamize.com/__attachments/a_5d55b4edb48d38fe91ab2e9b81b3fc834a3dc626e5bd4f9cca1cd55036b7d92e/Screenshot%202026-07-09%20at%2010.53.24%E2%80%AFAM-20260709-052329.png?cb=966804e3e4c5c7ca827719474d6832ec) ^Analyze V2 Home Screen^ ### Switching Back to Classic Analyze Users can return to the classic Analyze interface at any time by disabling the **Analyze V2** toggle from the user profile menu. ![Screenshot 2026-07-09 at 10.37.48 AM-20260709-050827.png](https://support.cloudamize.com/__attachments/a_2ad19ce124b5012f2ad54cbbc8c149a35a935fafa61c18c6334c32a34eec58db/Screenshot%202026-07-09%20at%2010.37.48%E2%80%AFAM-20260709-050827.png?cb=33d1bf7e298f2fd9a76952609e3da68d) ^Toggle to switch back to Classic analyze^ **Caveat:** If a user is viewing the **EVS** tab in the classic Analyze page and then switches directly to Analyze V2, the overview/TCO cost may not be displayed correctly. In some cases, the overview cost may fail to load due to an error while retrieving the overview cost information. As a workaround, navigate away from the EVS tab before enabling Analyze V2, or refresh the Analyze V2 page after switching. If you have any queries, please get in touch with the helpdesk via our [++Helpdesk Portal++](https://cloudreach-software.atlassian.net/servicedesk/customer/portal/9) or by email at [++helpdesk@cloudamize.com++](mailto:helpdesk@cloudamize.com). --- language: "en" --- # Analyzing Data Collected by Agents The Cloudamize agents collect system and performance data from your machines. A detailed description of the data we collect is available on the [Data Collected by Agents](https://support.cloudamize.com/kb/data-collected-by-agent) page. In rare cases, customers would like to analyze the actual data collected by the Cloudamize Agents before beginning their assessment. This guide outlines the steps necessary to capture the data "over-the-wire" as-is is being sent from the Cloudamize Agent to the Cloudamize Server. To review and analyze the data collected by Cloudamize Agents, without sending any data to Cloudamize, you can use a proxy server that captures traffic to /uploadFileV3, while allowing all other traffic to continue to am.cloudamize.com, am-de.cloudamize.com, or am-ae.cloudamize.com. **The proxy server described in this guide resides inside your network and must be installed and configured by your network and security teams.** Note: This guide is provided as-is and is not supported by Cloudamize Support team. As no two networks are alike and there are multiple products that can be used as proxies, Cloudamize cannot provide support or give any technical assistance in setting up the proxy server of your choice. As an example, instructions for setting up an NGINX proxy are available [here](http://nginx.org/en/docs/beginners_guide.html#proxy). Before Agents send data, they must register themselves with am.cloudamize.com in the US, am-de.cloudamize.com in Europe, or am-ae.cloudamize.com in the UAE. After they have registered themselves they will begin sending data to am.cloudamize.com/uploadFileV3 (or am-de or am-ae depending on the target region). Note that the string, File Successfully Uploaded!, should be included in the response to /uploadFileV3 for a successful file upload. After setting up the proxy, install Cloudamize Agents using the following "no-op" customer key: `44ac3d540b1a180a69b3ac4789413d0bc272f9aed9ecc86512733b8ad1cd0c1c` Note: Data sent to Cloudamize using this "no-op" customer key will be rejected by Cloudamize. Because of this, Agents installed with the "no-op" customer key will need to be uninstalled and the Agent will need to be reinstalled with a valid customer key located at Cloudamize console before beginning an assessment. ## Windows Agent You can download the Windows agent [here](https://am.cloudamize.com/cxf/downloadFileV3?custkey=44ac3d540b1a180a69b3ac4789413d0bc272f9aed9ecc86512733b8ad1cd0c1c&filename=cloudamizeAgent.msi). When prompted for your Customer Key, please use the following: `44ac3d540b1a180a69b3ac4789413d0bc272f9aed9ecc86512733b8ad1cd0c1c` To install the Agent from the command prompt as administrator use the following: Case 1) Forward proxy msiexec /i customerkey=44ac3d540b1a180a69b3ac4789413d0bc272f9aed9ecc86512733b8ad1cd0c1c USE_PROXY=1 HTTPS_PROXY="https://www.your_own_proxy.com" PROXY_PORT="your_proxy_server_port" IS_SERVER_CERTIFICATE_SIGNED_BY_CA=0 /qn If your proxy server requires authentication, use the following, updated command: msiexec /i customerkey=44ac3d540b1a180a69b3ac4789413d0bc272f9aed9ecc86512733b8ad1cd0c1c USE_PROXY=1 HTTPS_PROXY="https://www.your_own_proxy.com" PROXY_PORT="your_proxy_server_port" USE_PROXY_CREDENTIAL=1 PROXY_USER_NAME="user_name" PROXY_PASSWORD="password" IS_SERVER_CERTIFICATE_SIGNED_BY_CA=0 /qn Case 2) Reverse proxy msiexec /i customerkey=44ac3d540b1a180a69b3ac4789413d0bc272f9aed9ecc86512733b8ad1cd0c1c SERVER_DOMAIN_NAME="reverse proxy domain name" SERVER_IP="reverse proxy ip" IS_SERVER_CERTIFICATE_SIGNED_BY_CA=0 ALLOW_HOSTS_FILE_UPDATE=1 If a reverse proxy is installed on a machine where the agent is installed, here is the example command. msiexec /i cloudamizeAgent.msi customerkey=44ac3d540b1a180a69b3ac4789413d0bc272f9aed9ecc86512733b8ad1cd0c1c SERVER_DOMAIN_NAME=localhost SERVER_IP=127.0.0.1 IS_SERVER_CERTIFICATE_SIGNED_BY_CA=0 ALLOW_HOSTS_FILE_UPDATE=1 ## Linux Agent ### Prerequisites: * One of the following OSes: * Red Hat Enterprise Linux Server release 7.0 or higher * Oracle Linux 6.5 or higher * Ubuntu 16.04 or higher * CentOS release 7 or higher * Debian GNU/Linux 8.0 or higher * Amazon Linux AMI release 2013.03 or higher * Fedora release 12 or higher * Suse Linux 11 or higher * A [supported](https://www.openssl.org/policies/releasestrat.html) version of OpenSSL * Root and/or Wheel Group access * 350 MB persistent storage * The Install script requires ***wget*** to retrieve content, and ***curl*** to test/verify access to our data collection servers at **am.cloudamize.com for US infrastructure, am-de.cloudamize.com for EU infrastructure, or am-ae.cloudamize.com** **for UAE infrastructure** over port 443, either directly or through a corporate proxy. * If your system locally caches DNS resolution, you may need to resolve am.cloudamize.com to **35.171.170.26** or am-de.cloudamize.com to **18.194.12.63**to allow egress traffic. This feature is not currently available for our UAE region. *Note: The Linux agent/Agentless approach requires a user with root permissions to get PID-to-network mapping, certain hardware details, and data on logical/physical disk volumes. Become root user either through "sudo -s" or "su", most systems use sudo.* ### Procedure: **Step 1:** Export your customer key. export CLOUDAMIZE_CUSTOMER_KEY=44ac3d540b1a180a69b3ac4789413d0bc272f9aed9ecc86512733b8ad1cd0c1c **Step 2:** Execute the following command to install the Cloudamize Agent and configure it to route the data through your own proxy server: sh <(curl --proxy https://www.yourproxy.com:proxy_port 'https://am.cloudamize.com/cxf/downloadFileV3?custkey=44ac3d540b1a180a69b3ac4789413d0bc272f9aed9ecc86512733b8ad1cd0c1c&filename=installCloudamizeAgentV2.sh' -L) If your proxy server requires authentication, use the following, updated command. sh <(curl --proxy https://www.yourproxy.com:proxy_port --proxy-user username:password 'https://am.cloudamize.com/cxf/downloadFileV3?custkey=44ac3d540b1a180a69b3ac4789413d0bc272f9aed9ecc86512733b8ad1cd0c1c&filename=installCloudamizeAgentV2.sh' -L) Click [here](https://support.cloudamize.com/hc/en-us/articles/223218128-Installation-Troubleshooting) for steps to troubleshoot installation issues. Click [here](https://support.cloudamize.com/hc/en-us/articles/360000544173-Uninstall-Cloudamize-Windows-Linux-Agent) for instructions on how to uninstall the linux agents. ## Agentless You can download the Agentless installer [here](https://am.cloudamize.com/cxf/downloadFileV3?custkey=44ac3d540b1a180a69b3ac4789413d0bc272f9aed9ecc86512733b8ad1cd0c1c&filename=cloudamizeAgentlessDC.msi). When prompted for your Customer Key, please use the following: `44ac3d540b1a180a69b3ac4789413d0bc272f9aed9ecc86512733b8ad1cd0c1c` To install the Agent from the command prompt as administrator use the following: msiexec /i customerkey=44ac3d540b1a180a69b3ac4789413d0bc272f9aed9ecc86512733b8ad1cd0c1c USE_PROXY=1 HTTPS_PROXY="https://www.your_own_proxy.com" PROXY_PORT="your_proxy_server_port" /qn If your proxy server requires authentication, use the following, updated command: msiexec /i customerkey=44ac3d540b1a180a69b3ac4789413d0bc272f9aed9ecc86512733b8ad1cd0c1c USE_PROXY=1 HTTPS_PROXY="https://www.your_own_proxy.com" PROXY_PORT="your_proxy_server_port" USE_PROXY_CREDENTIAL=1 PROXY_USER_NAME="user_name" PROXY_PASSWORD="password" /qn If you have any queries, please get in touch with the helpdesk via our [++Helpdesk Portal++](https://cloudreach-software.atlassian.net/servicedesk/customer/portal/9) or by email at [++helpdesk@cloudamize.com++](mailto:helpdesk@cloudamize.com). --- language: "en" --- # App CPU Usage Report The **App CPU Usage Report** in Cloudamize provides deep visibility into how much CPU resources are consumed by individual applications running on each server or virtual machine in your environment. This data is crucial for **right-sizing, optimization, troubleshooting** , and **migration planning**. **Steps to navigate to the APP CPU Usage Report:** 1. Log in to the console 2. Navigate to the Plan page of your completed assessment. ![Screenshot 2026-07-22 at 1.08.22 PM-20260722-073857.png](https://support.cloudamize.com/__attachments/a_9518eb116bb6bf2f8bd5495b1df3849149f77e18297242768aab3d2cc9ce0864/Screenshot%202026-07-22%20at%201.08.22%E2%80%AFPM-20260722-073857.png?cb=76c65137fc56f1493e5553830e531a4a) 3. Click on the Reports Section as shown in the screenshot below under the Plan section. 4. Click on **App CPU Usage** → **Detailed** to download the report. ![Screenshot 2025-08-11 at 4.30.57 PM-20250811-110143.png](https://support.cloudamize.com/__attachments/a_128aac2899af3f716acd130c814d4eb8d72d8c96fc4c430a739ad72347d9d5b2/Screenshot%202025-08-11%20at%204.30.57%E2%80%AFPM-20250811-110143.png?cb=7e3891752ccbeee46cc8599591f1abe4) | Column Name | Description | |---------------------|----------------------------------------------------------------------------------| | **Process Name** | The name of the running process on the system. | | **CPU Utilization** | Percentage of CPU resources used by the process. | | **Group Name** | Logical or organizational grouping associated with the process or asset. | | **Asset Name** | The name/type of the asset associated with the process (e.g., Database, Script). | | **Instance Name** | Unique identifier or label for the specific instance of the asset. | **Example Report:** [MigrationPlanner-AppCPUUsage-Report.xlsx](https://support.cloudamize.com/__attachments/a_b541b45cea89c2ef3cb13b7f0b887858f301c8d540473e7c87f413099d85f0d9/MigrationPlanner-AppCPUUsage-Report.xlsx.md?cb=25358a7c81897d6b3391ba9438a4b94c) If you have any queries, please get in touch with the helpdesk via our [++Helpdesk Portal++](https://cloudreach-software.atlassian.net/servicedesk/customer/portal/9) or by email at [++helpdesk@cloudamize.com++](mailto:helpdesk@cloudamize.com). --- language: "en" --- # App Interconnectivity Report ## Overview The **Application Interconnectivity Report** in **Cloudamize** provides a detailed map of how applications and systems communicate with each other across your IT environment. This is one of the most powerful features of the Cloudamize platform, enabling you to understand system dependencies, group workloads intelligently, and design cloud migrations with minimal risk. The **Application Interconnectivity** feature in **Cloudamize** captures inbound and outbound traffic patterns, service dependencies, network connections, and more --- delivering a real-time, actionable view of your application ecosystem. This data is vital for cloud migration, application modernization, dependency analysis, and network architecture planning. **Steps to navigate to the App Interconnectivity Report:** 1. Log in to the console 2. Navigate to the Plan page of your completed assessment. ![Screenshot 2026-07-22 at 1.08.22 PM-20260722-073857.png](https://support.cloudamize.com/__attachments/a_b3e1cb11ce04413baf67c300dabbef31ad5375daa76cab8e1a3b9d2a7d11490a/Screenshot%202026-07-22%20at%201.08.22%E2%80%AFPM-20260722-073857.png?cb=76c65137fc56f1493e5553830e531a4a) 3. Click on the Reports Section as shown in the screenshot below under the Plan section. 4. Click on **App Interconnectivity** → **Detailed** to download the report. ![Screenshot 2025-08-12 at 10.31.52 AM-20250812-050250.png](https://support.cloudamize.com/__attachments/a_28081530ded965a84e22e324d1e2b9c0b41dc2ecae2139fda20ce21c1aa9bd61/Screenshot%202025-08-12%20at%2010.31.52%E2%80%AFAM-20250812-050250.png?cb=33f05ca3ffe86b56545966cfd36f63ba) | **Column Name** | **Description** | |---------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Client Group** | The logical group or business unit that the **client system** (initiating communication) belongs to. Grouping may be based on tags, resource groups, locations, or organizational units discovered during the scan. | | **Client Asset** | The **name of the asset (server, VM, or machine)** that initiated the connection. This is often the hostname or system identifier detected by Cloudamize. | | **Client Instance** | The specific **instance name** (e.g., VM name in AWS/Azure or on-prem) of the client asset initiating communication. Helpful for identifying virtualized or cloud-native deployments. | | **Client Process** | The **application or process** running on the client machine that initiated the communication. This gives context into what software/service is making the connection (e.g., `chrome.exe`, `sqlclient`, `powershell`, etc.). | | **Server Group** | The logical group or business unit that the **server system** (receiving communication) belongs to. Helps understand application flows across environments, tiers, or departments. | | **Server Asset** | The **name of the asset (server, VM, or machine)** that received the communication request. Typically, the hostname or system identifier of the server. | | **Server Instance** | The specific **instance name** (e.g., EC2 instance, Azure VM, VMware guest) of the server receiving the connection. Useful in multi-instance or hybrid environments. | | **Server Process** | The **application or process** on the server that responded to the connection. This could be a web server (`httpd`), database (`mysqld`, `sqlservr.exe`), or any background service. Identifying server processes helps trace application functionality and dependencies. | **Example Report:** [MigrationPlanner-AppInterconnectivity-Reportxlsx.xlsx](https://support.cloudamize.com/__attachments/a_d38cf0945d8a933478b22a4b7b84c843f6d853a82c2f6decff50aefcb2b67300/MigrationPlanner-AppInterconnectivity-Reportxlsx.xlsx.md?cb=124d7e8cfeaf9d21d3a695a0f2a2be41) If you have any queries, please get in touch with the helpdesk via our [++Helpdesk Portal++](https://cloudreach-software.atlassian.net/servicedesk/customer/portal/9) or by email at [++helpdesk@cloudamize.com++](mailto:helpdesk@cloudamize.com). --- language: "en" --- # App Interconnectivity Report (All) ## **App Interconnectivity( (All) Report -- Overview** The **App Interconnectivity App (All)** report in **Cloudamize** provides a comprehensive view of the **communication and dependency relationships** between applications discovered during the assessment. It helps users understand **how applications interact with each other across the environment**. This data is vital for cloud migration, application modernization, dependency analysis, and network architecture planning. **Steps to navigate to the App Interconnectivity(All) Report:** 1. Log in to the console 2. Navigate to the Plan page of your completed assessment. ![Screenshot 2026-07-22 at 1.08.22 PM-20260722-073857.png](https://support.cloudamize.com/__attachments/a_035e4b226c553ff9a125394b361b8f29ee03541e04fbe9995434e0ef63eb8c19/Screenshot%202026-07-22%20at%201.08.22%E2%80%AFPM-20260722-073857.png?cb=76c65137fc56f1493e5553830e531a4a) 3. Click on the Reports Section as shown in the screenshot below under the Plan section. 4. Click on **App Interconnectivity(All)** → **Detailed** to download the report. ![Screenshot 2025-10-07 at 12.37.28 PM-20251007-070832.png](https://support.cloudamize.com/__attachments/a_d0d4f7df6e9c190f6a284d19911cc4ce1fd30bdcedf5baf2e717589b82e24436/Screenshot%202025-10-07%20at%2012.37.28%E2%80%AFPM-20251007-070832.png?cb=e6d0da9aef042827f5273d8c607ab0df) | **Column Name** | **Description** | |---------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Client Group** | The **application group or logical grouping** of the client-side application initiating the communication (for example, a front-end app or user interface component). | | **Client Asset** | The **server or machine name** where the client-side application or process resides. Represents the source system initiating the connection. | | **Client Instance** | The **specific instance** of the client application or service running on the client asset. Used to distinguish between multiple instances of the same app on different hosts. | | **Client Process** | The **process name or executable** on the client side responsible for initiating the network communication (e.g., `tomcat.exe`, `sqlservr.exe`). | | **Server Group** | The **application group or logical grouping** of the server-side application receiving the communication (for example, a back-end or database tier). | | **Server Asset** | The **server or machine name** where the destination or target application resides. Represents the system receiving the connection. | | **Server Instance** | The **specific instance** of the target or server application running on the destination asset. Helps identify distinct deployments or service instances. | | **Server Process** | The **process name or executable** on the server side that receives and handles the request from the client (e.g., `mysqld.exe`). | **Example Report**: [MigrationPlanner-AppInterconnectivity(All)-Report.xlsx](https://support.cloudamize.com/__attachments/a_c426fea638bc44100659286499fb439ef1b901b9fb2e7c6d4dd89c609a61725a/MigrationPlanner-AppInterconnectivity(All)-Report.xlsx.md?cb=eed8f666048ca5bac6094f1bc673ad8b) If you have any queries, please get in touch with the helpdesk via our [++Helpdesk Portal++](https://cloudreach-software.atlassian.net/servicedesk/customer/portal/9) or by email at [++helpdesk@cloudamize.com++](mailto:helpdesk@cloudamize.com). --- language: "en" --- # Application Catalogue Report ## Overview The **Application Catalogue Report** empowers users with a detailed view of the business applications they have created within the Application Catalogue tool. It consolidates key application details in one place and provides critical information needed for effective migration planning, helping users make informed decisions and ensuring smoother migration execution. ### How to Download the Report Currently, the export option is available **only for individual business applications**, not for all business applications in bulk. Follow these steps to generate and download the **Application Catalog Report** for any business application created in the Application Catalogue tool: 1. From the main menu, navigate to the **Plan**page. 2. Go to the **Application Catalog** tab. 3. Select the **Business Application** for which you want to generate the report. 4. Click on the **Export** button on the right side of the selected business application's name. 5. The report will be downloaded in **DOCX format**. ![Screenshot 2025-04-24 at 12.43.25 PM.png](https://support.cloudamize.com/__attachments/a_edc92bb61fe5477e5f710835b140913bd3fa37c1d4af19548256b309e8191578/Screenshot%202025-04-24%20at%2012.43.25%E2%80%AFPM.png?cb=38c9eb4427499fa18f480986dabb62ea) The Export Button highlighted in the Application Catalogue page, for the "TESTing dpTest123@#$" Business Application ### Report Contents The **Application Catalog Report** offers a structured summary of the selected business application in Migration Planner, including: * **Associated Processes and Machines** * **IP and DNS Details** * **Cost Estimation** * **Target Instance Type Details** Three sections are currently present in the report but not yet populated: * **Firewall Rules** *(Section available, data coming soon)* * **Security Groups** *(Section available, data coming soon)* * **Application Dependencies** *(Section available, data coming soon)* Data for these sections will be included in a future release. ### Sample Report Layouts ![image-20250424-080421.png](https://support.cloudamize.com/__attachments/a_3083cd7559d60c3545bc400635c2115e76c64a2826f0db7aea2f84896abce672/image-20250424-080421.png?cb=9bfae7c4d1332091d77496969d229196) ![image-20250424-080539.png](https://support.cloudamize.com/__attachments/a_d7217880fbc7478191197b54268c4a1c407e32b9447b8544b519261289d78c26/image-20250424-080539.png?cb=a74147961498b20ffeacac5dfb4f3573) ![image-20250424-080658.png](https://support.cloudamize.com/__attachments/a_72f8988dfb2ad2642b1a24913257cf30603de55d7825728cfed4632019a0ea0c/image-20250424-080658.png?cb=99456eecb110ee4b48386afb5137296f) If you have any queries, please get in touch with the helpdesk via our [++Helpdesk Portal++](https://cloudreach-software.atlassian.net/servicedesk/customer/portal/9) or by email at [++helpdesk@cloudamize.com++](mailto:helpdesk@cloudamize.com). --- language: "en" --- # Application Data Postprocessing **Analytics Licenses** |------------------------------|---------------------------------------------------------------------------------------------------------------------------------------| | Matlab Compile Runtime (MCR) | [MCR Licenses](https://cloudamize-2.atlassian.net/wiki/display/EN/MCR+Licenses) (purchased) | | Postgresql's JDBC driver | [BSD](http://asm.objectweb.org/license.html) | | python | [Python Licenses Deployed with Analytics](https://cloudamize-2.atlassian.net/wiki/display/EN/Python+Licenses+Deployed+with+Analytics) | | log4m | [log4m License](https://cloudamize-2.atlassian.net/wiki/display/EN/log4m+License) | # this file as made by running briandailey's python-packages-license-check and updating the entries marked "UNKNOWN" from Anaconda's 3rd party license info located here: # Some are not included in Anaconda's list. To find those, one can search of other lists , such as **Unique Licenses** |----------------------------------------------------------|-------------------------------------------------------------------------------| | | | | | | | 2-clause BSD | [2-Clause BSD](https://opensource.org/licenses/BSD-2-Clause) | | 3-clause BSD | [3-Clause BSD](https://cloudreach-software.atlassian.net/wiki/3-Clause%20BSD) | | Apache | [Apache](http://www.apache.org/licenses/LICENSE-1.0.txt) | | Apache License, Version 2.0 | [Apache 2.0](http://www.apache.org/licenses/LICENSE-2.0) | | BSD | [BSD](http://asm.objectweb.org/license.html) | | Copyright (C) 2011 Serge S. Koval | [Apache 2.0](http://www.apache.org/licenses/LICENSE-2.0) | | Copyright 2011-2013 Jeffrey Gelens \ | [Apache 2.0](http://www.apache.org/licenses/LICENSE-2.0) | | Expat license | [Expat License](http://choosealicense.com/licenses/mit/) | | GNU GPL | [GNU GPL License](https://www.gnu.org/licenses/gpl-3.0.en.html) | | ISC | [ISC License](https://opensource.org/licenses/ISC) | | LGPL | [LGPL License](http://www.gnu.org/licenses/lgpl-2.1.html) | | LGPL with exceptions or ZPL | [LGPL with Exceptions](http://www.gnu.org/licenses/lgpl-2.1.html) | | LICENSE.txt | N/A | | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | Modified BSD | [Modified BSD](http://oss-watch.ac.uk/resources/modbsd) | | New BSD | [New BSD](http://www.opensource.org/licenses/bsd-license.html) | | proprietary - Continuum Analytics, Inc. | N/A | | public domain, Python, 2-Clause BSD, GPL 3 | (see COPYING.txt) | | Python Software Foundation License | [Python License](https://www.python.org/download/releases/2.7/license/) | | Simplified BSD | [Simplified BSD](https://opensource.org/licenses/BSD-2-Clause) | | Standard PIL License | [Standard PIL License](http://www.pythonware.com/products/pil/license.htm) | | ZPL 2.1 | [ZPL 2.1](http://directory.fsf.org/wiki?title=License:ZopePLv2.1) | | Chest License | [Chest License](https://github.com/blaze/chest/blob/master/LICENSE.txt) | | Anaconda License | [Chest License](https://github.com/blaze/chest/blob/master/LICENSE.txt) | **All Licenses** |-----------------------------------------------------------------------------|--------------------------------------------------------------|-------------------------------------------------------------------------------| | | | | | | | | | sphinx | BSD | [BSD](http://asm.objectweb.org/license.html) | | setuptools | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | alabaster | BSD | [BSD](http://asm.objectweb.org/license.html) | | anaconda-client | BSD | [BSD](http://asm.objectweb.org/license.html) | | anaconda-navigator | proprietary - Continuum Analytics, Inc. | [Anaconda License](https://docs.continuum.io/anaconda/eula) | | argcomplete | Apache Software License | [Apache](http://www.apache.org/licenses/LICENSE-1.0.txt) | | astropy | BSD | [BSD](http://asm.objectweb.org/license.html) | | Babel | BSD | [BSD](http://asm.objectweb.org/license.html) | | backports.ssl-match-hostname | BSD | [BSD](http://asm.objectweb.org/license.html) | | backports-abc | PSF | [Python License](https://www.python.org/download/releases/2.7/license/) | | bcolz | BSD | [BSD](http://asm.objectweb.org/license.html) | | beautifulsoup4 | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | binstar | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | bitarray | PSF | [Python License](https://www.python.org/download/releases/2.7/license/) | | blaze | BSD | [BSD](http://asm.objectweb.org/license.html) | | bokeh | New BSD | [New BSD](http://www.opensource.org/licenses/bsd-license.html) | | boto | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | Bottleneck | Simplified BSD | [Simplified BSD](https://opensource.org/licenses/BSD-2-Clause) | | cdecimal | BSD License | [BSD](http://asm.objectweb.org/license.html) | | certifi | ISC | [ISC License](https://opensource.org/licenses/ISC) | | cffi | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | chest | BSD | [BSD](http://asm.objectweb.org/license.html) | | [cloudpickle](https://github.com/ContinuumIO/chest/blob/master/LICENSE.txt) | LICENSE.txt | [Chest License](https://github.com/blaze/chest/blob/master/LICENSE.txt) | | clyent | BSD | [BSD](http://asm.objectweb.org/license.html) | | colorama | BSD | [BSD](http://asm.objectweb.org/license.html) | | comtypes | MIT License | [MIT License](http://choosealicense.com/licenses/mit) | | conda | BSD | [BSD](http://asm.objectweb.org/license.html) | | conda-build | BSD | [BSD](http://asm.objectweb.org/license.html) | | conda-env | BSD | [BSD](http://asm.objectweb.org/license.html) | | conda-manager | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | configobj | BSD | [BSD](http://asm.objectweb.org/license.html) | | cryptography | BSD or Apache License, Version 2.0 | [BSD](http://asm.objectweb.org/license.html) | | cycler | BSD | [BSD](http://asm.objectweb.org/license.html) | | Cython | Apache | [Apache](http://www.apache.org/licenses/LICENSE-1.0.txt) | | cytoolz | BSD | [BSD](http://asm.objectweb.org/license.html) | | dask | BSD | [BSD](http://asm.objectweb.org/license.html) | | datashape | BSD | [BSD](http://asm.objectweb.org/license.html) | | decorator | new BSD License | [New BSD](http://www.opensource.org/licenses/bsd-license.html) | | decorator | BSD license | [BSD](http://asm.objectweb.org/license.html) | | dill | BSD | [BSD](http://asm.objectweb.org/license.html) | | docutils | public domain, Python, 2-Clause BSD, GPL 3 (see COPYING.txt) | [2-Clause BSD](https://opensource.org/licenses/BSD-2-Clause) | | enum34 | BSD License | [BSD](http://asm.objectweb.org/license.html) | | et-xmlfile | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | fastcache | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | Flask | BSD | [BSD](http://asm.objectweb.org/license.html) | | Flask-Cors | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | funcsigs | ASL | [Apache](http://www.apache.org/licenses/LICENSE-1.0.txt) | | futures | BSD | [BSD](http://asm.objectweb.org/license.html) | | gevent | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | gevent-websocket | Copyright 2011-2013 Jeffrey Gelens \ | [Apache](http://www.apache.org/licenses/LICENSE-1.0.txt) | | greenlet | MIT License | [MIT License](http://choosealicense.com/licenses/mit) | | grin | BSD | [BSD](http://asm.objectweb.org/license.html) | | h5py | 3-clause BSD | [3-Clause BSD](https://cloudreach-software.atlassian.net/wiki/3-Clause%20BSD) | | HeapDict | BSD | [BSD](http://asm.objectweb.org/license.html) | | idna | BSD-like | [BSD](http://asm.objectweb.org/license.html) | | ipaddress | Python Software Foundation License | [Python License](https://www.python.org/download/releases/2.7/license/) | | ipykernel | BSD | [BSD](http://asm.objectweb.org/license.html) | | ipython | BSD | [BSD](http://asm.objectweb.org/license.html) | | ipython-genutils | BSD | [BSD](http://asm.objectweb.org/license.html) | | ipywidgets | BSD | [BSD](http://asm.objectweb.org/license.html) | | itsdangerous | BSD | [BSD](http://asm.objectweb.org/license.html) | | jdcal | BSD | [BSD](http://asm.objectweb.org/license.html) | | jedi | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | Jinja2 | BSD | [BSD](http://asm.objectweb.org/license.html) | | jsonschema | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | jupyter | BSD | [BSD](http://asm.objectweb.org/license.html) | | jupyter-client | BSD | [BSD](http://asm.objectweb.org/license.html) | | jupyter-console | BSD | [BSD](http://asm.objectweb.org/license.html) | | jupyter-core | BSD | [BSD](http://asm.objectweb.org/license.html) | | llvmlite | BSD | [BSD](http://asm.objectweb.org/license.html) | | locket | BSD | [BSD](http://asm.objectweb.org/license.html) | | lxml | BSD | [BSD](http://asm.objectweb.org/license.html) | | MarkupSafe | BSD | [BSD](http://asm.objectweb.org/license.html) | | matplotlib | BSD | [BSD](http://asm.objectweb.org/license.html) | | menuinst | BSD | [BSD](http://asm.objectweb.org/license.html) | | mistune | BSD | [BSD](http://asm.objectweb.org/license.html) | | mock | BSD | [BSD](http://asm.objectweb.org/license.html) | | mpmath | BSD | [BSD](http://asm.objectweb.org/license.html) | | multipledispatch | BSD | [BSD](http://asm.objectweb.org/license.html) | | nbconvert | BSD | [BSD](http://asm.objectweb.org/license.html) | | nbformat | BSD | [BSD](http://asm.objectweb.org/license.html) | | networkx | BSD | [BSD](http://asm.objectweb.org/license.html) | | nltk | Apache License, Version 2.0 | [Apache 2.0](http://www.apache.org/licenses/LICENSE-2.0) | | nose | GNU LGPL | [GNU GPL License](https://www.gnu.org/licenses/gpl-3.0.en.html) | | notebook | BSD | [BSD](http://asm.objectweb.org/license.html) | | numba | BSD | [BSD](http://asm.objectweb.org/license.html) | | numexpr | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | numpy | BSD | [BSD](http://asm.objectweb.org/license.html) | | odo | BSD | [BSD](http://asm.objectweb.org/license.html) | | openpyxl | MIT/Expat | [MIT License](http://choosealicense.com/licenses/mit) | | pandas | BSD | [BSD](http://asm.objectweb.org/license.html) | | partd | BSD | [BSD](http://asm.objectweb.org/license.html) | | path.py | MIT License | [MIT License](http://choosealicense.com/licenses/mit) | | patsy | 2-clause BSD | [2-Clause BSD](https://opensource.org/licenses/BSD-2-Clause) | | pep8 | Expat license | [Expat License](http://choosealicense.com/licenses/mit/) | | pickleshare | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | Pillow | Standard PIL License | [Standard PIL License](http://www.pythonware.com/products/pil/license.htm) | | pip | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | ply | BSD | [BSD](http://asm.objectweb.org/license.html) | | psutil | BSD | [BSD](http://asm.objectweb.org/license.html) | | psycopg2 | LGPL with exceptions or ZPL | [LGPL with Exceptions](http://www.gnu.org/licenses/lgpl-2.1.html) | | py | MIT license | [MIT License](http://choosealicense.com/licenses/mit) | | pyasn1 | BSD | [BSD](http://asm.objectweb.org/license.html) | | pycosat | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | pycparser | BSD | [BSD](http://asm.objectweb.org/license.html) | | pycrypto | Public-Domain | N/A | | pyflakes | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | Pygments | BSD License | [BSD](http://asm.objectweb.org/license.html) | | pyOpenSSL | APL2 | [Apache 2.0](http://www.apache.org/licenses/LICENSE-2.0) | | pyparsing | MIT License | [MIT License](http://choosealicense.com/licenses/mit) | | pyreadline | BSD | [BSD](http://asm.objectweb.org/license.html) | | pytest | MIT license | [MIT License](http://choosealicense.com/licenses/mit) | | python-dateutil | Simplified BSD | [Simplified BSD](https://opensource.org/licenses/BSD-2-Clause) | | pytz | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | pywin32 | PSF | [Python License](https://www.python.org/download/releases/2.7/license/) | | PyYAML | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | pyzmq | LGPL+BSD | [LGPL License](http://www.gnu.org/licenses/lgpl-2.1.html) | | QtAwesome | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | qtconsole | BSD | [BSD](http://asm.objectweb.org/license.html) | | QtPy | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | requests | Apache 2.0 | [Apache 2.0](http://www.apache.org/licenses/LICENSE-2.0) | | rope | GNU GPL | [GNU GPL License](https://www.gnu.org/licenses/gpl-3.0.en.html) | | ruamel-yaml | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | runipy | BSD | [BSD](http://asm.objectweb.org/license.html) | | scikit-image | Modified BSD | [Modified BSD](http://asm.objectweb.org/license.html) | | scikit-learn | new BSD | [New BSD](http://www.opensource.org/licenses/bsd-license.html) | | scipy | BSD | [BSD](http://asm.objectweb.org/license.html) | | simplegeneric | ZPL 2.1 | [ZPL 2.1](http://directory.fsf.org/wiki?title=License:ZopePLv2.1) | | singledispatch | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | six | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | snowballstemmer | BSD | [BSD](http://asm.objectweb.org/license.html) | | sockjs-tornado | Copyright (C) 2011 Serge S. Koval | [Apache](http://www.apache.org/licenses/LICENSE-1.0.txt) | | sphinx-rtd-theme | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | spyder | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | SQLAlchemy | MIT License | [MIT License](http://choosealicense.com/licenses/mit) | | statsmodels | BSD License | [BSD](http://asm.objectweb.org/license.html) | | sympy | BSD | [BSD](http://asm.objectweb.org/license.html) | | [toolz](http://www.opensource.org/licenses/bsd-license.php) | BSD | [BSD](http://asm.objectweb.org/license.html) | | tornado | Apache | [Apache](http://www.apache.org/licenses/LICENSE-1.0.txt) | | [traitlets](http://www.apache.org/licenses/LICENSE-2.0) | BSD | [BSD](http://asm.objectweb.org/license.html) | | ujson | BSD License | [BSD](http://asm.objectweb.org/license.html) | | unicodecsv | BSD License | [BSD](http://asm.objectweb.org/license.html) | | Werkzeug | BSD | [BSD](http://asm.objectweb.org/license.html) | | wheel | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | xlrd | BSD | [BSD](http://asm.objectweb.org/license.html) | | XlsxWriter | BSD | [BSD](http://asm.objectweb.org/license.html) | | xlwings | BSD 3-clause | [3-Clause BSD](https://cloudreach-software.atlassian.net/wiki/3-Clause%20BSD) | | xlwt | BSD | [BSD](http://asm.objectweb.org/license.html) | | xlwt: | BSD | [BSD](http://asm.objectweb.org/license.html) | --- language: "en" --- # Application Data Processing **Analytics Licenses** |------------------------------|---------------------------------------------------------------------------------------------------------------------------------------| | Matlab Compile Runtime (MCR) | [MCR Licenses](https://cloudamize-2.atlassian.net/wiki/display/EN/MCR+Licenses) (purchased) | | Postgresql's JDBC driver | [BSD](http://asm.objectweb.org/license.html) | | python | [Python Licenses Deployed with Analytics](https://cloudamize-2.atlassian.net/wiki/display/EN/Python+Licenses+Deployed+with+Analytics) | | log4m | [log4m License](https://cloudamize-2.atlassian.net/wiki/display/EN/log4m+License) | # this file as made by running briandailey's python-packages-license-check and updating the entries marked "UNKNOWN" from Anaconda's 3rd party license info located here: # Some are not included in Anaconda's list. To find those, one can search of other lists , such as **Unique Licenses** |----------------------------------------------------------|-------------------------------------------------------------------------------| | | | | | | | 2-clause BSD | [2-Clause BSD](https://opensource.org/licenses/BSD-2-Clause) | | 3-clause BSD | [3-Clause BSD](https://cloudreach-software.atlassian.net/wiki/3-Clause%20BSD) | | Apache | [Apache](http://www.apache.org/licenses/LICENSE-1.0.txt) | | Apache License, Version 2.0 | [Apache 2.0](http://www.apache.org/licenses/LICENSE-2.0) | | BSD | [BSD](http://asm.objectweb.org/license.html) | | Copyright (C) 2011 Serge S. Koval | [Apache 2.0](http://www.apache.org/licenses/LICENSE-2.0) | | Copyright 2011-2013 Jeffrey Gelens \ | [Apache 2.0](http://www.apache.org/licenses/LICENSE-2.0) | | Expat license | [Expat License](http://choosealicense.com/licenses/mit/) | | GNU GPL | [GNU GPL License](https://www.gnu.org/licenses/gpl-3.0.en.html) | | ISC | [ISC License](https://opensource.org/licenses/ISC) | | LGPL | [LGPL License](http://www.gnu.org/licenses/lgpl-2.1.html) | | LGPL with exceptions or ZPL | [LGPL with Exceptions](http://www.gnu.org/licenses/lgpl-2.1.html) | | LICENSE.txt | N/A | | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | Modified BSD | [Modified BSD](http://oss-watch.ac.uk/resources/modbsd) | | New BSD | [New BSD](http://www.opensource.org/licenses/bsd-license.html) | | proprietary - Continuum Analytics, Inc. | N/A | | public domain, Python, 2-Clause BSD, GPL 3 | (see COPYING.txt) | | Python Software Foundation License | [Python License](https://www.python.org/download/releases/2.7/license/) | | Simplified BSD | [Simplified BSD](https://opensource.org/licenses/BSD-2-Clause) | | Standard PIL License | [Standard PIL License](http://www.pythonware.com/products/pil/license.htm) | | ZPL 2.1 | [ZPL 2.1](http://directory.fsf.org/wiki?title=License:ZopePLv2.1) | | Chest License | [Chest License](https://github.com/blaze/chest/blob/master/LICENSE.txt) | | Anaconda License | [Chest License](https://github.com/blaze/chest/blob/master/LICENSE.txt) | **All Licenses** |-----------------------------------------------------------------------------|--------------------------------------------------------------|-------------------------------------------------------------------------------| | | | | | | | | | sphinx | BSD | [BSD](http://asm.objectweb.org/license.html) | | setuptools | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | alabaster | BSD | [BSD](http://asm.objectweb.org/license.html) | | anaconda-client | BSD | [BSD](http://asm.objectweb.org/license.html) | | anaconda-navigator | proprietary - Continuum Analytics, Inc. | [Anaconda License](https://docs.continuum.io/anaconda/eula) | | argcomplete | Apache Software License | [Apache](http://www.apache.org/licenses/LICENSE-1.0.txt) | | astropy | BSD | [BSD](http://asm.objectweb.org/license.html) | | Babel | BSD | [BSD](http://asm.objectweb.org/license.html) | | backports.ssl-match-hostname | BSD | [BSD](http://asm.objectweb.org/license.html) | | backports-abc | PSF | [Python License](https://www.python.org/download/releases/2.7/license/) | | bcolz | BSD | [BSD](http://asm.objectweb.org/license.html) | | beautifulsoup4 | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | binstar | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | bitarray | PSF | [Python License](https://www.python.org/download/releases/2.7/license/) | | blaze | BSD | [BSD](http://asm.objectweb.org/license.html) | | bokeh | New BSD | [New BSD](http://www.opensource.org/licenses/bsd-license.html) | | boto | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | Bottleneck | Simplified BSD | [Simplified BSD](https://opensource.org/licenses/BSD-2-Clause) | | cdecimal | BSD License | [BSD](http://asm.objectweb.org/license.html) | | certifi | ISC | [ISC License](https://opensource.org/licenses/ISC) | | cffi | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | chest | BSD | [BSD](http://asm.objectweb.org/license.html) | | [cloudpickle](https://github.com/ContinuumIO/chest/blob/master/LICENSE.txt) | LICENSE.txt | [Chest License](https://github.com/blaze/chest/blob/master/LICENSE.txt) | | clyent | BSD | [BSD](http://asm.objectweb.org/license.html) | | colorama | BSD | [BSD](http://asm.objectweb.org/license.html) | | comtypes | MIT License | [MIT License](http://choosealicense.com/licenses/mit) | | conda | BSD | [BSD](http://asm.objectweb.org/license.html) | | conda-build | BSD | [BSD](http://asm.objectweb.org/license.html) | | conda-env | BSD | [BSD](http://asm.objectweb.org/license.html) | | conda-manager | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | configobj | BSD | [BSD](http://asm.objectweb.org/license.html) | | cryptography | BSD or Apache License, Version 2.0 | [BSD](http://asm.objectweb.org/license.html) | | cycler | BSD | [BSD](http://asm.objectweb.org/license.html) | | Cython | Apache | [Apache](http://www.apache.org/licenses/LICENSE-1.0.txt) | | cytoolz | BSD | [BSD](http://asm.objectweb.org/license.html) | | dask | BSD | [BSD](http://asm.objectweb.org/license.html) | | datashape | BSD | [BSD](http://asm.objectweb.org/license.html) | | decorator | new BSD License | [New BSD](http://www.opensource.org/licenses/bsd-license.html) | | decorator | BSD license | [BSD](http://asm.objectweb.org/license.html) | | dill | BSD | [BSD](http://asm.objectweb.org/license.html) | | docutils | public domain, Python, 2-Clause BSD, GPL 3 (see COPYING.txt) | [2-Clause BSD](https://opensource.org/licenses/BSD-2-Clause) | | enum34 | BSD License | [BSD](http://asm.objectweb.org/license.html) | | et-xmlfile | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | fastcache | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | Flask | BSD | [BSD](http://asm.objectweb.org/license.html) | | Flask-Cors | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | funcsigs | ASL | [Apache](http://www.apache.org/licenses/LICENSE-1.0.txt) | | futures | BSD | [BSD](http://asm.objectweb.org/license.html) | | gevent | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | gevent-websocket | Copyright 2011-2013 Jeffrey Gelens \ | [Apache](http://www.apache.org/licenses/LICENSE-1.0.txt) | | greenlet | MIT License | [MIT License](http://choosealicense.com/licenses/mit) | | grin | BSD | [BSD](http://asm.objectweb.org/license.html) | | h5py | 3-clause BSD | [3-Clause BSD](https://cloudreach-software.atlassian.net/wiki/3-Clause%20BSD) | | HeapDict | BSD | [BSD](http://asm.objectweb.org/license.html) | | idna | BSD-like | [BSD](http://asm.objectweb.org/license.html) | | ipaddress | Python Software Foundation License | [Python License](https://www.python.org/download/releases/2.7/license/) | | ipykernel | BSD | [BSD](http://asm.objectweb.org/license.html) | | ipython | BSD | [BSD](http://asm.objectweb.org/license.html) | | ipython-genutils | BSD | [BSD](http://asm.objectweb.org/license.html) | | ipywidgets | BSD | [BSD](http://asm.objectweb.org/license.html) | | itsdangerous | BSD | [BSD](http://asm.objectweb.org/license.html) | | jdcal | BSD | [BSD](http://asm.objectweb.org/license.html) | | jedi | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | Jinja2 | BSD | [BSD](http://asm.objectweb.org/license.html) | | jsonschema | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | jupyter | BSD | [BSD](http://asm.objectweb.org/license.html) | | jupyter-client | BSD | [BSD](http://asm.objectweb.org/license.html) | | jupyter-console | BSD | [BSD](http://asm.objectweb.org/license.html) | | jupyter-core | BSD | [BSD](http://asm.objectweb.org/license.html) | | llvmlite | BSD | [BSD](http://asm.objectweb.org/license.html) | | locket | BSD | [BSD](http://asm.objectweb.org/license.html) | | lxml | BSD | [BSD](http://asm.objectweb.org/license.html) | | MarkupSafe | BSD | [BSD](http://asm.objectweb.org/license.html) | | matplotlib | BSD | [BSD](http://asm.objectweb.org/license.html) | | menuinst | BSD | [BSD](http://asm.objectweb.org/license.html) | | mistune | BSD | [BSD](http://asm.objectweb.org/license.html) | | mock | BSD | [BSD](http://asm.objectweb.org/license.html) | | mpmath | BSD | [BSD](http://asm.objectweb.org/license.html) | | multipledispatch | BSD | [BSD](http://asm.objectweb.org/license.html) | | nbconvert | BSD | [BSD](http://asm.objectweb.org/license.html) | | nbformat | BSD | [BSD](http://asm.objectweb.org/license.html) | | networkx | BSD | [BSD](http://asm.objectweb.org/license.html) | | nltk | Apache License, Version 2.0 | [Apache 2.0](http://www.apache.org/licenses/LICENSE-2.0) | | nose | GNU LGPL | [GNU GPL License](https://www.gnu.org/licenses/gpl-3.0.en.html) | | notebook | BSD | [BSD](http://asm.objectweb.org/license.html) | | numba | BSD | [BSD](http://asm.objectweb.org/license.html) | | numexpr | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | numpy | BSD | [BSD](http://asm.objectweb.org/license.html) | | odo | BSD | [BSD](http://asm.objectweb.org/license.html) | | openpyxl | MIT/Expat | [MIT License](http://choosealicense.com/licenses/mit) | | pandas | BSD | [BSD](http://asm.objectweb.org/license.html) | | partd | BSD | [BSD](http://asm.objectweb.org/license.html) | | path.py | MIT License | [MIT License](http://choosealicense.com/licenses/mit) | | patsy | 2-clause BSD | [2-Clause BSD](https://opensource.org/licenses/BSD-2-Clause) | | pep8 | Expat license | [Expat License](http://choosealicense.com/licenses/mit/) | | pickleshare | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | Pillow | Standard PIL License | [Standard PIL License](http://www.pythonware.com/products/pil/license.htm) | | pip | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | ply | BSD | [BSD](http://asm.objectweb.org/license.html) | | psutil | BSD | [BSD](http://asm.objectweb.org/license.html) | | psycopg2 | LGPL with exceptions or ZPL | [LGPL with Exceptions](http://www.gnu.org/licenses/lgpl-2.1.html) | | py | MIT license | [MIT License](http://choosealicense.com/licenses/mit) | | pyasn1 | BSD | [BSD](http://asm.objectweb.org/license.html) | | pycosat | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | pycparser | BSD | [BSD](http://asm.objectweb.org/license.html) | | pycrypto | Public-Domain | N/A | | pyflakes | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | Pygments | BSD License | [BSD](http://asm.objectweb.org/license.html) | | pyOpenSSL | APL2 | [Apache 2.0](http://www.apache.org/licenses/LICENSE-2.0) | | pyparsing | MIT License | [MIT License](http://choosealicense.com/licenses/mit) | | pyreadline | BSD | [BSD](http://asm.objectweb.org/license.html) | | pytest | MIT license | [MIT License](http://choosealicense.com/licenses/mit) | | python-dateutil | Simplified BSD | [Simplified BSD](https://opensource.org/licenses/BSD-2-Clause) | | pytz | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | pywin32 | PSF | [Python License](https://www.python.org/download/releases/2.7/license/) | | PyYAML | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | pyzmq | LGPL+BSD | [LGPL License](http://www.gnu.org/licenses/lgpl-2.1.html) | | QtAwesome | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | qtconsole | BSD | [BSD](http://asm.objectweb.org/license.html) | | QtPy | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | requests | Apache 2.0 | [Apache 2.0](http://www.apache.org/licenses/LICENSE-2.0) | | rope | GNU GPL | [GNU GPL License](https://www.gnu.org/licenses/gpl-3.0.en.html) | | ruamel-yaml | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | runipy | BSD | [BSD](http://asm.objectweb.org/license.html) | | scikit-image | Modified BSD | [Modified BSD](http://asm.objectweb.org/license.html) | | scikit-learn | new BSD | [New BSD](http://www.opensource.org/licenses/bsd-license.html) | | scipy | BSD | [BSD](http://asm.objectweb.org/license.html) | | simplegeneric | ZPL 2.1 | [ZPL 2.1](http://directory.fsf.org/wiki?title=License:ZopePLv2.1) | | singledispatch | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | six | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | snowballstemmer | BSD | [BSD](http://asm.objectweb.org/license.html) | | sockjs-tornado | Copyright (C) 2011 Serge S. Koval | [Apache](http://www.apache.org/licenses/LICENSE-1.0.txt) | | sphinx-rtd-theme | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | spyder | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | SQLAlchemy | MIT License | [MIT License](http://choosealicense.com/licenses/mit) | | statsmodels | BSD License | [BSD](http://asm.objectweb.org/license.html) | | sympy | BSD | [BSD](http://asm.objectweb.org/license.html) | | [toolz](http://www.opensource.org/licenses/bsd-license.php) | BSD | [BSD](http://asm.objectweb.org/license.html) | | tornado | Apache | [Apache](http://www.apache.org/licenses/LICENSE-1.0.txt) | | [traitlets](http://www.apache.org/licenses/LICENSE-2.0) | BSD | [BSD](http://asm.objectweb.org/license.html) | | ujson | BSD License | [BSD](http://asm.objectweb.org/license.html) | | unicodecsv | BSD License | [BSD](http://asm.objectweb.org/license.html) | | Werkzeug | BSD | [BSD](http://asm.objectweb.org/license.html) | | wheel | MIT | [MIT License](http://choosealicense.com/licenses/mit) | | xlrd | BSD | [BSD](http://asm.objectweb.org/license.html) | | XlsxWriter | BSD | [BSD](http://asm.objectweb.org/license.html) | | xlwings | BSD 3-clause | [3-Clause BSD](https://cloudreach-software.atlassian.net/wiki/3-Clause%20BSD) | | xlwt | BSD | [BSD](http://asm.objectweb.org/license.html) | | xlwt: | BSD | [BSD](http://asm.objectweb.org/license.html) | --- language: "en" --- # Canvas - Application View ## Application View in Migration Planner To access the Application View from the Main Dashboard, 1. Log in to the console 2. Once logged into the console, you will see a home page with the icons as shown below- ![Screenshot 2026-07-22 at 1.08.22 PM-20260722-073857.png](https://support.cloudamize.com/__attachments/a_8a6fbedc8f09160f6febdab8b75bd3f2e67b455b236943bab9a3a7796245de56/Screenshot%202026-07-22%20at%201.08.22%E2%80%AFPM-20260722-073857.png?cb=76c65137fc56f1493e5553830e531a4a) 3. Click on "Plan," which will navigate you to the page below, and then select the "Application Canvas". ![Screenshot 2025-03-12 at 11.49.04 AM-20250312-062118.png](https://support.cloudamize.com/__attachments/a_ab6a1a7dd8682a82efef0a5ba2f7394e88dc875ae8e805006afa649be1454be5/Screenshot%202025-03-12%20at%2011.49.04%E2%80%AFAM-20250312-062118.png?cb=a8a73993bd8f3b451830c1d68fb68bdb) ![Screenshot 2025-03-12 at 11.46.42 AM-20250312-061746.png](https://support.cloudamize.com/__attachments/a_d9b3e9d1474d0b0aa246cc42a4a810ba736b14827dabcf101a227a8fedc0172c/Screenshot%202025-03-12%20at%2011.46.42%E2%80%AFAM-20250312-061746.png?cb=ef530681344415d7eb88143660b8a783) **Note**: The Machine and Application View in Migration Planner are available as shown in the above screenshot. To expand the view of applications,'Click' on the 'Plus' button in the center of the canvas. ![image-20220112-200502.png](https://support.cloudamize.com/__attachments/a_ab0a6edef43286e601c53877e4ff4a4d14d4a7bdc036b159166ecfbbe60b2c1c/image-20220112-200502.png?cb=5e5ce38414ddfdabe77916f6cf4f6254) A list of applications will be displayed in their default groupings. To view more information on the application, click on the icon. ![image-20220112-200508.png](https://support.cloudamize.com/__attachments/a_06cb6162204840aa8ca6e12cdce98431ed28528fd33ac52d3498b991adf4da17/image-20220112-200508.png?cb=22f081272bb8decf5e500f1772818b8f) A summary of the application will be displayed on the right side of the page. This information will include the application information as well as the host on which the application was discovered. ![image-20220112-200515.png](https://support.cloudamize.com/__attachments/a_6c23a980f642732d7067967a502a1a076aad05ac4f9379145c6008a208b78557/image-20220112-200515.png?cb=b0dde9caf3fd64b53b211c3e1570abd3) 'Click' on the icon under 'Application Info' to display the application description, application category, vendor, and links to more information. ![image-20220112-200521.png](https://support.cloudamize.com/__attachments/a_0e0af748c1e78451d69e2eb697dc71af2cb4160f23ab55edade5d66a8e5a0896/image-20220112-200521.png?cb=c29945fafca15b7575411c8f54a41f93) ### Automated Application Grouping The left-hand panel in the application view groups the applications in various ways: * Commercial off-the-shelf software (COTS) applications, such as SharePoint, Citrix, VMware, Symantec, and many others, are used to identify well-known apps from patterns and processes that have been captured in our application library. * Non-COTS software is identified by the types of processes and patterns of communication, indicating that the processes are working together as a single application or application component. These applications are labeled 'App 0', 'App 1', 'App 2', etc., in the left-hand panel. * The remaining applications are identified by which processes appear to be working together to form an application or application component. These applications are labeled 'Apps on machine_name'. Our software searches for well-known patterns in components like web servers and databases and then analyzes the processes that interact with them to determine if they can likely be considered a part of a larger application. ![image-20220112-200526.png](https://support.cloudamize.com/__attachments/a_d891dcd863e5d508df007e013742c2d60f5c0371bc27901b55cce3e4fc4117cf/image-20220112-200526.png?cb=08409cf0fc48e30d00a8c8c66af0e5ce) If you have any queries, please get in touch with the helpdesk via our [++Helpdesk Portal++](https://cloudreach-software.atlassian.net/servicedesk/customer/portal/9) or by email at [++helpdesk@cloudamize.com++](mailto:helpdesk@cloudamize.com). --- language: "en" --- # Assess ## Unique Licenses |------------------------------------------------------------------------------------------------------------------------| | [Apache License, Version 2.0](http://www.gwtproject.org/terms.html) | | [Highsoft Standard License Agreement 7.0](https://shop.highsoft.com/media/highsoft/Standard-License-Agreement-7.0.pdf) | | | | [++MIT License++](http://www.opensource.org/licenses/mit-license.php) | | [GPL version 2](https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html) | | | |-----------------------|---------|----------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------| | Library | Version | type | license | | GWT | 2.5.1 | JS | [Apache License, Version 2.0](http://www.gwtproject.org/terms.html) | | Highcharts | 2.0.1 | JS Chart | [Highsoft Standard License Agreement 7.0](https://shop.highsoft.com/media/highsoft/Standard-License-Agreement-7.0.pdf) | | jQuery | 1.9.1 | JS | | | moment | 2.9.0 | JS | [++MIT License++](http://www.opensource.org/licenses/mit-license.php) | | jquery.nicescroll | 3.2.0 | JS | [++MIT License++](http://www.opensource.org/licenses/mit-license.php) | | jquery.onoff | 0.3.1 | JS | [++MIT License++](http://www.opensource.org/licenses/mit-license.php) | | jScrollPane | 2.0.14 | JS | Dual licensed under the [MIT](http://www.opensource.org/licenses/mit-license.php) or [GPL version 2](https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html) | | jQuery Tooltip plugin | 1.3 | JS | Dual licensed under the [MIT](http://www.opensource.org/licenses/mit-license.php) or [GPL version 2](https://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html) | | jQuery ZeroClipboard | 1.1.1 | JS | [++MIT License++](http://www.opensource.org/licenses/mit-license.php) | | yFiles | 1.2 | JS | | --- language: "en" --- # Assessment Summary The **Assessment Summary Report** is a downloadable **PDF report** available in the **Assessment Reports** section. This report provides an executive overview of the cloud migration assessment. It condenses key findings, **TCO projections, workload sizing, and optimization opportunities**, offering strategic insights for cloud adoption. Steps to navigate to the **OLA Assessment Summary Report:** 1. Log in to the console 2. Navigate to the Analyze page of your completed assessment. 3. Click the View Details button beside your AWS results. 4. Click the Reports tab on the right-hand side of the screen to see the following: ![Screenshot 2025-07-10 at 7.34.01 PM-20250710-140430.png](https://support.cloudamize.com/__attachments/a_28727c308da5250e9bbe7a5cb72f8604e06849e4023363cf824b65aaa44f6e79/Screenshot%202025-07-10%20at%207.34.01%E2%80%AFPM-20250710-140430.png?cb=ffb228acc28aea8a3b69e803f47f15f4) Analyze \> AWS View Details \> Reports \| Showing the Assessment Summary Report | **Slide Name** | **Description** | |-------------------------------------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Assessment Overview** | This slide summarizes the Cloudamize discovery and assessment project. It outlines the total number of servers assessed and the methodology used for data collection. Key infrastructure details are provided, including a breakdown of Windows and Linux servers. The overview also covers resource metrics, such as storage utilization and the number of applications discovered, highlighting those designated as business applications. This report provides a quick snapshot of the project scope and key findings. | | **Financial Overview** | This section summarizes the cost savings from your cloud migration strategy. It provides a financial overview of how **Infrastructure Modernization** , **Licensing Optimization** , and a **Savings Plan Commitment** can significantly reduce your Total Cost of Ownership (TCO). By right-sizing your resources and leveraging cost-effective licensing, this analysis projects your potential savings over a multi-year period, allowing for data-driven decisions on your cloud spend. **Designs:** **On-Demand \| Shared Tenancy Hardware / Lift \& Shift:** The cost of a "lift-and-shift" migration, where your on-premise hardware configuration is moved to an equivalent, unoptimized AWS instance on a shared server. **On-Demand \| Shared Tenancy \| Right-Sized \| No Upfront:** Pay-as-you-go pricing for right-sized instances, optimized for cost based on actual workload performance, with no long-term commitment. **1-Year RI \| Shared Tenancy \| Right-Sized \| No Upfront**: Commits to a right-sized instance for one year, providing significant discounts over on-demand rates without an initial payment. **3-Year RI \| Shared Tenancy \| Right-Sized \| No Upfront:** Commits to a right-sized instance for three years, offering the deepest available discounts for stable, long-running workloads. | | **Potential Savings with Graviton** | The Graviton family of ARM64 processors offers a significant opportunity to improve performance and reduce costs on AWS. By rehosting or replatforming your compatible workloads to Graviton instances, you can achieve a better price-performance ratio compared to traditional x86-based instances. This optimization can lead to substantial reductions in your ongoing compute costs without compromising application performance. This analysis identifies Linux servers that are compatible with Graviton processors, a compatibility that most modern Linux operating systems now support. It then projects the cost savings by comparing your current non-Graviton costs with the projected Graviton costs. The goal is to realize a total estimated annual savings of around 10% by making this switch. | | **VMware Licensing Analysis, On-Premise Licensing Cost Estimate** | This slide estimates your on-premises VMware licensing costs to build a comprehensive Total Cost of Ownership (TCO) analysis. The report provides a clear breakdown of estimated costs for different VMware editions over various term lengths, based on your specific environment's hosts and licensed cores. The analysis then compares this total on-premises TCO (including infrastructure and licensing) with the projected costs of migrating to AWS EC2. It highlights the substantial cost reduction by eliminating VMware licensing fees in the cloud and quantifies the potential savings from moving a specific number of VMs. This provides a clear financial justification for migrating to an optimized cloud environment. | | **SQL Server Optimization and Core Reduction** | This section outlines how Cloudamize helps reduce your SQL Server licensing costs by optimizing core count. By right-sizing your instances and leveraging AWS's "Optimize CPU" feature for Bring-Your-Own-License (BYOL) scenarios, you can free up valuable licenses for use on other servers. This strategy not only generates immediate savings on Software Assurance renewals but also provides a clear financial benefit by reducing the number of licensable cores you need in the cloud. Non-prod machines could use SQL Server Developer Edition, which has no license cost. | | **Storage Analysis** | This section details your storage requirements and projected costs. It compares the Total Disk Capacity with your actual Total Disk Occupancy to provide an initial TCO based on 100% utilization. For further optimization, Cloudamize can also model shared storage solutions like Amazon FSx for Windows File Server, allowing you to customize your TCO with additional storage headroom and leverage fully managed services. | | **Microsoft EOL (End-of-Life) Analysis** | This section identifies all Microsoft operating systems and software in your environment that are nearing or have passed their End-of-Life (EOL) date. Running EOL software exposes your organization to significant security vulnerabilities and a lack of vendor support. This analysis helps you prioritize which workloads require immediate modernization or re-platforming, ensuring you migrate to a secure, compliant, and supported cloud environment. The report provides a clear breakdown of your environment's risk level by specifying the **support cycle and end dates for both Windows Server and SQL Server versions.** It also helps you identify servers that are **unsupported and represent a high risk**, allowing you to make data-driven decisions to mitigate these risks as part of your cloud migration strategy. | | **AWS End-of-Life Migration Program (EMP)** | The AWS End-of-Life Migration Program (EMP) is a dedicated service that provides tools, expert guidance, and funding to help you migrate legacy applications and databases to the AWS cloud. By simplifying the process of moving software that is no longer supported by its vendor, the EMP significantly reduces the cost, complexity, and risk of modernizing your critical workloads. | | **Modernization Options** | **Amazon RDS as a Migration Option** Migrating to Amazon RDS allows your team to focus on innovation by offloading the time-consuming tasks of database management and administration. With features like automated patching, backups, and high availability, RDS improves both database and infrastructure efficiency while decreasing capital and operational expenses. It provides easy scalability and built-in durability, allowing you to move your databases without complex re-architecting. The pricing shown in this analysis compares the cost of a 1-year EC2 Reserved Instance with RDS Standard On-Demand rates. **Migration \& Modernization Journey:** The Cloudamize Migration \& Modernization Journey provides a data-driven path from on-premises to the cloud. It begins with Infrastructure Modernization, where you rehost your workloads with confidence and control, using Cloudamize to right-size your infrastructure for immediate cost savings. The journey continues with Application Modernization, where the platform continually provides recommendations to optimize your cloud environment. This includes suggestions for moving COTS software to open-source alternatives, leveraging AWS-optimized and managed services, and adopting cloud-native solutions to further reduce your cost of compute and improve efficiency. | | **Business Value** | **Sustainability** Cloudamize helps you understand the environmental impact of your cloud migration by estimating your current on-premises carbon footprint based on key metrics like CPU utilization, disk capacity, and uptime. It then calculates the reduced carbon footprint associated with your modernized plan in AWS, providing a clear comparison. You can download a full sustainability report from the Cloudamize console to help inform your green initiatives and explore potential carbon reduction incentives. **Zombie Server Analysis** This section identifies "zombie servers," which are machines that are powered on but have had less than 20% resource utilization throughout the assessment period. These servers represent an unnecessary cost, and we recommend investigating their purpose to confirm they are truly unused. You can use the Cloudamize Plan component to review all application dependencies and confirm if a server is safe to decommission, or you can remove them from the assessment scope to get a more accurate TCO. | | **Cloudamize Platform Overview** | **Discover:** Cloudamize uses three standard data collection methods (agent, agentless, and hypervisor-level) to gather in-depth insights into your on-premises environment. It also offers advanced telemetry for specific technologies, such as SQL and NetApp, to provide a detailed view of your infrastructure, performance, and application dependencies. More details are available in our KB [here](https://support.cloudamize.com/kb/inventory-settings). **Analyze:** This component allows you to explore multiple Total Cost of Ownership (TCO) plans, including customized scenarios. It helps you understand the financial impact of your migration and can show how to reduce your "lift-and-shift" costs by over 50% by leveraging data-driven right-sizing recommendations. More details are available in our KB [here](https://support.cloudamize.com/kb/viewing-interpreting-results). **Plan** The Plan module helps you intelligently prepare for migration. It automatically maps all application and server dependencies, enabling you to group workloads logically by application, migration wave, or the "7 R's" (Rehost, Replatform, etc.). This ensures a smooth and low-risk migration. More details are available in our KB [here](https://support.cloudamize.com/kb/plan). **Migrate:** This is where planning becomes execution. The Migrate module streamlines the process by helping you connect to the cloud, replicate servers, and apply the right-sizing recommendations you defined during the analysis phase, all from within the Cloudamize console. More details are available in our KB [here](https://support.cloudamize.com/kb/ima-intelligent-migration-assistance). **Manage:** The Manage component provides tools to orchestrate and track your entire migration project. It allows you to create Runbooks to organize and coordinate all of your team's assessment, planning, and migration activities, ensuring a structured and controlled process. More details are available in our KB [here](https://support.cloudamize.com/kb/runbooks). **Modernize:** Cloudamize's journey doesn't end with migration. The Modernize component offers continuous, real-time in-cloud recommendations to optimize your cloud environment as you grow. These recommendations can help you further reduce costs and improve performance by suggesting new services or better configurations. More details are available in our KB [here](https://support.cloudamize.com/kb/cloudamize-modernize). | Sample Report for **AWS-OLA** Assessment Summary: [Assessment Summary Report.pdf](https://support.cloudamize.com/__attachments/a_bf83ec7aaaeb7c09dd24a1afbb26750952497f082e2b332fb3747b2ae93d8dae/Assessment%2520Summary%2520Report.pdf.md?cb=85ddf7a91440d0afb3bfc60932bb8990) Sample Report for **Non AWS-OLA** Assessment Summary: [Assessment_Summary.pdf](https://support.cloudamize.com/__attachments/a_6b19f07c0cba8d71334d0a26f35da008504e47603fb812fc1fdf0294e8963a76/Assessment_Summary.pdf.md?cb=0240e3593f6f810760e1ebbf44e4a779) If you have any queries, please get in touch with the helpdesk via our [++Helpdesk Portal++](https://cloudreach-software.atlassian.net/servicedesk/customer/portal/9) or by email at [++helpdesk@cloudamize.com++](mailto:helpdesk@cloudamize.com). --- language: "en" --- # Assets ## Assets This article provides guidelines for navigating and using the Asset tabs page within your assessment. We can create and edit new asset groups within the Assets tab. Asset groups allow for easy management of a group of machines during data collection and within the Migration Planner. To create a new asset group, enter a name, toggle whether it should be in scope or excluded, and then click Add. ![Screenshot 2025-03-11 at 12.19.00 PM-20250311-064925.png](https://support.cloudamize.com/__attachments/a_b3f90270093ac7f8d909ae12ff428767c454289cba8d68a216c4d68fd629268b/Screenshot%202025-03-11%20at%2012.19.00%E2%80%AFPM-20250311-064925.png?cb=fbb1a63844d7022d2e9d5dc2a34a7cc8) Assets tab ![Screenshot 2025-09-09 at 3.05.47 PM-20250909-093804.png](https://support.cloudamize.com/__attachments/a_ca5d21cde66714ef76ee50179e0e925a0ff46b138e07dd3df665eb1d3c8d9a67/Screenshot%202025-09-09%20at%203.05.47%E2%80%AFPM-20250909-093804.png?cb=80850967f725ce165215835a499bf7e9) Asset groups can be edited or deleted by clicking the three dots and selecting the appropriate option. ![Screenshot 2024-03-11 at 13.56.47.png](https://support.cloudamize.com/__attachments/a_0edd91e2b4abe67ac089f1b7abfdb1bc43af0f92a414c35c54c2e4e3171ed7cd/Screenshot%202024-03-11%20at%2013.56.47.png?cb=ff0d4b4678c095993417aa399ac47006) Edit or Delete Options If you have any queries, please get in touch with the helpdesk via our [++Helpdesk Portal++](https://cloudreach-software.atlassian.net/servicedesk/customer/portal/9) or by email at [++helpdesk@cloudamize.com++](mailto:helpdesk@cloudamize.com). --- language: "en" --- # AWS Bring Your Own License ## Introduction Cloudamize now includes the ability to calculate savings associated with moving workloads to the Amazon Web Service cloud without any additional software licensing fees. For customers with License Mobility through Software Assurance, Cloudamize can now show you the potential cost savings by bringing your own licenses. ### *Note: SQL Data is only captured using agents and the agentless data collector. This feature is not available for nodes assessed with vCenter-only and Hyper-V-only installations.* ## License Cost After launching the Cloudamize platform, license cost for all AWS assessments will be reflected in the **Infrastructure Summary** chart in the center of the Assess Dashboard. This summary information provides you with the **total SQL license cost for all assessed machines** (1) as well as the **annual cost including licenses** (2). ![image-20220112-193341.png](https://support.cloudamize.com/__attachments/a_4fa96c3dd5b2b7bbd38bad63c40dc59791d9c33b2e2d938425dd13cfbc624060/image-20220112-193341.png?cb=05506dc22adba1aaaad1c8c9e5965ab1) ## Licensing information can also be found under the **Compute** tab. Here Cloudamize provides two new columns: **Cost with License** and **Cost w/o License** . Information provided is as follows: ## Cost with License 1. **Total Annualized Cost** - This is the sum of the Annual Hourly Cost and the Upfront Cost over the Duration of the Reserved Instance. Reserved Instance durations are set at one year or three years. 2. **Annual Hourly Cost** - The hourly Reserved Instance cost remaining after Upfront Costs are paid. 3. **Upfront Cost** - The amount of the Reserved Instance cost paid Upfront. 4. **License Cost** - The cost of the SQL license. 5. **Annual Dedicated Instance Fees** - Total cost of the dedicated per region fee. 6. **Region** - The AWS region selected for the assessment. 7. **Pricing Plan** - The selected pricing plan for the assessment. 8. **License Mobility through SA** - Details whether or not License Mobility has been applied. Values for this column are as follows: 1. **N.A.** 2. **Not Applied** 3. **Applied** 9. **License Cost Reason**- Details the reason why License Mobility was or was not applied. Values for this column are as follow: 1. **N.A.** 10. **License Mobility through SA is Applied** 11. **License Mobility through SA is Not Applied** ## Cost w/o License 1. **Total Annualized Cost** - This is the sum of the Annual Hourly Cost and the Upfront Cost over the Duration of the Reserved Instance. Reserved Instance durations are set at one year or three years. 2. **Annual Hourly Cost** - The hourly Reserved Instance cost remaining after Upfront Costs are paid. 3. **Upfront Cost** - The amount of the Reserved Instance cost paid Upfront. 4. **Annual Dedicated Instance Fees** - Total cost of the dedicated per region fee. 5. **Region** - The AWS region selected for the assessment. 6. **Pricing Plan** - The selected pricing plan for the assessment. ## License Tab The **License** tab provides a quick glance look at all the same information found under the **Cost with License** columns found under the **Compute**tab. ## Designer ### Pricing Plan Using the Designer, Cloudamize allows you to build custom scenarios to view the costs and potential savings associated with a range of AWS Instance options. 1. **Multi-Tenant SQL Server License Mobility through SA**: View the savings associated with BYOL licenses to standard, Multi-Tenant EC2 Instances as part of the customer's current Software Assurance agreement. 2. **Dedicated Instance**: View the cost and performance of moving the selected machine to a Dedicated Instance within AWS. 3. **Dedicated Instance with BYOL**: View the savings associated with BYOL MSDN or SQL licenses to Dedicated Instances in AWS. 4. **Dedicated Host with SQL**: View the savings associated with BYOL MSDN or SQL licenses to Dedicated Hosts in AWS. ![image-20220112-193354.png](https://support.cloudamize.com/__attachments/a_a1a8c4b043e86b066138ea7a54aeb0716f36ada14e5c0e24dfc3aa2f4371aac7/image-20220112-193354.png?cb=f9b2d794bf6fc8d1620feb77b321662e) ### License Optimization ![image-20220112-193409.png](https://support.cloudamize.com/__attachments/a_3dff7b21ccfb246296a9669f9129264a750511090838f4896221ecc588d0bc86/image-20220112-193409.png?cb=f8d4b74bf01c70b3123d8b0d9076c346) Optimize the cost and performance of the assessed infrastructure by reducing the number of hardware threads and/or disabling Hyperthreading where possible. This, in turn, can lead to a decrease in Compute costs while ensuring any SQL licensing requirements are met. 1. **Optimize Cost and Reduce Number of Threads**: Reduce the number of hardware threads or disable hyperthreading to lower cost will still ensuring the necessary performance benchmarks are met. 2. **Optimize Number of Threads**: Suggests an instance with the fewest number of hardware threads necessary to meet the performance needs of the assessed workload. 3. **Disable Hyperthreading**: Will only recommend instances where Hyperthreading is disabled by default. Useful in scenarios where a customer is concerned about any potential security issues related to Hyperthreading. ### Pricing Plan Cloudamize now includes a range of new pricing plans including all Reserved Instance 1-year and 3-year options currently available from AWS. ## Advanced Filtering Two new filters allow you to gain deeper insight into the assessed infrastructure and further ensure that migrations are as efficient and cost-effective as possible. 1. **BYOL for Microsoft Software**: Searches for all machines with applications installed that are covered under Amazon's BYOL license program including the following: 2. Microsoft Exchange Server 3. Microsoft SharePoint Server 4. Microsoft SQL Server 5. Microsoft System Center 6. Microsoft Remote Desktop Services 7. Microsoft Skype for Business Server 8. Microsoft Dynamics products 9. Microsoft BizTalk Server 10. **SQL With Less Than 4 Threads**: Searches for all machines running SQL server where the number of observed CPU threads is less than four. These machines are candidates for further optimization to lower SQL license cost. *** ** * ** *** ## SQL Server and License Usage ![image-20220112-193447.png](https://support.cloudamize.com/__attachments/a_97ff5809173c3f050d374d5af67c9a96e89970ba4f0384fc163dabd70410b616/image-20220112-193447.png?cb=681558e7c32ececa4fb2496453bc1511) Using the Migration Planner, Cloudamize now provides a more in-depth look at the SQL servers found in the assessed infrastructure. The information provided within the SQL Server and License Usage machine allows you to gain further insight into the on-premise licensing data and view a comparison of host-based versus VM-based SQL licensing. This new feature also provides an overview of necessary on-cloud SQL licensing. ### SQL Server Provides a breakdown of the SQL instances assessed and provides an overview including the number of licenses utilized and SQL database information such as size, edition, version, location, and more. ### On-Cloud License Usage Provides a breakdown of license usage on-cloud including information such as the On-Cloud Instance Type, Number of Hardware Threads, SQL Edition, and whether or not the SQL license is part of the BYOL program. ### On-Premise Physical View how many SQL licenses are needed on-cloud based on the observed on-premise configuration and Cloudamize recommended cloud instances. The chart also includes information such as the Number of Hardware Threads, CPU information, and Number of Required SQL Enterprise of Standard licenses. This chart also informs you as to whether or not any of the following services are running: 1. **SQL Server Analysis Services** 2. **SQL Server Integration Services** 3. **SQL Server Report Services** 4. **SQL Server Master Data Services** ### On-Premise VMware View how many SQL licenses are needed on-cloud based on the observed on-premise VMware configuration and Cloudamize recommended cloud instances. The chart also includes information such as the Number of Hardware Threads, CPU information, and Number of Required SQL Enterprise of Standard licenses. Also provided is a summary of the VM-based and host-based SQL licenses broken down by Standard and Enterprise editions. This chart also informs you as to whether or not any of the following services are running: 1. **SQL Server Analysis Services** 2. **SQL Server Integration Services** 3. **SQL Server Report Services** 4. **SQL Server Master Data Services** ### On-Premise HyperV View how many SQL licenses are needed on-cloud based on the observed on-premise Hyper-V configuration and Cloudamize recommended cloud instances. The chart also includes information such as the Number of Hardware Threads, CPU information, and Number of Required SQL Enterprise of Standard licenses. Also provided is a summary of the VM-based and host-based SQL licenses broken down by Standard and Enterprise editions. This chart also informs you as to whether or not any of the following services are running: 1. **SQL Server Analysis Services** 2. **SQL Server Integration Services** 3. **SQL Server Report Services** 4. **SQL Server Master Data Services** If you have any queries, please get in touch with the helpdesk via our [++Helpdesk Portal++](https://cloudreach-software.atlassian.net/servicedesk/customer/portal/9) or by email at [++helpdesk@cloudamize.com++](mailto:helpdesk@cloudamize.com). --- language: "en" --- # AWS Fleet Deployment: Cloudamize Agent Installation via SSM Run Command ## Overview This Knowledge Base article provides a step-by-step guide on how to perform mass, non-interactive installations of the Cloudamize Agent across your EC2 fleet using **AWS Systems Manager (SSM) Run Command**. AWS Systems Manager Run Command allows you to remotely and securely manage the configuration of your managed instances without requiring direct SSH/RDP access, bastion hosts, or open inbound ports. By utilizing SSM Run Command alongside Cloudamize's silent installation scripts, administrators can rapidly deploy the Cloudamize inventory agent across hundreds of Linux and Windows EC2 instances simultaneously. **Note:** The AWS Systems Manager Run Command steps in this article are provided as guidance for using third-party deployment tooling with the Cloudamize Agent. Cloudamize has not validated or tested these AWS deployment workflows end to end. Review and test the process in your own AWS environment before using it for production deployments. ### Prerequisites Before deploying the Cloudamize Agent across your AWS fleet, verify that all target nodes comply with the official [Cloudamize Agent Installation Prerequisites](https://support.cloudamize.com/kb/agent-installation-prerequisites) and meet the following AWS-specific requirements: * **Official Cloudamize Prerequisites:** Review OS compatibility, system resource requirements, and regional proxy/endpoint settings in the [Agent Installation Prerequisites KB](https://support.cloudamize.com/kb/agent-installation-prerequisites). * **Network \& Outbound Access:** Target instances must have outbound access on **TCP Port 443** directly or via proxy to your assigned Cloudamize regional endpoint: * **US Region:** `am.cloudamize.com` * **EU Region:** `am-de.cloudamize.com` * **UAE Region:** `am-ae.cloudamize.com` * **SSM Agent:** Target EC2 instances must have `amazon-ssm-agent` installed and running (pre-installed on most standard AWS AMIs). * **IAM Permissions:** Target EC2 instances must have an IAM role attached with the `AmazonSSMManagedInstanceCore` policy attached. * **Network Access:** Target instances must have outbound HTTPS access on **TCP Port 443** to `am.cloudamize.com` (or your regional Cloudamize endpoint). * **Customer Key:** Ensure you have your unique Cloudamize Customer Key from the [Cloudamize Console](https://console.cloudamize.com/). ### Step-by-Step Installation Instructions #### Step 1: Open AWS Systems Manager Run Command 1. Log in to the **AWS Management Console**. 2. Search for and select **Systems Manager**. 3. In the left navigation menu under **Node Management** , choose **Run Command**. 4. Click the **Run command** button at the top right of the page. ##### Step 2: Select the Execution Document In the **Command document** search box: * For **Linux instances** , search and select: `AWS-RunShellScript` * For **Windows instances** , search and select: `AWS-RunPowerShellScript` ##### Step 3: Configure Command Parameters **Important Note on Region Endpoints \& Customer Keys:** The installer URL domain and custkey / customerkey parameters depend on the specific region where your Cloudamize assessment is provisioned (e.g., US, EU, or UAE) and your unique account credentials. Always copy the exact command and key directly from your Cloudamize Console. In the **Command parameters** box, paste the non-interactive installation script matching your target operating system. Replace `` with your actual key. #### For Linux Fleet (`AWS-RunShellScript`): #!/bin/bash # Download and execute official Cloudamize Agent Installer sh <(curl 'https://am.cloudamize.com/cxf/downloadFileV3?custkey=&filename=installCloudamizeAgentV2.sh' -L) (Replace `am.cloudamize.com` with your regional endpoint domain if using EU or UAE, and replace `YOUR_CUSTOMER_KEY` with your actual Customer Key). #### For Windows Fleet (`AWS-RunPowerShellScript`): #PowerShel # Download and silently install Cloudamize Agent MSI $msiPath = "$env:TEMP\cloudamizeAgent.msi" Invoke-WebRequest -Uri "https://am.cloudamize.com/cxf/downloadFileV3?custkey=&filename=cloudamizeAgent.msi" -OutFile $msiPath msiexec /i $msiPath customerkey=YOUR_CUSTOMER_KEY / (Replace `am.cloudamize.com` with your regional endpoint domain if using EU or UAE, and replace `YOUR_CUSTOMER_KEY` with your actual Customer Key). ##### Step 4: Target Instances Under the **Targets** section, select how you want to target your EC2 fleet: * **Specify instance tags:** (Recommended for scale) Target instances using tag key-value pairs (e.g., `Key: Environment, Value: Production`). * **Choose instances manually:** Manually select specific EC2 instances from the list. * **Choose a resource group:** Target instances belonging to a specific AWS Resource Group. ##### Step 5: Output Options \& Execution 1. *(Optional)* Under **Output options** , choose to write standard output and error logs to an **S3 Bucket** or **CloudWatch Logs** group for auditing. 2. Click **Run** to initiate deployment across the selected fleet. ### Verification \& Monitoring Once execution completes, verify the installation status across your targets: 1. In the SSM Console, navigate to **Run Command** and select the command execution ID to view the per-instance execution status (`Success` or `Failed`). 2. Verify agent services on target nodes: * **Linux:** Run `systemctl status cloudamize-agent` * **Windows:** Check services for `Cloudamize Agent Service` 3. Log in to the [Cloudamize Console](https://console.cloudamize.com/) and confirm that the newly registered instances appear in your node list. Frequently Asked Questions **Why are some instances not showing up in the target list?** Instances must have the SSM Agent active and possess an IAM role with `AmazonSSMManagedInstanceCore` attached. If offline or missing permissions, they will not appear as SSM managed nodes. **Can I automate this for newly launched EC2 instances?** Yes. To automatically enforce Cloudamize Agent installation on new or auto-scaled instances, use **AWS SSM State Manager** instead of Run Command to apply the policy on an automated schedule or event trigger. **Do I need SSH/RDP ports open for this installation?** No. AWS SSM communicates over outbound HTTPS (Port 443) to AWS SSM endpoints. No inbound SSH or RDP ports need to be open on your security groups. If you have any queries, please get in touch with the helpdesk via our [++Helpdesk Portal++](https://cloudreach-software.atlassian.net/servicedesk/customer/portal/9) or by email at [++helpdesk@cloudamize.com++](mailto:helpdesk@cloudamize.com). --- language: "en" --- # AWS FSx for Windows File Server(FSxW) The AWS FSx service is a fully managed, high-performance file system that can replace customers' on-premises file servers. Cloudamize has the capability to recommend Amazon FSxW where customers have Windows File Servers in place on-premises. ## What is Supported? Cloudamize can identify Windows Servers currently sharing files and folders via SMB. Storage on such servers can be migrated to FSx without necessarily moving the servers to EC2 instances. ## Data Collection Cloudamize will collect the necessary data for FSx migrations using data currently gathered by Agent and Agentless Data Collectors; nothing further is required to provide the data necessary for these recommendations. ## How it Works Windows servers that are sharing files via SMB will be included in the analytics for FSx recommendations. Note that C:\\ drives or any administrative shares (those ending in $ (eg, \\ADMIN$ or \\IPC$)) are excluded from this. Recommendations for FSx are then made based on multiple factors and included with the final TCO results. ## What it looks like The Assessment Details screen, and its downloadable report, includes an FSx tab that shows the results of the recommendation calculations, with the following columns: * Server Name * Single-AZ/Multi-AZ * Storage Type (SSD/HDD) * Storage Capacity (GB) * Deduplication % * Effective Storage Capacity(GB) * Throughput (MBps) * EC2 Compute cost(Licenses Included)($) * EBS Storage cost (Note: this ++*will*++ include the C:\\ drive in addition to the data drives) * Total Instance cost (EC2 Compute cost + EBS Storage cost) * FSx cost * Annual Savings($) (Total Instance cost - FSx Cost) | Column Name | Description | |------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Server Name** | Machine's hostname. | | **Single-AZ / Multi-AZ** | Indicates whether the FSx deployment is **Single-AZ** (within one Availability Zone) or **Multi-AZ** (with high availability across two AZs). Multi-AZ provides redundancy but may increase cost. | | **Storage Type (SSD / HDD)** | Specifies the FSx storage type: - **SSD (Solid State Drive)** : Higher performance for transactional workloads. - **HDD (Hard Disk Drive)**: Cost-effective for throughput-intensive workloads. | | **Storage Capacity (GB)** | The total allocated storage capacity in gigabytes (GB) for the FSx file system. | | **Deduplication %** | The estimated percentage of storage savings from deduplication helps in calculating **effective storage capacity**. | | **Effective Storage Capacity (GB)** | The storage available after applying deduplication, compression, or other storage efficiency features. | | **Throughput (MBps)** | The expected throughput or I/O bandwidth of the FSx system in megabytes per second. Useful for estimating performance and sizing workloads. | | **EC2 Compute Cost ($)(Licenses Included)** | The cost associated with the compute instance required to access or manage FSx, if applicable. | | **EBS Storage Cost ($)** | The cost of storage used in the context of FSx (may include temporary or attached EBS volumes if part of the TCO calculation). | | **Total Instance Cost ($)(EC2 Compute Cost + EBS storage Cost)** | Sum of **EC2 Compute Cost** and **EBS Storage Cost**, representing the total cost of ownership for the FSxW asset. | | **FSx Cost ($)** | The FSx Cost ($) column represents the estimated monthly cost of the Amazon FSx file system | | **Annual Savings ($) (Total Instance Cost - FSx Cost)** | The **Annual Savings ($)** column represents the **estimated yearly cost savings** when migrating to Amazon FSx. | For more details on AWS's FSx offering please see their documentation at See , or reach out to AWS directly. If you have any queries, please get in touch with the helpdesk via our [++Helpdesk Portal++](https://cloudreach-software.atlassian.net/servicedesk/customer/portal/9) or by email at [++helpdesk@cloudamize.com++](mailto:helpdesk@cloudamize.com). --- language: "en" --- # AWS Instance Manager ## List of unique licenses used | License | |----------------------------------------------------------------------------------------| | [Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | [BSD License](https://jdbc.postgresql.org/about/license.html) | | [Eclipse Public License - v 1.0](http://www.eclipse.org/org/documents/epl-v10.php) | ### List of libraries used | | | | | | | GroupId | ArtifactId | Version | Type | License | |----------------------------|----------------------------------------------------------------------|----------------|------|----------------------------------------------------------------------------------------| | com.amazonaws | [aws-java-sdk](https://aws.amazon.com/sdk-for-java/) | 1.10.50 | jar | [Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.postgresql | [postgresql](http://jdbc.postgresql.org/) | 9.4-1204-jdbc4 | jar | [BSD License](https://jdbc.postgresql.org/about/license.html) | | org.aspectj | [aspectjrt](http://www.eclipse.org/aspectj/) | 1.8.2 | jar | [Eclipse Public License - v 1.0](http://www.eclipse.org/org/documents/epl-v10.php) | | commons-codec | [commons-codec](http://commons.apache.org/proper/commons-codec/) | 1.6 | jar | [Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | commons-logging | [commons-logging](http://commons.apache.org/proper/commons-logging/) | 1.1.3 | jar | [Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.apache.httpcomponents | [httpclient](http://hc.apache.org/httpcomponents-client) | 4.3.6 | jar | [Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.apache.httpcomponents | [httpcore](http://hc.apache.org/httpcomponents-core-ga) | 4.3.3 | jar | [Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | com.fasterxml.jackson.core | [jackson-annotations](http://github.com/FasterXML/jackson) | 2.5.0 | jar | [Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | com.fasterxml.jackson.core | [jackson-core](https://github.com/FasterXML/jackson) | 2.5.3 | jar | [Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | com.fasterxml.jackson.core | [jackson-databind](http://github.com/FasterXML/jackson) | 2.5.3 | jar | [Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | joda-time | [joda-time](http://www.joda.org/joda-time/) | 2.8.1 | jar | [Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | --- language: "en" --- # Migration Portfolio Assessment(MPA) Export **Migration Portfolio Assessment (MPA) Export** ++**Overview**++ Detailed portfolio assessment and migration planning can be accomplished online with the AWS Migration Portfolio Assessment (MPA). The data from this Cloudamize export can be imported into MPA with a web-based data ingestion process. MPA offers extensive configuration and enables experienced consultants to model scenarios and generate data for business case analysis and migration planning. ++**Use case**++ The use case of this feature is to export infrastructure assets and dependency details in Excel sheets, which have all the columns the AWS MPA tool is looking for and can be ingested into its system. The file contains all the data required to import and map to the respective columns. ++**User Journey**++ Customers can export the MPA report by following these steps: * Access your Cloudamize console ([https://console.cloudamize.com](https://app.cloudamize.com/)) and install Cloudamize agents or agentless data collectors. * Start the assessment ([learn more here](https://support.cloudamize.com/kb/starting-an-assessment-new-console)) and allow the assessment to run to completion. * After the final results are available, log into the Cloudamize console. * Click "Analyze" on the home page, which will navigate to the results page, and click on view details as shown in the screenshots below. ![Screenshot 2026-07-21 at 4.22.58 PM-20260721-105335.png](https://support.cloudamize.com/__attachments/a_9bf43d55fbde92b1363681f7d3cf84b6111a2fbf8811d64f044a5ab066eff841/Screenshot%202026-07-21%20at%204.22.58%E2%80%AFPM-20260721-105335.png?cb=143a70d0d629e6d43c4dea4d0389930b) ^Cloudamize Landing page^ ![image-20241219-074857.png](https://support.cloudamize.com/__attachments/a_37158797777e11ad923d132afd929288e3b92df17ec8ee32540bf6d071082131/image-20241219-074857.png?cb=0d517e80228b63dd34fbfbd84feba319) AWS View Details As a next step, once the " View Details " is clicked on, it will navigate to the new page, which shows the "Reports" tab as shown below. Click on the "Reports" tab and then download "Migration Portfolio Assessment (MPA) Export". The MPA report will be downloaded using the selected plan from the left-hand panel (the default plan is "OLA 2 - Workload, On-Demand") *As Migration Portfolio Assessment (MPA) Export is an AWS-specific feature, the MPA export is only available for AWS assessments.* ![Screenshot 2025-06-05 at 11.40.17 AM-20250605-061921.png](https://support.cloudamize.com/__attachments/a_0433ab31624666719b16a9ac0f5f74394ae5ef53292e0219923dba08a6a15d67/Screenshot%202025-06-05%20at%2011.40.17%E2%80%AFAM-20250605-061921.png?cb=2c6db67d7236e2b5d54489f4d82db92b) ![Screenshot 2025-06-05 at 11.57.04 AM-20250605-062750.png](https://support.cloudamize.com/__attachments/a_4777c0c89c2cab247451176316b60e6695c4feddb12b7c3dd9a0215d329a3476/Screenshot%202025-06-05%20at%2011.57.04%E2%80%AFAM-20250605-062750.png?cb=c2ae71d50661242451e45218748a721b) * The MPA export is design-dependent, and selecting a different design will change the exported report data. You can select a new design from the menu on the left-hand side. * In database details sheets, the recommended target RDS offering 'target instance' and 'deployment engine' are specific to the RDS design. Hence, to get those details, you must select a design with the RDS recommendation option enabled. * Details like Business Unit, Business Owner, Business Owner Email, Business Owner Phone, etc., which Cloudamize agents either do not collect or NA for data collection, will not be exported, and the complete column in Excel will be exported as blank. * As Cloudamize does not maintain the installed database to its running application mapping, the database to application sheet does not contain any data, and ''No data to show" message will be shown. * The customer should not manipulate the Server Id, Application Id, and Database Id values in any of the Excel sheets. Doing this will corrupt the data, and MPA will not be able to identify the correct dependencies ++Link to MPA portal :++ The MPA export includes infrastructure details in different tabs named as follows. |----------------|--------------------------| | * Servers | * Server to application | | * Applications | * Application dependency | | * Databases | * Server communication | If you have any queries, please get in touch with the helpdesk via our [++Helpdesk Portal++](https://cloudreach-software.atlassian.net/servicedesk/customer/portal/9) or by email at [++helpdesk@cloudamize.com++](mailto:helpdesk@cloudamize.com). --- language: "en" --- # AWS Pricing Calculator Integration ## Overview Cloudamize makes it easier to turn your migration assessment results into AWS cost estimates by integrating with the official **AWS Pricing Calculator**. With this integration, you can use assessment data to create AWS cost estimates without manually rebuilding your infrastructure configuration. You can either generate a shareable AWS Pricing Calculator link or download an Excel file for bulk import. ### Benefits * **Save time:** Reuse assessment results instead of manually entering infrastructure details into the AWS Pricing Calculator. * **Reduce manual effort:** Assessment data is formatted for use with AWS pricing estimation workflows. * **Choose your preferred workflow:** Use a pre-populated calculator link for quick review or an Excel export for bulk import. * **Maintain consistency:** Instance, region, operating system, purchase option, and storage information are carried into the AWS pricing workflow. ## Where to find AWS Pricing Calculator 1. Sign in to Cloudamize console portal using the URL . ![Screenshot 2026-08-11 at 11.20.48 AM-20260811-055056.png](https://support.cloudamize.com/__attachments/a_99b509486618b09db9f512ea73eda4a604c34f53935f4ad2fac5618da09f8057/Screenshot%202026-08-11%20at%2011.20.48%E2%80%AFAM-20260811-055056.png?cb=8b137d0ee27cfe3f23b0e05b59132f33) ^Console Home page^ 2. Click on the **Analyze** tile on the console home page and then click on **View Details** to access **Reports** tab. ![Screenshot 2026-08-11 at 11.22.55 AM-20260811-055333.png](https://support.cloudamize.com/__attachments/a_2002ea4e1157f25ce620de2ff6e3b4d860598c0a7ec7fe1cf3b4dd14097b0d10/Screenshot%202026-08-11%20at%2011.22.55%E2%80%AFAM-20260811-055333.png?cb=42025f8f90058b0017bf1c1660418634) ^Analyze^ ![Screenshot 2026-08-11 at 11.23.54 AM-20260811-055446.png](https://support.cloudamize.com/__attachments/a_6baeb462aecea94dead0104e1c2a0c1ef3d32edad3b148e03fea8eec0bc82cdb/Screenshot%202026-08-11%20at%2011.23.54%E2%80%AFAM-20260811-055446.png?cb=d4ce3fd7b27a76ab2935070897105180) ^View Details^ 3. Select the **Reports** tab. ![Screenshot 2026-08-11 at 11.26.49 AM-20260811-055718.png](https://support.cloudamize.com/__attachments/a_37f1375015d5371bbef8f67d10a5d7423cb470f740333a5500e196fcee10daa7/Screenshot%202026-08-11%20at%2011.26.49%E2%80%AFAM-20260811-055718.png?cb=2e6682349a4011008b2de599b160ad17) ^Reports tab^ 3. Locate the **AWS Pricing Calculator** section. ![Screenshot 2026-08-11 at 11.27.58 AM-20260811-055826.png](https://support.cloudamize.com/__attachments/a_949f6bc16a7023a409519177e0d32205ff17ec0381fdb8961b16434734d3e365/Screenshot%202026-08-11%20at%2011.27.58%E2%80%AFAM-20260811-055826.png?cb=cdb6dd45f5e2ab4558c54efdb44f9592) ^AWS Calculator Estimation^ Depending on the options available, you can choose either **Generate Shareable Link** or **AWS Calculator Export (Excel)**. ![Screenshot 2026-08-11 at 11.30.26 AM-20260811-060103.png](https://support.cloudamize.com/__attachments/a_9da71daad371d47d04daced29178a6bb03ce3b55267b228d0049a31627e01ab0/Screenshot%202026-08-11%20at%2011.30.26%E2%80%AFAM-20260811-060103.png?cb=55115464b0a26dcd08da69cf33537965) ^Generate link/Export option^ ## Generate a Shareable Link The **Generate Shareable Link** option creates an official AWS Pricing Calculator URL with your assessment information pre-populated. ### To generate a link 1. Go to **Reports** under**Analyze**section. 2. Find the **AWS Calculator Estimation** section. 3. Click on **Generate Link**. ![Screenshot 2026-08-11 at 11.32.03 AM-20260811-060208.png](https://support.cloudamize.com/__attachments/a_0a8480387cdd2939d1b8983fb2f10bbd972d2441b9d4f5233d774e5b4cd6544d/Screenshot%202026-08-11%20at%2011.32.03%E2%80%AFAM-20260811-060208.png?cb=90e58c9f666dd88e763566f9d3d4f0e3) ^Generate link^ 4. Open the generated link in your browser on a new tab. ![Screenshot 2026-08-11 at 11.33.43 AM-20260811-060348.png](https://support.cloudamize.com/__attachments/a_0506650b11de1339fb9aafccc0b8b065fda3d7052b797247eb1d541bab3ed3a7/Screenshot%202026-08-11%20at%2011.33.43%E2%80%AFAM-20260811-060348.png?cb=1bea07e9b2342b7a39c43f69952c3470) ^Link to open in a new tab^ 5. Review the estimate in the AWS Pricing Calculator. 6. Share the link with other stakeholders as needed. This option is useful when you want to quickly review or collaborate on an AWS cost estimate without downloading a file. ## Export to Excel for AWS Calculator Bulk Import The **AWS Calculator Export (Excel)** option downloads an Excel workbook containing your assessment data in a format that can be used with the AWS Pricing Calculator bulk-import workflow. ### To export your assessment 1. Go to **Reports** under**Analyze**section. 2. Find the **AWS Pricing Calculator** section. 3. Select **AWS Calculator Export (Excel)**. 4. Download and save the Excel workbook. ![Screenshot 2026-08-11 at 11.35.38 AM-20260811-060543.png](https://support.cloudamize.com/__attachments/a_2784cf430ffce8773ba7ee33d61f348434c4c25e6a18ac9395247dc6efe54610/Screenshot%202026-08-11%20at%2011.35.38%E2%80%AFAM-20260811-060543.png?cb=ea2c8a61a28bc1c1847d0c9998124edc) ^Export option^ 5. Open the AWS Pricing Calculator bulk-import page. ![Screenshot 2026-08-11 at 11.36.34 AM-20260811-060731.png](https://support.cloudamize.com/__attachments/a_28fe6cef384c55d7cda6c9fe04df0eb6df4ec65b686651f51449bdf05b5aa48d/Screenshot%202026-08-11%20at%2011.36.34%E2%80%AFAM-20260811-060731.png?cb=be545b207708072d05407ecc5687bae4) ^AWS Pricing Calculator bulk-import page^ 5. Upload the downloaded workbook. 6. Review the imported estimate and make any additional adjustments required. You can access the AWS Pricing Calculator bulk-import page [here](https://calculator.aws/?utm_source=chatgpt.com#/bulk-import) ### Dedicated Host Plans For **Dedicated Host** plans, the AWS Calculator export provides two pre-filled Excel files: * **Shared EC2 Instances Data Export** * **Dedicated Hosts Data Export** **Network costs are excluded:** Network costs are not included in the exported Excel sheets or the estimations. For EVS plans, this feature is not available. ## What information is included? The integration formats relevant assessment information for the AWS Pricing Calculator workflow, including: * AWS region * Instance information * Operating system * Purchase option * Storage details The resulting estimate can then be reviewed and adjusted in the AWS Pricing Calculator based on your specific migration and pricing requirements. If you have any queries, please get in touch with the helpdesk via our [++Helpdesk Portal++](https://cloudreach-software.atlassian.net/servicedesk/customer/portal/9) or by email at [++helpdesk@cloudamize.com++](mailto:helpdesk@cloudamize.com). --- language: "en" --- # AWS RDS BYOM (Bring Your Own Media) ## **Overview** **AWS RDS BYOM (Bring Your Own Media)** enables users with eligible SQL Server licenses to evaluate AWS RDS workloads using **License Mobility through BYOM** in Cloudamize. With this capability, users can enable BYOM while analyzing the supported **AWS RDS plan --- OLA 8 (RDS Workload, 1 Year No Upfront)** . When enabled, Cloudamize adjusts the license cost calculation for applicable RDS instances (`db.*`) from the standard **blended OS + SQL license cost** to the **OS-only annual license cost**. The BYOM toggle is **view-only** and is reflected in the **Licence grid, Summary grid, Annual Cost panel, Analyze, and Analyze V2**. The selection is not saved and resets when switching to a non-RDS plan. ### Steps to view **BYOM** 1. Log in to the Cloudamize portal at the URL: [++console.cloudamize.com++](https://console.cloudamize.com/). 2. Select **Analyze** on the landing page. ![Screenshot 2026-08-20 at 11.57.09 AM-20260820-062748.png](https://support.cloudamize.com/__attachments/a_b8d31e42c18a190321e79b5d32e0113239099aef0308e183bb2a008898c7d50b/Screenshot%202026-08-20%20at%2011.57.09%E2%80%AFAM-20260820-062748.png?cb=31fe569b8af4d2a3ae2c7edc263019df) ^Analyze^ 3. Click **View Details** to see detailed infrastructure results. ![Screenshot 2026-08-20 at 11.59.03 AM-20260820-062948.png](https://support.cloudamize.com/__attachments/a_31120b6debdb1aad65c2dfd7f21fbb4f4012652b3d465c924dec365e1e7d0a0d/Screenshot%202026-08-20%20at%2011.59.03%E2%80%AFAM-20260820-062948.png?cb=4af7ffd20ef5ba8c21d1945421830623) ^View Details^ 4. Select the **OLA 8** -**(RDS Workload, 1 Year No Upfront)**plan from the drop-down button of the design section as shown below ![Screenshot 2026-08-20 at 12.02.07 PM-20260820-063243.png](https://support.cloudamize.com/__attachments/a_8ccfe1ffcce0002af6bc0a0dda4c6b7824b6fa6734dd80fd87fbd612bba32a87/Screenshot%202026-08-20%20at%2012.02.07%E2%80%AFPM-20260820-063243.png?cb=2f5434a980f57013265c7ce5e5b6a04f) ^Select OLA- 8 RDS Plan^ 5. As soon as the design is selected, you will see the BYOM option available beside the **search**box as shown below ![Screenshot 2026-08-20 at 12.05.35 PM-20260820-063904.png](https://support.cloudamize.com/__attachments/a_61c6791469e445831148584887bd3b47d06b0fee2870be2df278d01cce8e7bc9/Screenshot%202026-08-20%20at%2012.05.35%E2%80%AFPM-20260820-063904.png?cb=d2d506edee6bfd38c5ceef75793bb1c6) ^BYOM option^ ### **Enable BYOM** * **BYOM OFF:** Uses the existing **blended OS + SQL Server licensing model**, with both licensing components included in the applicable pricing. ![Screenshot 2026-08-20 at 12.12.17 PM-20260820-064326.png](https://support.cloudamize.com/__attachments/a_6f4105fb3006685e8f1ee9646ddbb6f47220916ef468d2843a244c4999cc7cc2/Screenshot%202026-08-20%20at%2012.12.17%E2%80%AFPM-20260820-064326.png?cb=8e131fc33f2a4a0c1db64773cbdd935c) ^OS + SQL Server licensing^ * **BYOM ON:** RDS `db.*` instances use **OS-only annual license pricing**, SQL Server licensing is covered by the customer's existing BYOM licenses. ![Screenshot 2026-08-20 at 12.20.15 PM-20260820-065346.png](https://support.cloudamize.com/__attachments/a_e8d1ee45f14e2dbbce08efa080a32ad460342103bd7db90cdde968230d35981b/Screenshot%202026-08-20%20at%2012.20.15%E2%80%AFPM-20260820-065346.png?cb=145469360e7e71f580f48e3e7dd367a8) ^OS-only annual license^ * **License Cost \& License Cost Reason:** License Mobility through BYOM is applied when an eligible existing license is brought to AWS RDS under the BYOM option. In this case, the applicable license cost is excluded from the RDS pricing, and the workload is priced using the OS-only annual license cost. ![Screenshot 2026-08-20 at 12.27.39 PM-20260820-065856.png](https://support.cloudamize.com/__attachments/a_ce8b9ced7571a794bfe78f0ad4d6869666dba1dc89052c16f85974317edd091b/Screenshot%202026-08-20%20at%2012.27.39%E2%80%AFPM-20260820-065856.png?cb=849a505bef1bdf3d1341728877492a9f) ^License Mobility through BYOM is applied^ ### **View BYOM License Costs** ### **Summary grid with BYOM enabled:** ![Screenshot 2026-08-20 at 7.21.51 PM-20260820-135231.png](https://support.cloudamize.com/__attachments/a_3d709e2271338fb6f73269cb8b86445153127d0aec98ceea7d74480759a0c80c/Screenshot%202026-08-20%20at%207.21.51%E2%80%AFPM-20260820-135231.png?cb=1a1a4660dd2bbbd8f8e4fdf64d2ad9bb) ### **License grid without BYOM:** ![Screenshot 2026-08-20 at 7.12.20 PM-20260820-134226.png](https://support.cloudamize.com/__attachments/a_8fa97cefebfc99f75e4e1f1490a6d9a3cf457fff4c0b9a6f2d906a3295cb716d/Screenshot%202026-08-20%20at%207.12.20%E2%80%AFPM-20260820-134226.png?cb=2d9c77c4a173caeb9da9225b94c133a2) License Grid without BYOM #### **License grid with BYOM:** ![Screenshot 2026-08-20 at 7.06.13 PM-20260820-133726.png](https://support.cloudamize.com/__attachments/a_fff3bff486909185baabbb741702f1e443ab7876471205d10a9ceb07bd9168a8/Screenshot%202026-08-20%20at%207.06.13%E2%80%AFPM-20260820-133726.png?cb=03c2e8930999138e04ae682197de9690) License Grid with BYOM ### **Annual Cost panel** When BYOM is enabled, the **Total Annual Cost** is updated to reflect the applicable BYOM-based licensing for AWS RDS workloads. The **License** section displays the updated license cost and indicates that **OS License only for RDS (BYOM applied)** is included in the calculation. The overall annual cost is recalculated accordingly. This allows you to view the impact of BYOM on the total annual infrastructure cost directly from the **Annual Cost** panel. ### Analyze V2 **BYOM OFF:** The applicable AWS RDS instances continue to use the **standard blended OS + SQL licensing model**, with the corresponding licensing costs reflected in the plan. ![Screenshot 2026-08-20 at 1.28.04 PM-20260820-080419.png](https://support.cloudamize.com/__attachments/a_0df4d73817f4d75777b775a980714726cc9cd10eb41e651780b754df7589d9bd/Screenshot%202026-08-20%20at%201.28.04%E2%80%AFPM-20260820-080419.png?cb=2cc4c58f1b650c9071e454853b86dc47) ### After Enabling BYOM Once **BYOM (Bring Your Own License)** is enabled, the applicable software license costs are excluded from the AWS migration cost calculation. This results in reduced **Total Annual Cost** and reflects the potential savings from using existing licenses. The **License** section also shows the updated licensing cost, allowing users to easily identify the cost impact of BYOM. ![Screenshot 2026-08-20 at 1.34.52 PM-20260820-080910.png](https://support.cloudamize.com/__attachments/a_9086ef0a2edf0e6415910533fc11f02bf092c1f1f05740664b50551d1d27df1e/Screenshot%202026-08-20%20at%201.34.52%E2%80%AFPM-20260820-080910.png?cb=31869164908155644873822c56d4384d) ### **Understanding BYOM Behaviour** 1. **View-only functionality** The BYOM toggle is intended for viewing and comparing the applicable licensing impact. Changing the toggle does not modify the underlying plan configuration. 2. **Selection is not saved** The BYOM selection is not persisted as part of the plan. Any change made using the toggle applies only to the current view and does not permanently update the plan's licensing configuration. 3. **Reset when switching plans** BYOM is applicable only to supported AWS RDS plans. If you switch from an RDS plan to a non-RDS plan, the BYOM selection is automatically reset and no longer applies. ![Screenshot 2026-08-20 at 1.22.22 PM-20260820-075259.png](https://support.cloudamize.com/__attachments/a_37cfe43c20d0d74452c63d1b2634c02e357b48ee9f630eebe3dce2591d1da28e/Screenshot%202026-08-20%20at%201.22.22%E2%80%AFPM-20260820-075259.png?cb=900248f3c1bcfca481bcf725a7944439) ### **Export limitation** Currently, exports continue to display the **blended license cost** even when BYOM is enabled in the analysis UI. Export support for BYOM-consistent licensing will be addressed separately. If you have any queries, please get in touch with the helpdesk via our [++Helpdesk Portal++](https://cloudreach-software.atlassian.net/servicedesk/customer/portal/9) or by email at [++helpdesk@cloudamize.com++](mailto:helpdesk@cloudamize.com). --- language: "en" --- # AWS Results * [AWS Bring Your Own License](https://support.cloudamize.com/kb/aws-bring-your-own-license.md) * [Design Dedicated Host View](https://support.cloudamize.com/kb/design-dedicated-host-view.md) * [Oracle DB to AWS DBCSI Integration](https://support.cloudamize.com/kb/oracle-db-to-aws-dbcsi-integration.md) * [Estimated Decarbonization Report](https://support.cloudamize.com/kb/estimated-decarbonization-report.md) * [Column Descriptions of the Headers for AWS (IAAS)](https://support.cloudamize.com/kb/column-descriptions-of-the-headers-for-aws-iaas.md) * [AWS FSx for Windows File Server(FSxW)](https://support.cloudamize.com/kb/aws-fsx-for-windows-file-server.md) * [Elastic VMware Service (EVS) on AWS Recommendation in Cloudamize](https://support.cloudamize.com/kb/vmware-cloud-on-aws-recommendation-in-cloudamize.md) * [Cloudamize Design Infrastructure Modernized, Burstable removed](https://support.cloudamize.com/kb/cloudamize-design-infrastructure-modernized-bursta.md) * [Designer: Lift \& Shift and Infrastructure Modernized](https://support.cloudamize.com/kb/designer-lift-shift-and-infrastructure-modernized.md) * [AMD Cloud Design Standards](https://support.cloudamize.com/kb/amd-cloud-design-standards.md) * [Improved Reduced Core License Optimization](https://support.cloudamize.com/kb/improved-reduced-core-license-optimization.md) * [AWS OLA Savings Plans](https://support.cloudamize.com/kb/designer-ola-savings-plans.md) * [RDS Recommendations](https://support.cloudamize.com/kb/rds-recommendations.md) * [Amazon FSx for NetApp ONTAP Recommendations (FSxN)](https://support.cloudamize.com/kb/amazon-fsx-for-netapp-ontap-recommendations-fsxn.md) --- language: "en" --- # Azure Design Plan Definitions ## Overview This document provides detailed explanations for the default Azure Design Plans. These designs are used to perform "What-If" scenarios, comparing a direct "lift-and-shift" approach against right-sized, cost-optimized workloads. This article lists the basic settings for each design to aid understanding. ### Design Plans #### Lift and Shift, Pay as you go The **Lift and Shift, Pay as you go** plan represents a "Direct Transition" model. It is designed to provide a "Like-for-Like" baseline, showing the cost to replicate your current on-premises environment in Azure without making changes to resource allocations based on performance. |--------------------|---------------------------|------------------------------------------------| | **Category** | **Setting** | **Value / Configuration** | | **Pricing Plan** | Pricing Plans | Pay-as-you-go | | | Hybrid Benefits | Do Not Use Hybrid Benefits | | | MSSQL License | Use Azure MSSQL VM Platform | | | Region | \[Set on Assessment Launch\] | | | Discount | 0% | | | Time Modeling | Observed On Time | | **Compute Tuning** | Compute Type | Use Azure VM | | | Resource Selection | CPU and Instance Family | | | Target Peak CPU Threshold | 80% | | | Instance Family | All checked (std.a, std.b, std.d, std.e, etc.) | | **Storage Tuning** | Storage Capacity Scaling | 100% | | | IOPS Scale | 100% | | | Azure Storage | Allow Managed, Unmanaged, and Premium | | | standard HDD disks | Unlimited | | | P4 through P50 disks | 0 | | **Network Tuning** | Network Load Factor | 10% | #### **Infrastructure Modernized, Pay as you go** The **Infrastructure Modernized, Pay-as-you-go** design is an optimization-focused blueprint. Unlike "Lift and Shift" models that replicate physical hardware, this design uses Cloudamize's right-sizing algorithms to match your actual performance utilization to the most cost-effective Azure resources. By targeting modern instance families and utilizing a Pay-As-You-Go model, it provides a balance of high-performance modern hardware with the flexibility of on-demand billing. It is the ideal "Phase 2" migration model for organizations looking to reduce cloud waste while maintaining the ability to scale without long-term commitments. |--------------------|---------------------------|------------------------------------------------| | **Category** | **Setting** | **Value / Configuration** | | **Pricing Plan** | Pricing Plans | Pay-as-you-go | | | Hybrid Benefits | Do Not Use Hybrid Benefits | | | MSSQL License | Use Azure MSSQL VM Platform | | | Region | \[Set on Assessment Launch\] | | | Discount | 0% | | | Time Modeling | Observed On Time | | **Compute Tuning** | Compute Type | Use Azure VM | | | Resource Selection | CPU and Instance Family | | | Target Peak CPU Threshold | 80% | | | Instance Family | All checked (std.a, std.b, std.d, std.e, etc.) | | **Storage Tuning** | Storage Capacity Scaling | 100% | | | IOPS Scale | 100% | | | standard HDD disks | 4 | | | P4 disks | 6 | | | P6 disks | 6 | | | P10 disks | 12 | | | P15 disks | 12 | | | P20 disks | 12 | | | P30 disks | 12 | | | P40 disks | Unlimited | | | P50 disks | Unlimited | | **Network Tuning** | Network Load Factor | 10% | #### **Infrastructure Modernized, Pay as you go, SQL Hybrid Benefit** This design focuses on modernizing database workloads while leveraging existing software investments. It utilizes Cloudamize's right-sizing intelligence to match on-premises performance to modern Azure VM families, but specifically applies the **SQL Server Hybrid Benefit**. By selecting this model, organizations can bring their own SQL Server licenses (with Software Assurance) to Azure, significantly reducing the hourly cost of SQL-enabled VMs. This plan is ideal for organizations that want the flexibility of **Pay-As-You-Go** (on-demand) billing for their infrastructure while eliminating the "License Included" surcharge for their database software. |--------------------|-----------------------------|-------------------------------------------------------| | **Category** | **Setting** | **Value / Configuration** | | **Pricing Plan** | Pricing Plans | Pay-as-you-go | | | Hybrid Benefits | Do Not Use Hybrid Benefits (Applies to OS) | | | MSSQL License | Assume BYO MSSQL License | | | Region | \[Set on Assessment Launch\] | | | Discount | 0% | | | Time Modeling | Observed On Time | | **Compute Tuning** | Compute Type | Use Azure VM | | | Resource Selection | CPU and Instance Family | | | Target Peak CPU Threshold | 80% | | | Instance Family | All checked (std.a, std.b, std.d, std.e, std.m, etc.) | | **Storage Tuning** | Storage Capacity Scaling | 100% | | | IOPS Scale | 100% | | | Azure Storage | Allow Managed, Unmanaged, and Premium | | | standard HDD disks | 4 | | | P4 / P6 disks | 6 | | | P10 / P15 / P20 / P30 disks | 12 | | | P40 / P50 disks | 12 | | **Network Tuning** | Network Load Factor | 10% | #### **Infrastructure Modernized, 1 Year Reserved** The **Infrastructure Modernized, 1 Year Reserved** design is a high-efficiency cost model designed for stable, production-grade workloads. This design leverages Cloudamize's right-sizing intelligence to ensure servers are not over-provisioned, then applies **Azure 1-Year Reserved Instance (RI)** pricing. By committing to a 1-year term, organizations can achieve significant savings (typically 30-40%) compared to standard Pay-As-You-Go rates. This plan is best suited for "always-on" infrastructure where the workload requirements are understood and expected to remain consistent for at least twelve months, providing a balance between deep cost reduction and mid-term commitment flexibility. |--------------------|---------------------------|------------------------------------------------| | **Category** | **Setting** | **Value / Configuration** | | **Pricing Plan** | Pricing Plans | 1-year Reservation | | | Hybrid Benefits | Do Not Use Hybrid Benefits | | | MSSQL License | Use Azure MSSQL VM Platform | | | Region | \[Set on Assessment Launch\] | | | Discount | 0% | | | Time Modeling | Observed On Time | | **Compute Tuning** | Compute Type | Use Azure VM | | | Resource Selection | CPU and Instance Family | | | Target Peak CPU Threshold | 80% | | | Instance Family | All checked (std.a, std.b, std.d, std.e, etc.) | | **Storage Tuning** | Storage Capacity Scaling | 100% | | | IOPS Scale | 100% | | | Azure Storage | Allow Managed, Unmanaged, and Premium | | | standard HDD disks | 4 | | | P4 disks | 6 | | | P6 disks | 6 | | | P10 disks | 12 | | | P15 disks | 12 | | | P20 disks | 12 | | | P30 disks | 12 | | | P40 disks | Unlimited | | | P50 disks | Unlimited | | **Network Tuning** | Network Load Factor | 10% | #### **Infrastructure Modernized, 3 Year Reserved** The **Infrastructure Modernized, 3 Year Reserved** design represents the maximum compute cost-optimization strategy for long-term, stable workloads. This design utilizes Cloudamize's right-sizing intelligence to eliminate over-provisioning and then applies the **Azure 3-Year Reserved Instance (RI)** pricing model. By committing to a three-year term, organizations lock in the highest available compute discounts (often 60% or more compared to Pay-As-You-Go). This plan is the primary recommendation for "Always-On" production environments and core infrastructure where the application footprint is expected to remain stable over a multi-year horizon, ensuring the lowest possible Total Cost of Ownership (TCO) for compute resources. |--------------------|---------------------------|------------------------------------------------| | **Category** | **Setting** | **Value / Configuration** | | **Pricing Plan** | Pricing Plans | 3-year Reservation | | | Hybrid Benefits | Do Not Use Hybrid Benefits | | | MSSQL License | Use Azure MSSQL VM Platform | | | Region | \[Set on Assessment Launch\] | | | Discount | 0% | | | Time Modeling | Observed On Time | | **Compute Tuning** | Compute Type | Use Azure VM | | | Resource Selection | CPU and Instance Family | | | Target Peak CPU Threshold | 80% | | | Instance Family | All checked (std.a, std.b, std.d, std.e, etc.) | | **Storage Tuning** | Storage Capacity Scaling | 100% | | | IOPS Scale | 100% | | | Azure Storage | Allow Managed, Unmanaged, and Premium | | | standard HDD disks | 4 | | | P4 disks | 6 | | | P6 disks | 6 | | | P10 disks | 12 | | | P15 disks | 12 | | | P20 disks | 12 | | | P30 disks | 12 | | | P40 disks | Unlimited | | | P50 disks | Unlimited | | **Network Tuning** | Network Load Factor | 10% | #### **Infrastructure Modernized, 1 Year Reserved, Azure Hybrid Benefit** The **Infrastructure Modernized, 1 Year Reserved, Azure Hybrid Benefit** design is a high-optimization cost model that combines three major saving levers: Right-Sizing, Term Commitment, and License Portability. 1. **Workload Optimization:** It uses actual performance data to ensure you only pay for the resources you need. 2. **1-Year Reservation:** It applies a mid-term commitment discount on compute. 3. **Azure Hybrid Benefit (AHB):** It allows you to use your existing on-premises Windows Server and SQL Server licenses (with Software Assurance) to cover the OS and software costs. This design is the best choice for organizations that already own Microsoft licenses and want to significantly reduce their Azure spend without committing to a full three-year term. |--------------------|---------------------------|------------------------------------------------| | **Category** | **Setting** | **Value / Configuration** | | **Pricing Plan** | Pricing Plans | 1-year Reservation | | | Hybrid Benefits | Use Hybrid Benefits... (Selected) | | | MSSQL License | Assume BYO MSSQL License | | | Region | \[Set on Assessment Launch\] | | | Discount | 0% | | | Time Modeling | Observed On Time | | **Compute Tuning** | Compute Type | Use Azure VM | | | Resource Selection | CPU and Instance Family | | | Target Peak CPU Threshold | 80% | | | Instance Family | All checked (std.a, std.b, std.d, std.e, etc.) | | **Storage Tuning** | Storage Capacity Scaling | 100% | | | IOPS Scale | 100% | | | Azure Storage | Allow Managed, Unmanaged, and Premium | | | standard HDD disks | 4 | | | P4 disks | 6 | | | P6 disks | 6 | | | P10 disks | 12 | | | P15 disks | 12 | | | P20 disks | 12 | | | P30 disks | 12 | | | P40 disks | Unlimited | | | P50 disks | Unlimited | | **Network Tuning** | Network Load Factor | 10% | #### **Infrastructure Modernized, 3 Year Reserved, Azure Hybrid Benefit** The **Infrastructure Modernized, 3 Year Reserved, Azure Hybrid Benefit** design is the most aggressive cost-saving model available within the platform. It represents the "Minimum TCO" (Total Cost of Ownership) scenario by layering three distinct optimization strategies: 1. **Workload Modernization:** Infrastructure is right-sized based on actual performance utilization, ensuring no waste in provisioned vCPU or RAM. 2. **3-Year Commitment:** Applies the maximum compute discount available from Azure by committing to a three-year reservation. 3. **License Portability (AHB):** Removes the cost of Windows Server and SQL Server from the Azure hourly rate by utilizing existing on-premises licenses with Software Assurance. This design is the primary recommendation for production environments where the organization owns perpetual licenses and intends to maintain the workload in Azure for the long term. |--------------------|---------------------------|-----------------------------------------------------| | **Category** | **Setting** | **Value / Configuration** | | **Pricing Plan** | Pricing Plans | 3-year Reservation | | | Hybrid Benefits | Use Hybrid Benefits And BYO MSSQL License If Needed | | | MSSQL License | Assume BYO MSSQL License | | | Region | \[Set on Assessment Launch\] | | | Discount | 0% | | | Time Modeling | Observed On Time | | **Compute Tuning** | Compute Type | Use Azure VM | | | Resource Selection | CPU and Instance Family | | | Target Peak CPU Threshold | 80% | | | Instance Family | All checked (std.a, std.b, std.d, std.e, etc.) | | **Storage Tuning** | Storage Capacity Scaling | 100% | | | IOPS Scale | 100% | | | Azure Storage | Allow Managed, Unmanaged, and Premium | | | standard HDD disks | 4 | | | P4 disks | 6 | | | P6 disks | 6 | | | P10 disks | 12 | | | P15 disks | 12 | | | P20 disks | 12 | | | P30 disks | 12 | | | P40 disks | Unlimited | | | P50 disks | Unlimited | | **Network Tuning** | Network Load Factor | 10% | If you have any queries, please get in touch with the helpdesk via our [++Helpdesk Portal++](https://cloudreach-software.atlassian.net/servicedesk/customer/portal/9) or by email at [++helpdesk@cloudamize.com++](mailto:helpdesk@cloudamize.com). --- language: "en" --- # Azure Fleet Deployment: Cloudamize Agent Mass Installation via Azure Run Command ## Overview This Knowledge Base article provides a step-by-step guide on how to perform mass, non-interactive installations of the Cloudamize Agent across your Azure Virtual Machine (VM) and Virtual Machine Scale Set (VMSS) fleet using **Azure Run Command**. Azure Run Command uses the built-in Azure VM Agent (`waagent` on Linux, Azure Windows VM Agent on Windows) to execute PowerShell or shell scripts remotely within an Azure VM. This enables administrators to deploy software at scale without requiring public IP addresses, direct SSH/RDP connectivity, or management port access on Network Security Groups (NSGs). **Note:** The Azure Run Command steps in this article are provided as guidance for using third-party deployment tooling with the Cloudamize Agent. Cloudamize has not validated or tested these Azure deployment workflows end to end. Review and test the process in your own Azure environment before using it for production deployments. ### Prerequisites Before deploying the Cloudamize Agent across your Azure fleet, verify that all target nodes comply with the official [Cloudamize Agent Installation Prerequisites](https://support.cloudamize.com/kb/agent-installation-prerequisites) and meet the following Azure-specific requirements: * **Official Cloudamize Prerequisites:** Review OS compatibility, system resource requirements, and regional proxy/endpoint settings in the [Agent Installation Prerequisites KB](https://support.cloudamize.com/kb/agent-installation-prerequisites). * **Network \& Outbound Access:** Target instances must have outbound access on **TCP Port 443** directly or via a NAT Gateway/Proxy to your assigned Cloudamize regional endpoint: * **US Region:** `am.cloudamize.com` * **EU Region:** `am-de.cloudamize.com` * **UAE Region:** `am-ae.cloudamize.com` * **Azure VM Guest Agent:** Target virtual machines must have the Azure VM Guest Agent installed and in a `Ready` state. * **Azure RBAC Permissions:** Your Azure account or automation service principal requires the `Microsoft.Compute/virtualMachines/runCommand/action` permission (included in roles such as **Virtual Machine Contributor** or **Contributor**). * **Console Access:** Ensure you have access to your [Cloudamize Console](https://console.cloudamize.com/) to copy your environment-specific installation command and Customer Key. ### Step-by-Step Installation Instructions #### Step 1: Prepare Your Installation Command **Important Note on Region Endpoints \& Customer Keys:** The installer URL domain and `custkey` / `customerkey` parameters depend on the specific region where your Cloudamize assessment is provisioned (e.g., US, EU, or UAE) and your unique account credentials. Always copy the exact command and key directly from your [Cloudamize Console](https://console.cloudamize.com/). #### For Linux Fleet (`RunShellScript`): #Bash sh <(curl 'https://am.cloudamize.com/cxf/downloadFileV3?custkey=&filename=installCloudamizeAgentV2.sh' -L) *(Replace* `am.cloudamize.com`*with your regional endpoint domain if using EU or UAE, and replace* `YOUR_CUSTOMER_KEY`*with your actual Customer Key).* #### For Windows Fleet (`RunPowerShellScript`): #PowerShell $msiPath = "$env:TEMP\cloudamizeAgent.msi" Invoke-WebRequest -Uri "https://am.cloudamize.com/cxf/downloadFileV3?custkey=&filename=cloudamizeAgent.msi" -OutFile $msiPath msiexec /i $msiPath customerkey=YOUR_CUSTOMER_KEY /qn *(Replace* `am.cloudamize.com`*with your regional endpoint domain if using EU or UAE, and replace* `YOUR_CUSTOMER_KEY`*with your actual Customer Key).* ##### Step 2: Execute Deployment via Azure Portal or Azure CLI ##### Option A: Deploy via Azure Portal (Single VM or Small Fleet) 1. Log in to the **Azure Portal**. 2. Navigate to **Virtual machines** and select your target VM. 3. In the left navigation menu under **Operations** , select **Run command**. 4. Choose the command execution module: * **Linux:** Click **RunShellScript** * **Windows:** Click **RunPowerShellScript** 5. Paste the corresponding script block into the script window and click **Run** . ##### Option B: Mass Deployment Across Resource Groups via Azure CLI / Cloud Shell To perform mass deployment across multiple VMs in a Resource Group simultaneously, use the Azure CLI (`az vm run-command invoke`): ###### Mass Linux Fleet Deployment: Bash #Bash # Save installation script locally cat << 'EOF' > install_cloudamize.sh #!/bin/bash sh <(curl 'https://am.cloudamize.com/cxf/downloadFileV3?custkey=YOUR_CUSTOMER_KEY&filename=installCloudamizeAgentV2.sh' -L) EOF # Mass execute across all Linux VMs in a Resource Group for vm in $(az vm list -g "rg-production" --query "[?storageProfile.osDisk.osType=='Linux'].name" -o tsv); do echo "Deploying Cloudamize Agent to VM: $vm" az vm run-command invoke \ --resource-group "rg-production" \ --name "$vm" \ --command-id "RunShellScript" \ --scripts "@install_cloudamize.sh" \ --no-wait done ###### Mass Windows Fleet Deployment: Bash #Bash # Save PowerShell script locally cat << 'EOF' > install_cloudamize.ps1 $msiPath = "$env:TEMP\cloudamizeAgent.msi" Invoke-WebRequest -Uri "https://am.cloudamize.com/cxf/downloadFileV3?custkey=YOUR_CUSTOMER_KEY&filename=cloudamizeAgent.msi" -OutFile $msiPath msiexec /i $msiPath customerkey=YOUR_CUSTOMER_KEY /qn EOF # Mass execute across all Windows VMs in a Resource Group for vm in $(az vm list -g "rg-production" --query "[?storageProfile.osDisk.osType=='Windows'].name" -o tsv); do echo "Deploying Cloudamize Agent to VM: $vm" az vm run-command invoke \ --resource-group "rg-production" \ --name "$vm" \ --command-id "RunPowerShellScript" \ --scripts "@install_cloudamize.ps1" \ --no-wait done ### Verification \& Monitoring Once execution completes, verify the installation status across your target VMs: 1. View execution logs in the Azure CLI response output or under **Run command** \> **Script execution status** in the Azure Portal. 2. Verify agent services directly on target virtual machines: * **Linux:** Run `systemctl status cloudamize-agent` * **Windows:** Check services for `Cloudamize Agent Service` 3. Log in to the [Cloudamize Console](https://console.cloudamize.com/) and confirm that the newly registered instances appear in your node list. Frequently Asked Questions **Why am I getting a "VM Agent is not in a ready state" error?** Azure Run Command requires the Azure Guest Agent (`waagent` on Linux or Windows Guest Agent) to be running and healthy. Ensure the agent service is installed, active, and able to communicate with Azure fabric endpoints. **Can I automate this across all newly created Azure VMs automatically?** Yes. You can create an **Azure Policy** with the `DeployIfNotExists` effect targeting `Microsoft.Compute/virtualMachines/runCommands` or deploy via the **Custom Script Extension** during VM provisioning. **Do I need public IP addresses or open inbound RDP/SSH ports on NSGs?** No. Azure Run Command executes natively through the guest VM agent using outbound fabric polling over HTTPS (Port 443). No inbound network ports need to be exposed. If you have any queries, please get in touch with the helpdesk via our [++Helpdesk Portal++](https://cloudreach-software.atlassian.net/servicedesk/customer/portal/9) or by email at [++helpdesk@cloudamize.com++](mailto:helpdesk@cloudamize.com). --- language: "en" --- # Azure Instance Manager List of unique licenses used | License | |--------------------------------------------------------------------------------------------------------------------| | [Apache License, Version 2.0](https://raw.githubusercontent.com/WindowsAzure/azure-sdk-for-net/master/LICENSE.txt) | | [MIT License](https://raw.githubusercontent.com/Microsoft/dotnet/master/LICENSE) | | [Microsoft .NET Library License](https://www.microsoft.com/net/dotnet_library_license.htm) | ## List of libraries used | Package | Version | Type | License | |-----------------------------------------------------------------------------------------------------------------|----------------------|------|--------------------------------------------------------------------------------------------------------------------| | [WindowsAzure.Storage](https://docs.microsoft.com/en-us/azure/storage/) | 6.2.2 | dll | [Apache License, Version 2.0](https://raw.githubusercontent.com/WindowsAzure/azure-sdk-for-net/master/LICENSE.txt) | | [Hyak.Common](https://github.com/Azure/hyak-common) | 1.0.0 | dll | [Apache License, Version 2.0](https://raw.githubusercontent.com/WindowsAzure/azure-sdk-for-net/master/LICENSE.txt) | | [Microsoft.Azure.Commerce.UsageAggreates](https://github.com/Azure/azure-sdk-for-net) | 1.5.0 | dll | [Apache License, Version 2.0](https://raw.githubusercontent.com/WindowsAzure/azure-sdk-for-net/master/LICENSE.txt) | | [Microsoft.Azure.Insights](https://github.com/Azure/azure-sdk-for-net) | 0.11.0-preview | dll | [MIT License](https://raw.githubusercontent.com/Microsoft/dotnet/master/LICENSE) | | [Microsoft.Azure.Common](https://github.com/Azure/azure-sdk-for-net) | 2.1.0 | dll | [Apache License, Version 2.0](https://raw.githubusercontent.com/WindowsAzure/azure-sdk-for-net/master/LICENSE.txt) | | [Microsoft.Azure.KeyVault.Core](https://github.com/Azure/azure-sdk-for-net) | 1.0.0 | dll | [MIT License](https://raw.githubusercontent.com/Microsoft/dotnet/master/LICENSE) | | [Microsoft.Azure.Management.Compute](https://github.com/Azure/azure-sdk-for-net) | 13.0.1-prerelease | dll | [MIT License](https://raw.githubusercontent.com/Microsoft/dotnet/master/LICENSE) | | [Microsoft.Azure.Management.Network](https://github.com/Azure/azure-sdk-for-net) | 4.5.0-preview | dll | [MIT License](https://raw.githubusercontent.com/Microsoft/dotnet/master/LICENSE) | | [Microsoft.Azure.Management.Storage](https://github.com/Azure/azure-sdk-for-net) | 5.0.0 | dll | [MIT License](https://raw.githubusercontent.com/Microsoft/dotnet/master/LICENSE) | | [Microsfot.Bcl](https://blogs.msdn.microsoft.com/bclteam/p/bcl/) | 1.1.10 | dll | [Microsoft .NET Library License](https://www.microsoft.com/net/dotnet_library_license.htm) | | [Microsoft.Data.Edm](http://odata.github.io/) | 5.7.0 | dll | [Microsoft .NET Library License](http://www.odata.org/documentation/odatacomponent_rtw_enu.htm) | | [Microsoft.Azure.Management.Sql](https://github.com/Azure/azure-sdk-for-net) | 0.46.0-prerelease | dll | [Apache License, Version 2.0](https://raw.githubusercontent.com/WindowsAzure/azure-sdk-for-net/master/LICENSE.txt) | | [Microsoft.Azure.Manangement.TrafficManager](https://github.com/Azure/azure-sdk-for-net) | 1.0.0 | dll | [MIT License](https://raw.githubusercontent.com/Microsoft/dotnet/master/LICENSE) | | [System.Spatial](http://odata.github.io/) | 5.7.0 | dll | [Microsoft .NET Library License](http://www.odata.org/documentation/odatacomponent_rtw_enu.htm) | | [Microsoft.Azure.ResourceManager](https://github.com/Azure/azure-sdk-for-net) | 3.0.0-preview | dll | [Apache License, Version 2.0](https://raw.githubusercontent.com/WindowsAzure/azure-sdk-for-net/master/LICENSE.txt) | | [Microsoft.Bcl.Build](https://blogs.msdn.microsoft.com/bclteam/p/bclbuild/) | 1.0.21 | dll | [Microsoft .NET Library License](https://www.microsoft.com/net/dotnet_library_license.htm) | | [Microsoft.Data.OData](http://odata.github.io/) | 5.7.0 | dll | [Microsoft .NET Library License](http://www.odata.org/documentation/odatacomponent_rtw_enu.htm) | | [Microsoft.Data.Services.Client](http://odata.github.io/) | 5.7.0 | dll | [Microsoft .NET Library License](http://www.odata.org/documentation/odatacomponent_rtw_enu.htm) | | [Microsoft.Bcl.Async](https://blogs.msdn.microsoft.com/bclteam/p/asynctargetingpackkb/) | 1.0.168 | dll | [Microsoft .NET Library License](https://www.microsoft.com/net/dotnet_library_license.htm) | | [Microsoft.Net.Http](https://blogs.msdn.microsoft.com/bclteam/p/httpclient/) | 2.2.29 | dll | [Microsoft .NET Library License](https://www.microsoft.com/net/dotnet_library_license.htm) | | [Microsoft.Rest.ClientRuntime.Azure](https://github.com/Azure/AutoRest) | 3.2.0 | dll | [MIT License](https://raw.githubusercontent.com/Microsoft/dotnet/master/LICENSE) | | [Microsoft.WindowsAzure.Common.Dependencies](https://github.com/Azure/azure-sdk-for-net) | 1.1.1 | dll | [Apache License, Version 2.0](https://raw.githubusercontent.com/WindowsAzure/azure-sdk-for-net/master/LICENSE.txt) | | [Microsoft.IdentifyModel.Clients.ActiveDirectory](https://msdn.microsoft.com/en-us/library/azure/mt417579.aspx) | 3.11.305310302-alpha | dll | [MIT License](https://github.com/AzureAD/azure-activedirectory-library-for-dotnet/blob/dev/LICENSE) | | [Microsoft.WindowsAzure.Management](https://github.com/Azure/azure-sdk-for-net) | 4.1.1 | dll | [Apache License, Version 2.0](https://raw.githubusercontent.com/WindowsAzure/azure-sdk-for-net/master/LICENSE.txt) | | [Microsoft.WindowsAzure.Management.Libraries](https://github.com/Azure/azure-sdk-for-net) | 2.0.0 | dll | [Apache License, Version 2.0](https://raw.githubusercontent.com/WindowsAzure/azure-sdk-for-net/master/LICENSE.txt) | | [Microsoft.Rest.ClientRunTime](https://github.com/Azure/AutoRest) | 2.2.0 | dll | [MIT License](https://raw.githubusercontent.com/Microsoft/dotnet/master/LICENSE) | | [Microsoft.WindowsAzure.Management.Monitoring](https://github.com/Azure/azure-sdk-for-net) | 4.1.0 | dll | [Apache License, Version 2.0](https://raw.githubusercontent.com/WindowsAzure/azure-sdk-for-net/master/LICENSE.txt) | | [Microsoft.WindowsAzure.Common](https://github.com/Azure/azure-sdk-for-net) | 1.4.1 | dll | [Apache License, Version 2.0](https://raw.githubusercontent.com/WindowsAzure/azure-sdk-for-net/master/LICENSE.txt) | | [Microsoft.WindowsAzure.Management.Network](https://github.com/Azure/azure-sdk-for-net) | 7.1.1 | dll | [Apache License, Version 2.0](https://raw.githubusercontent.com/WindowsAzure/azure-sdk-for-net/master/LICENSE.txt) | | [Microsoft.WindowsAzure.Management.Compute](https://github.com/Azure/azure-sdk-for-net) | 12.8.0 | dll | [Apache License, Version 2.0](https://raw.githubusercontent.com/WindowsAzure/azure-sdk-for-net/master/LICENSE.txt) | | [Microsoft.WindowsAzure.Management.Scheduler](https://github.com/Azure/azure-sdk-for-net) | 6.2.0 | dll | [Apache License, Version 2.0](https://raw.githubusercontent.com/WindowsAzure/azure-sdk-for-net/master/LICENSE.txt) | | [Microsoft.WindowsAzure.Management.MediaServices](https://github.com/Azure/azure-sdk-for-net) | 4.1.0 | dll | [Apache License, Version 2.0](https://raw.githubusercontent.com/WindowsAzure/azure-sdk-for-net/master/LICENSE.txt) | | [Microsoft.WindowsAzure.Management.Storage](https://github.com/Azure/azure-sdk-for-net) | 4.0.0 | dll | [Apache License, Version 2.0](https://raw.githubusercontent.com/WindowsAzure/azure-sdk-for-net/master/LICENSE.txt) | | [Microsoft.WindowsAzure.Management.Sql](https://github.com/Azure/azure-sdk-for-net) | 5.2.0 | dll | [Apache License, Version 2.0](https://raw.githubusercontent.com/WindowsAzure/azure-sdk-for-net/master/LICENSE.txt) | | [Microsoft.WindowsAzure.Management.WebSites](https://github.com/Azure/azure-sdk-for-net) | 5.0.0-prerelease | dll | [Apache License, Version 2.0](https://raw.githubusercontent.com/WindowsAzure/azure-sdk-for-net/master/LICENSE.txt) | | [Newtonsoft.Json](http://www.newtonsoft.com/json) | 9.0.1-beta1 | dll | [MIT License](https://github.com/JamesNK/Newtonsoft.Json/blob/master/LICENSE.md) | --- language: "en" --- # Azure Manage Dashboard ## Unique Licenses |----------------------------------------------------------------------------------------------------------------| | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | [Apache License 2.0](http://www.apache.org/licenses/LICENSE-2.0) | | [GNU Lesser General Public License](http://www.gnu.org/licenses/lgpl.html) | | [CDDL + GPLv2 with classpath exception](https://glassfish.dev.java.net/nonav/public/CDDL+GPL.html) | | [BSD License](http://www.antlr.org/license.html) | | [Public Domain](http://repository.jboss.org/licenses/cc0-1.0.txt) | | [Additional Information](https://wiki.creativecommons.org/wiki/Public_domain) | | [Unicode/ICU License](http://source.icu-project.org/repos/icu/trunk/icu4j/main/shared/licenses/LICENSE) | | [MIT](http://choosealicense.com/licenses/mit/) | | [MPL 1.1](http://www.mozilla.org/MPL/MPL-1.1.html) | | [++Google Web Toolkit Terms++](http://code.google.com/webtoolkit/terms.html) | | [LGPL 2.1](http://www.gnu.org/licenses/lgpl-2.1.html) | | [Common Development and Distribution License (CDDL) v1.0](https://glassfish.dev.java.net/public/CDDLv1.0.html) | | [CDDL](http://www.sun.com/cddl)-[GPLv2+CE](https://glassfish.java.net/public/CDDL+GPL_1_1.html) | | [CDDL + GPLv2 with classpath exception](https://glassfish.dev.java.net/nonav/public/CDDL+GPL.html) | | | | | | [++Eclipse Public License - v 1.0++](http://www.eclipse.org/legal/epl-v10.html) | | [Bouncy Castle Licence](http://www.bouncycastle.org/licence.html) | | [BSD-style license](http://freemarker.org/LICENSE.txt) | | [Eclipse Distribution License - v 1.0](http://www.eclipse.org/org/documents/edl-v10.php) | | [lgpl](http://repository.jboss.org/licenses/lgpl-2.1.txt) | | [GNU Lesser General Public License Version 3.0](http://www.gnu.org/licenses/lgpl.html) | | | | | | | | GroupId | ArtifactId | Version | Type | Licenses | |----------------------------------|-------------------------------------------------------------------------------------------------------|-----------------|------|----------------------------------------------------------------------------------------------------------------------------------------------------------------| | com.google.code.gson | [gson](http://code.google.com/p/google-gson/) | 2.2.3 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | com.google.gwt.inject | [gin](http://code.google.com/p/google-gin/) | 2.0.0 | jar | [Apache License 2.0](http://www.apache.org/licenses/LICENSE-2.0) | | com.google.inject | [guice](http://code.google.com/p/google-guice/guice/) | 3.0 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | com.google.inject.extensions | [guice-assistedinject](http://code.google.com/p/google-guice/extensions-parent/guice-assistedinject/) | 3.0 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | com.microsoft.aad | [adal4j](http://maven.apache.org/) | 0.0.2 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | com.thetransactioncompany | [cors-filter](http://software.dzhuvinov.com/cors-filter.html) | 1.5.1 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | commons-codec | [commons-codec](http://commons.apache.org/codec/) | 1.6 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | commons-logging | [commons-logging](http://commons.apache.org/proper/commons-logging/) | 1.1.3 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | de.novanic.gwteventservice | [eventservice](http://gwteventservice.googlecode.com/eventservice) | 1.2.1 | jar | [GNU Lesser General Public License](http://www.gnu.org/licenses/lgpl.html) | | de.novanic.gwteventservice | [eventservice-rpc](http://gwteventservice.googlecode.com/eventservice-rpc) | 1.2.1 | jar | [GNU Lesser General Public License](http://www.gnu.org/licenses/lgpl.html) | | de.novanic.gwteventservice | [gwteventservice](http://gwteventservice.googlecode.com/gwteventservice) | 1.2.1 | jar | [GNU Lesser General Public License](http://www.gnu.org/licenses/lgpl.html) | | javax.servlet | jstl | 1.1.2 | jar | [CDDL + GPLv2 with classpath exception](https://glassfish.dev.java.net/nonav/public/CDDL+GPL.html) | | net.bull.javamelody | [javamelody-core](http://javamelody.googlecode.com/) | 1.40.0 | jar | | | net.sf.gwt-widget | [gwt-sl](http://code.google.com/p/gwt-sl/) | 1.3-RC1 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.apache.httpcomponents | [httpclient](http://hc.apache.org/httpcomponents-client) | 4.3.1 | jar | [Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.apache.httpcomponents | [httpcore](http://hc.apache.org/httpcomponents-core-ga) | 4.3 | jar | [Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.springframework | [spring-web](https://github.com/SpringSource/spring-framework) | 3.2.1.RELEASE | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.springframework | [spring-webmvc](https://github.com/SpringSource/spring-framework) | 3.2.1.RELEASE | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | taglibs | standard | 1.1.2 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | antlr | [antlr](http://www.antlr.org/) | 2.7.7 | jar | [BSD License](http://www.antlr.org/license.html) | | aopalliance | [aopalliance](http://aopalliance.sourceforge.net/) | 1.0 | jar | [Public Domain](http://repository.jboss.org/licenses/cc0-1.0.txt) [Additional Information](https://wiki.creativecommons.org/wiki/Public_domain) | | asm | [asm](http://asm.objectweb.org/asm/) | 3.3 | jar | [BSD](http://asm.objectweb.org/license.html) | | asm | [asm-commons](http://asm.objectweb.org/asm-commons/) | 3.3 | jar | [BSD](http://asm.objectweb.org/license.html) | | asm | [asm-tree](http://asm.objectweb.org/asm-tree/) | 3.3 | jar | [BSD](http://asm.objectweb.org/license.html) | | c3p0 | [c3p0](http://c3p0.sourceforge.net/) | 0.9.1.1 | jar | [GNU LESSER GENERAL PUBLIC LICENSE](http://www.gnu.org/licenses/lgpl.txt) | | cglib | [cglib-nodep](http://cglib.sourceforge.net/) | 2.1_3 | jar | [Apache License, Version 2.0](http://aws.amazon.com/apache2.0) | | com.amazonaws | [aws-java-sdk](http://aws.amazon.com/sdkforjava) | 1.3.23 | jar | [Apache License, Version 2.0](http://aws.amazon.com/apache2.0) | | com.fasterxml.jackson.core | [jackson-annotations](http://github.com/FasterXML/jackson) | 2.7.0 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | com.fasterxml.jackson.core | [jackson-core](https://github.com/FasterXML/jackson-core) | 2.7.2 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | com.fasterxml.jackson.core | [jackson-databind](http://github.com/FasterXML/jackson) | 2.7.2 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | com.google.guava | [guava](http://code.google.com/p/guava-libraries) | r08 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | com.ibm.icu | icu4j | 2.6.1 | jar | [Unicode/ICU License](http://source.icu-project.org/repos/icu/trunk/icu4j/main/shared/licenses/LICENSE) | | com.jolbox | [bonecp](http://jolbox.com/bonecp) | 0.7.1.RELEASE | jar | [Apache v2](http://www.apache.org/licenses/LICENSE-2.0.html) | | com.jolbox | [bonecp-provider](http://jolbox.com/bonecp-provider) | 0.7.1.RELEASE | jar | [Apache v2](http://www.apache.org/licenses/LICENSE-2.0.html) | | com.nimbusds | [lang-tag](https://bitbucket.org/nimbusds/nimbus-langtag) | 1.4 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | com.nimbusds | [nimbus-jose-jwt](https://bitbucket.org/connect2id/nimbus-jose-jwt) | 3.1.2 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | com.nimbusds | [oauth2-oidc-sdk](https://bitbucket.org/connect2id/oauth-2.0-sdk-with-openid-connect-extensions) | 4.5 | jar | [http://www.apache.org/licenses/LICENSE-2.0.html‎](#) | | com.stripe | [stripe-java](https://github.com/stripe/stripe-java) | 1.5.1 | jar | [MIT](http://choosealicense.com/licenses/mit/) | | com.thetransactioncompany | [java-property-utils](http://software.dzhuvinov.com/) | 1.7.1 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | commons-beanutils | [commons-beanutils](http://commons.apache.org/beanutils/) | 1.8.3 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | commons-collections | [commons-collections](http://commons.apache.org/collections/) | 3.2.1 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | commons-fileupload | [commons-fileupload](http://commons.apache.org/fileupload/) | 1.2.2 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | commons-io | [commons-io](http://commons.apache.org/io/) | 2.0.1 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | commons-lang | [commons-lang](http://commons.apache.org/lang/) | 2.5 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | dom4j | [dom4j](http://dom4j.org/) | 1.6.1 | jar | [BSD](http://asm.objectweb.org/license.html) | | javassist | [javassist](http://www.javassist.org/) | 3.11.0.GA | jar | [MPL 1.1](http://www.mozilla.org/MPL/MPL-1.1.html) [LGPL 2.1](http://www.gnu.org/licenses/lgpl-2.1.html) | | javax.activation | [activation](http://java.sun.com/products/javabeans/jaf/index.jsp) | 1.1 | jar | [Common Development and Distribution License (CDDL) v1.0](https://glassfish.dev.java.net/public/CDDLv1.0.html) | | javax.inject | [javax.inject](http://code.google.com/p/atinject/) | 1 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | javax.mail | [mail](http://kenai.com/projects/javamail/mail) | 1.4.6 | jar | [CDDL](http://www.sun.com/cddl)-[GPLv2+CE](https://glassfish.java.net/public/CDDL+GPL_1_1.html) | | javax.servlet | servlet-api | 2.5 | jar | [CDDL + GPLv2 with classpath exception](https://glassfish.dev.java.net/nonav/public/CDDL+GPL.html) | | javax.validation | validation-api | 1.0.0.GA | jar | [Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | jaxen | [jaxen](http://jaxen.codehaus.org/) | 1.1.1 | jar | [Apache License Version 2.0](http://www.apache.org/licenses/LICENSE-2.0) | | jdom | jdom | 1.0 | jar | | | log4j | [log4j](http://logging.apache.org/log4j/1.2/) | 1.2.17 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | net.jcip | [jcip-annotations](http://jcip.net/) | 1.0 | jar | | | net.minidev | | 1.1.1 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | ognl | [ognl](http://ognl.org/) | 3.0.4 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.apache.commons | [commons-lang3](http://commons.apache.org/proper/commons-lang/) | 3.3.1 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.apache.poi | [poi](http://poi.apache.org/) | 3.10-FINAL | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.apache.poi | [poi-ooxml](http://poi.apache.org/) | 3.10-FINAL | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.apache.poi | [poi-ooxml-schemas](http://poi.apache.org/) | 3.10-FINAL | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.apache.struts | [struts2-core](http://struts.apache.org/struts2/struts2-core) | 2.3.1.2 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.apache.struts | [struts2-json-plugin](http://struts.apache.org/struts2/struts2-plugins/struts2-json-plugin) | 2.2.3 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.apache.struts.xwork | [xwork-core](http://struts.apache.org/struts2/xwork-core) | 2.3.1.2 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.apache.xmlbeans | [xmlbeans](http://xmlbeans.apache.org/) | 2.3.0 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.aspectj | [aspectjrt](http://www.aspectj.org/) | 1.7.0 | jar | [Eclipse Public License - v 1.0](http://www.eclipse.org/legal/epl-v10.html) | | org.aspectj | [aspectjweaver](http://www.aspectj.org/) | 1.7.0 | jar | [Eclipse Public License - v 1.0](http://www.eclipse.org/legal/epl-v10.html) | | org.bouncycastle | [bcprov-jdk15on](http://www.bouncycastle.org/java.html) | 1.51 | jar | [Bouncy Castle Licence](http://www.bouncycastle.org/licence.html) | | org.codehaus.jackson | [jackson-core-asl](http://jackson.codehaus.org/) | 1.8.9 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.codehaus.jackson | [jackson-mapper-asl](http://jackson.codehaus.org/) | 1.8.9 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.freemarker | [freemarker](http://freemarker.org/) | 2.3.18 | jar | [BSD-style license](http://freemarker.org/LICENSE.txt) | | org.hibernate | [hibernate-core](http://hibernate.org/) | 4.2.0.Final | jar | [GNU Lesser General Public License](http://www.gnu.org/licenses/lgpl-2.1.html) | | org.hibernate | [hibernate-validator](http://validator.hibernate.org/hibernate-validator) | 4.2.0.Final | jar | [Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.hibernate.common | [hibernate-commons-annotations](http://hibernate.org/) | 4.0.1.Final | jar | [GNU LESSER GENERAL PUBLIC LICENSE](http://www.gnu.org/licenses/lgpl-2.1.html) | | org.hibernate.javax.persistence | [hibernate-jpa-2.0-api](http://hibernate.org/) | 1.0.1.Final | jar | [Eclipse Distribution License - v 1.0](http://www.eclipse.org/org/documents/edl-v10.php) | | org.javassist | [javassist](http://www.javassist.org/) | 3.15.0-GA | jar | [MPL 1.1](http://www.mozilla.org/MPL/MPL-1.1.html)-[LGPL 2.1](http://www.gnu.org/licenses/lgpl-2.1.html)-[Apache License 2.0](http://www.apache.org/licenses/) | | org.jboss.logging | [jboss-logging](http://www.jboss.org/) | 3.1.2.GA | jar | [Apache License, version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.jboss.spec.javax.transaction | | 1.0.0.Final | jar | [lgpl](http://repository.jboss.org/licenses/lgpl-2.1.txt) | | org.jrobin | [jrobin](http://www.jrobin.org/) | 1.5.9 | jar | [GNU LESSER GENERAL PUBLIC LICENSE Version 3](http://www.gnu.org/licenses/lgpl.html).0 | | org.quartz-scheduler | [quartz](http://quartz-scheduler.org/quartz/) | 2.1.6 | jar | [Apache 2.0](http://www.apache.org/licenses/LICENSE-2.0) | | org.slf4j | [slf4j-api](http://www.slf4j.org/) | 1.6.1 | jar | [MIT License](http://www.opensource.org/licenses/mit-license.php) | | org.slf4j | [slf4j-log4j12](http://www.slf4j.org/) | 1.6.1 | jar | [MIT License](http://www.opensource.org/licenses/mit-license.php) | | org.springframework | [spring-aop](https://github.com/SpringSource/spring-framework) | 3.2.1.RELEASE | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.springframework | [spring-beans](https://github.com/SpringSource/spring-framework) | 3.2.1.RELEASE | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.springframework | [spring-context](https://github.com/SpringSource/spring-framework) | 3.2.1.RELEASE | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.springframework | [spring-core](https://github.com/SpringSource/spring-framework) | 3.2.1.RELEASE | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.springframework | [spring-expression](https://github.com/SpringSource/spring-framework) | 3.2.1.RELEASE | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.springframework | spring-jdbc | 3.0.5.RELEASE | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.springframework | [spring-orm](https://github.com/SpringSource/spring-framework) | 3.2.1.RELEASE | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.springframework | [spring-test](https://github.com/SpringSource/spring-framework) | 3.2.1.RELEASE | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.springframework | [spring-tx](https://github.com/SpringSource/spring-framework) | 3.2.1.RELEASE | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.springframework.security | [spring-security-acl](http://springsource.org/spring-security) | 3.1.4.RELEASE | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.springframework.security | [spring-security-config](http://springsource.org/spring-security) | 3.1.4.RELEASE | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.springframework.security | [spring-security-core](http://springsource.org/spring-security) | 3.1.4.RELEASE | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.springframework.security | [spring-security-taglibs](http://springsource.org/spring-security) | 3.1.4.RELEASE | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | org.springframework.security | [spring-security-web](http://springsource.org/spring-security) | 3.1.4.RELEASE | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | postgresql | [postgresql](http://jdbc.postgresql.org/) | 9.1-901-1.jdbc4 | jar | [BSD License](http://jdbc.postgresql.org/license.html) | | stax | [stax-api](http://stax.codehaus.org/) | 1.0.1 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | xalan | xalan | 2.6.0 | jar | [++Apache 2.0++](http://www.apache.org/licenses/LICENSE-2.0) | | xerces | [xercesImpl](http://xerces.apache.org/xerces2-j) | 2.9.1 | jar | [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt) | | xml-apis | [xml-apis](http://xml.apache.org/commons/#external) | 1.3.02 | jar | [++Apache 2.0++](http://www.apache.org/licenses/LICENSE-2.0) | | xom | [xom](http://www.xom.nu/) | 1.0 | jar | [GNU Lesser General Public License Version 3.0](http://www.gnu.org/licenses/lgpl.html) | --- language: "en" --- # Azure Results * [Integrate with Azure Migrate](https://support.cloudamize.com/kb/integrate-with-azure-migrate.md) * [Column Descriptions of the Headers for Azure(IAAS)](https://support.cloudamize.com/kb/column-descriptions-of-the-headers-for-azure-iaas.md) * [Azure Design Plan Definitions](https://support.cloudamize.com/kb/azure-design-plan-definitions.md) --- language: "en" --- # Basic and Advanced MS SQL data collected by Agents and Agentless Data Collectors ## What is it? Cloudamize can collect two types of Microsoft (MS) SQL data: *Basic* data and *Advanced* data. The *Basic* data includes much of the critical MS SQL data. Customers who want additional MS SQL data will want to capture the advanced data as well (this can be helpful for detailed SQL licensing analysis). More information about what is included in the *Basic* data and *Advanced* data can be found in the table below. ## How does it work? The Cloudamize software uses a PowerShell script to collect *Basic* and *Advanced* MS SQL data from servers. The Cloudamize agent (Windows) will almost always capture *Basic* MS SQL data successfully without using a PowerShell script. To collect the *Advanced* MS SQL data from the server, the Agent (and Agentless) both require PowerShell 5.1 or higher. If using the Agentless Data Collector, PowerShell 2.0 or higher must be installed on the **remote host** for Cloudamize to collect the *Basic* MS SQL Data. To collect the *Advanced* MS SQL Data from the server, PowerShell 5.1 or higher must be installed on the remote host. |--------------------------------------------------------------------------------------------------------------------------------------|-------|-----------| | Data | Agent | Agentless | | **Basic SQL DATA Collected** ||| | · SQL server instance ID | ✔ | ✔ | | · SQL server instance name | ✔ | ✔ | | · SQL server edition | ✔ | ✔ | | · SQL server version | ✔ | ✔ | | · SQL server patch level | ✔ | ✔ | | · SQL server service pack | ✔ | ✔ | | · SQL server bin path | ✔ | ✔ | | · SQL server data path | ✔ | ✔ | | · SQL server error log file | ✔ | ✔ | | · Database name: master, model. | ✔ | ✔ | | · Database size in MB | ✔ | ✔ | | · Database name and its size info | ✔ | ✔ | | · Core licenses text | ✔ | ✔ | | · Cluster name | ✔ | ✔ | | · Cluster state (If the SQL server belongs to the cluster or Not) | ✔ | ✔ | | · SQL server Status (if Server is active in the cluster) | ✔ | ✔ | | · SQL cluster owner host name | ✔ | ✔ | | · SQL server feature list | ✔ | ✔ | | · SQL server product info | ✔ | ✔ | | · SQL server uses HADR (High Availability and Disaster Recovery) | ✔ | ✔ | | · SQL server filestream enable level | ✔ | ✔ | | · Is Fulltext installed | ✔ | ✔ | | · Is Polybase installed | ✔ | ✔ | | · Collation content | ✔ | ✔ | | **Advanced SQL DATA Collected** ||| | · Cluster Quorum Type | ✔ | ✔ | | · PerfMon Mode | ✔ | ✔ | | · Availability Group Name | ✔ | ✔ | | · Availability Group Primary Replica Server Name | ✔ | ✔ | | · Availability Group Local Replica Role | ✔ | ✔ | | · Local Availability Group Replica Server Primary | ✔ | ✔ | | · Availability Group Replicas | ✔ | ✔ | | · Linked Server (Is sever a Linked server) | ✔ | ✔ | | · Command Shell Status (Enabled/Disabled) | ✔ | ✔ | | · SQL CLR Status (Common Language Runtime (CLR) integration is enabled or not) | ✔ | ✔ | | · Encryption Status (Enabled/Disabled) | ✔ | ✔ | | · Database Mirroring Status (Enabled/Disabled) | ✔ | ✔ | | · Database Replication Status (Enabled/ Disabled) | ✔ | ✔ | | · Maximum server memory | ✔ | ✔ | | · Number of databases | ✔ | ✔ | | · Total database size | ✔ | ✔ | | · Availability Group Readable Secondary (Description of secondary role connections) | ✔ | ✔ | | · Availability Group Synchronous Replication (The availability mode of the replica, (Asynchronous/ Synchronous/ Configuration only)) | ✔ | ✔ | | · Availability Group Failover Mode (Description of failover mode) | ✔ | ✔ | If you have any queries, please get in touch with the helpdesk via our [++Helpdesk Portal++](https://cloudreach-software.atlassian.net/servicedesk/customer/portal/9) or by email at [++helpdesk@cloudamize.com++](mailto:helpdesk@cloudamize.com). --- language: "en" --- # Billing Plan for Network Discovery ## Overview This introduces a dedicated billing plan for the **Network Discovery** plan in Cloudamize. The new plan enables partners and customers to leverage network discovery capabilities with clear, transparent billing and streamlined upgrade paths to more advanced plans. We have divided the sections below into Partner-wise and User-wise, and listed the changes that are incorporated as part of this Network Discovery plan. ## Partners: The partner will see a new option, **"** Network Discovery**"**, in the plan selection dropdown when adding a new order. ![Screenshot 2025-06-11 at 10.42.27 AM-20250611-051327.png](https://support.cloudamize.com/__attachments/a_156e754c0915d5cffcbd426d7c1611858f6a6584607316d0d70136b819cce410/Screenshot%202025-06-11%20at%2010.42.27%E2%80%AFAM-20250611-051327.png?cb=1f4ffdc73aedd31025e6c5f2017bd8e3) ## Customers: * Customers benefit from a clear, focused entry point for network discovery. * Below, we have mentioned the changes with respect to Network Discovery Customers ++**Discover Page:**++ * On the Discover page, the customer can view their Assessment Plan with their Plan name and status in the Assessment Details Section * In the **Setup and Inventory** settings menu, the customer will be automatically redirected to tabs related exclusively to **Network Discovery** features. ***All other tabs will be disabled.*** ++**Home Page:**++ * Except for the "**Discover** " Feature, all other features will be locked, and routes to these respective features will also be blocked. ![image-20260722-085312.png](https://support.cloudamize.com/__attachments/a_a1d418da2c7993c44d3c583ff390e7815e05cee555e7a5689307923bad8bd5f9/image-20260722-085312.png?cb=0f4ad2659027eb85047183b7a3951fb3) ## **Plan Upgrade Requests:** The "Network Discovery" customer will have an option to request a plan upgrade. The option to request a plan upgrade is provided at: * Home Page Banner * Discover-\>Assessment Details * Home Page-\> On Hover over Locked Feature cards. ![image-20260722-085622.png](https://support.cloudamize.com/__attachments/a_94cfbeaef0def2878715d98f261398fec3a60a79aed4e99ebcb1ae07dfe1fe1c/image-20260722-085622.png?cb=8e64a44911d370aa2bed3a8fef8909d8) ![Screenshot 2025-06-12 at 11.26.12 AM-20250612-055618.png](https://support.cloudamize.com/__attachments/a_26f687c94d1d8fadc289bf2537bc7bde2f45c9eb9b416040a50c8f8265d9fc42/Screenshot%202025-06-12%20at%2011.26.12%E2%80%AFAM-20250612-055618.png?cb=4d70e1fe00d0c173e85d4a4894f17f81) * On clicking on Upgrade Plan at any of the above-mentioned locations, a dialog will be opened for sending the Plan upgrade email, which can accept any customer input as additional comments(optional), and after clicking on Send Email, an Email Will be sent to [sales@cloudamize.com](mailto:sales@cloudamize.com) informing about the customer's upgrade request. ![Screenshot 2025-06-12 at 11.33.42 AM-20250612-060348.png](https://support.cloudamize.com/__attachments/a_4531b427a03a4d206f25997db3c7d8eb6dd60858c430bcc4937e6c41b5215f09/Screenshot%202025-06-12%20at%2011.33.42%E2%80%AFAM-20250612-060348.png?cb=8fa65a5dfca04f851ea7d4e606de3860) Sample Email: ![image-20250528-062704-20250612-060559.png](https://support.cloudamize.com/__attachments/a_4cd80802cc8e64fc6428d78d3ab2f5a8c4195f943496e35687ab2fae6e91903e/image-20250528-062704-20250612-060559.png?cb=da5cc32542a310851d9a33d99eaf4af0) ## Additional Notes * The expiry date for Network Discovery plans is capped at 30 days, and UI labels have been updated accordingly. * The plan upgrade process is fully auditable and integrated with existing support workflows. * The experience for **"Plan Edition"**customers would be unchanged. If you have any queries, please get in touch with the helpdesk via our [++Helpdesk Portal++](https://cloudreach-software.atlassian.net/servicedesk/customer/portal/9) or by email at [++helpdesk@cloudamize.com++](mailto:helpdesk@cloudamize.com). --- language: "en" --- # Classic Console is Retiring As of March 2025, Cloudamize are making the New UI (console-lite) as the default UI for the Cloudamize console. ## Whats Changing ? As part of transitioning to the New UI, Cloudamize are limiting access to the Classic Console by making the New UI the default. As of this release, features that were previously only supported on the Classic Console - **Designer and Migrator Canvas** - will be accessible from the new UI itself. This change renders the Classic Console entirely redundant. As a result: * The "Switch to old UI button" will no longer appear anywhere on the new UI * Attempting to access the old UI URL's will display appropriate messages and a link to navigate to the new UI ![Screenshot 2025-03-04 at 11.44.55 AM-20250304-061500.png](https://support.cloudamize.com/__attachments/a_5f701a1a643d462e872d11400fd85702280695e8b4df0f31aa39f4fe10019039/Screenshot%202025-03-04%20at%2011.44.55%E2%80%AFAM-20250304-061500.png?cb=3139545198f3ca6d6dbdebea23f25fe9) The new UI won't show the switch to button ![Screenshot 2025-03-04 at 11.47.36 AM-20250304-064140.png](https://support.cloudamize.com/__attachments/a_9f61a824e270ca802595f6c2041c2df4c5133811c88b6731e3564d55da58352d/Screenshot%202025-03-04%20at%2011.47.36%E2%80%AFAM-20250304-064140.png?cb=8d0bbb1bc2514d6b470acaeaddffde56) Designer can be opened from Overview dashboard on new UI ![Screenshot 2025-03-04 at 11.56.07 AM-20250304-062612.png](https://support.cloudamize.com/__attachments/a_0244863a4c3b807a502278ba5e8aff1ed3f7504f2bca9fdbcd72eb86c790ed37/Screenshot%202025-03-04%20at%2011.56.07%E2%80%AFAM-20250304-062612.png?cb=b10a6645bdeccc820426b4fb1ca98384) Classic Console's Designer can be accessed within new UI; provider can be changed from Platform Drop down at top of screen ![Screenshot 2025-03-04 at 11.58.06 AM-20250304-062811.png](https://support.cloudamize.com/__attachments/a_012108051cc18ddc0b2deb2352dac238ec233b2c8c9ab4ea3934a9759033a43e/Screenshot%202025-03-04%20at%2011.58.06%E2%80%AFAM-20250304-062811.png?cb=aa76316ea239c29dc49de10578520979) Classic Console's Migration planner Canvas can be accessed from Application Canvas tab from new UI's Plan page ![Screenshot 2025-03-04 at 12.16.27 PM-20250304-064633-20250731-124553.png](https://support.cloudamize.com/__attachments/a_d370dbea4232d70e37d57a47cadbfdf903b9d1ff6c8a199a2789b3c20cab3dad/Screenshot%202025-03-04%20at%2012.16.27%E2%80%AFPM-20250304-064633-20250731-124553.png?cb=96ae8b6c94304b1e6aa6704fa87f372f) When accessing Classic Console URL, a message to navigate to new UI are shown If you have any queries about the new UI functionality please refer to our KB documentation, or contact the technical helpdesk. --- language: "en" --- # Client App DNS Report The Cloudamize **Client App DNS Report** is a specialized report that focuses on network dependencies from a DNS perspective. While other reports may show IP-to-IP communication, this report specifically captures and maps DNS resolution requests from your source machines. This is a critical report for migrations, as it helps you identify which applications rely on specific hostnames and ensures you can correctly update DNS records in the cloud environment. This report shows **DNS activity** originating from machines in your environment, essentially tracking **what domain names client applications are querying**, and how frequently. **Steps to navigate to the Client App DNS Report:** 1. Log in to the console 2. Navigate to the Plan page of your completed assessment. ![Screenshot 2026-07-22 at 1.08.22 PM-20260722-073857.png](https://support.cloudamize.com/__attachments/a_77015b360e1c898b489153d8cf59b0e46954088d3e0b89dd290e0471dabea73e/Screenshot%202026-07-22%20at%201.08.22%E2%80%AFPM-20260722-073857.png?cb=76c65137fc56f1493e5553830e531a4a) 3. Click on the Reports Section as shown in the screenshot below under the Plan section. 4. Click on **Client App DNS** → **Detailed** for Client App DNS to download the report. ![Screenshot 2025-08-11 at 12.32.00 PM-20250811-070305.png](https://support.cloudamize.com/__attachments/a_7f8ccc856ef672c1ee3e27c4494fdaa98accf75079156a784d8e11771ee5b692/Screenshot%202025-08-11%20at%2012.32.00%E2%80%AFPM-20250811-070305.png?cb=324f240a1411fa93359b6ad59e19212d) | Column Name | Detailed Description | |----------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Application Name** | The name of the software application or service to which the DNS record belongs. This helps identify the purpose or business function the DNS entry supports (e.g., CRM system, internal API, analytics tool). | | **DNS Name** | The fully qualified domain name (FQDN) that maps to the application or asset. This is the human-readable address used to access the system over the network (e.g., `server1.company.com`). | | **IP Addresses** | The numeric network addresses (IPv4 or IPv6) associated with the DNS name. These are used by devices to locate and connect to the resource on a network. | | **Group Name** | The classification or grouping to which the asset belongs, often based on department, function, security zone, or ownership. This helps in organizing and managing assets logically. | | **Asset Name** | The registered name of the asset in the organization's asset inventory often represents a server, virtual machine, or network device associated with the application. | | **Instance Name** | A unique identifier for a specific instance of the asset or application. Useful in environments with multiple deployments of the same application (e.g., development, staging, production instances). | **Example Report:** [MigrationPlanner-ClientAppDNS-Report.xlsx](https://support.cloudamize.com/__attachments/a_fb4b979c3dbbf9be37df6f13f78b672c2ae8a1c057ce206aba4e1402de4c32cb/MigrationPlanner-ClientAppDNS-Report.xlsx.md?cb=791195bc5cb1678ead393d999623b363) If you have any queries, please get in touch with the helpdesk via our [++Helpdesk Portal++](https://cloudreach-software.atlassian.net/servicedesk/customer/portal/9) or by email at [++helpdesk@cloudamize.com++](mailto:helpdesk@cloudamize.com). --- language: "en" --- # Cloudamize ADC – Antivirus or Endpoint Detection (EDR) Flagging ## **Overview** During the deployment or operation of the **Cloudamize Agentless Data Collector (ADC)**, your Antivirus (AV) or Endpoint Detection and Response (EDR) solution (e.g., CrowdStrike, SentinelOne, Microsoft Defender) may flag ADC components as suspicious. This typically happens because the ADC: * Executes remote queries via **WMI** and **RPC**. * Runs automated inventory scripts. * Communicates with Cloudamize endpoints to upload encrypted metadata. ### **Issues seen** * The ADC installation fails, or files are automatically deleted. * Security logs report `CloudamizeCurl.exe` or `CloudamizeAgentlessDc.exe` as a "Potentially Unwanted Program" (PUP) or "Heuristic hit." ## **Troubleshooting Steps** ### **Exclusion \& Whitelisting** To ensure uninterrupted data collection, you should add the following directory and process exclusions to your security software. #### **1. Directory Exclusions** Exclude the following primary installation and data paths from real-time scanning: * `C:\Program Files\CloudamizeAgentlessDc\` * `C:\ProgramData\CloudamizeAgentlessDc\` #### **2. Process/Executable Exclusions** Whitelist the following specific binaries to allow them to execute and communicate over the network: * `CloudamizeAgentlessDc.exe` -- The primary collection engine. * `CloudamizeWatchdog.exe` -- Ensures the agent remains running. * `CloudamizeCurl.exe` -- Handles the secure transmission of data to the Cloudamize console. * `CloudamizeUI.exe` -- The local management interface. #### **3. Network/Firewall Whitelisting** If your AV includes a network firewall, ensure outgoing traffic is permitted to the Cloudamize collection endpoints (typically over port **443/HTTPS**). ## **Reinstallation Guidelines** If the ADC has been flagged and quarantined, a simple reinstallation on the same host is often unsuccessful due to residual files and registry flags left behind during the automated uninstallation process. * **Recommendation:** Cloudamize recommends performing a **fresh installation** of the ADC on a **different host** that meets all system prerequisites. Agentless Installation Prerequisites are available in our KB [**here**](https://support.cloudamize.com/kb/agentless-installation-prerequisites). ### **Backing Up Your Host List** If you have already added inventory/hosts to your collector, you must back up your configuration files before uninstalling. Failure to do so will result in the loss of your "Added Hosts" list. ### **1. Locate and Save Host Files** The following files contain your configuration and added nodes: * `HostInfo.xml` * `HostInfoBackup.xml` **File Locations:** * `C:\Program Files (x86)\CloudamizeAgentlessDC\` > **Note:** These files can only be accessed by accounts belonging to the **Local Administrators** group. Copy these files to a neutral temporary folder, such as `C:\Temp\`, before proceeding with uninstallation. ### **2. Recovery and Migration Process** Once your files are safely backed up, follow these steps to restore your collector: 1. **Uninstall:** Remove the flagged Cloudamize ADC from the original machine. 2. **Download:** Obtain the latest version of the ADC from the Cloudamize portal. 3. **New Install:** Install the ADC on a fresh host (or the original host if all remnants have been cleared and whitelisting is active). 4. **Restore:** \* Navigate to the installation folder on the new machine. * Copy your backed-up `HostInfo.xml` and `HostInfoBackup.xml` back into the directory. 5. **Restart Services:** Open `services.msc` and restart: * **Cloudamize Watchdog** * **Cloudamize Agentless** If the issue persists, please capture a screenshot of the error output and collect the `log_backup.txt` file from the following directory on the Cloudamize Agentless DC: `C:\Program Files (x86)\CloudamizeAgentlessDc\log_backup.txt` Please attach both the screenshot and the log file in an email to [**helpdesk@cloudamize.com**](mailto:helpdesk@cloudamize.com) for further investigation. If you have any queries, please get in touch with the helpdesk via our Helpdesk Portal or by email at [helpdesk@cloudamize.com](mailto:helpdesk@cloudamize.com). [Next Page](https://support.cloudamize.com/llms-full.txt/1)