Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

Q: What types of input data streams does Cloudamize support?

A: Cloudamize supports VMware ESX/ESXi environments, Microsoft Hyper-V, and physical servers (Windows and Linux).

Q: Which IaaS providers does Cloudamize support?

A: Cloudamize supports Amazon Web Services, Google Cloud Platform, and Microsoft Azure.

Q: Does Cloudamize support standalone ESXi?

A: No, Cloudamize only supports ESXi through vCenter.

Q: What is the assessment life cycle?

A: See the following:

Event

Result

Account creation

Access key generates

Agent installation

Assessment can be started

Assessment is started

Data collection begins

Data collection completes

Results processing begins

Results processing completes

Results are delivered

Subscription period ends

Portal access terminates


Q: Do we have any visibility via Cloudamize on what traffic that goes via the Netscalers?

A: Cloudamize does not support the data collection from the container/Pod. The Cloudamize Agent may be able to collect the data if installed on individual servers but not the container itself. Cloudamize doesn’t support Kubernetes/Container instance recommendations. Currently, we only support VM recommendations.

Q: Could you explain how cache memory is measured and processed in the reports at the end of the measurements?
A. Cloudamize queries the OS directly on cached memory, but does not display this info directly in the results. The Sizing results consider cache memory usage when determining memory usage. Memory usage = Total memory - free Memory - cached. The only related metric we expose is the peak used memory in the infrastructure details. Currently Available (GB): Available memory on the customer’s machine. Peak Used (GB): 95th percentile of all observed/adjusted daily peak memory usage on the customer machine.

Q: Are network-layer vulnerability scans completed regularly as prescribed by industry best practices Please describe scope/coverage scan areas?

A. Yes, all assets on weekly basis

Q: Do Cloudamize regularly undertake a patching regime on their server estate?

A. Every 4 weeks or earlier if required

Q: What monitoring tools are in place in terms of DLP (Data Loss Prevention) and intrusion detection?

A. Alert Logic. IDS/Log management

Q: Does the Cloudamize capture certificate information from the nodes?

A. No, Cloudamize doesn’t capture certificate-related information from the nodes.

Q: Does Cloudamize capture the PAAS services details and how will it capture?

A. Cloudamize do not collect any PAAS service details in general. Only Infrastructure details to provide respective recommendations on the desired cloud.

Q: Will CloudAmize gather the SSIS packages installation details on the server?

A. Unfortunately, Cloudamize does not gather the SSIS packages installation details on the server

Q: Does Cloudamize support the use of SSH keys for authentication on Linux servers, instead of entering a username and password?

A. The Cloudamize Agentless Data Collector or Agent is not designed to use public keys, and only supports username/password method for now.

Q: Does cloudamize supports SAML authentication?

A. The Cloudamize is not designed to use SAML authentication, and only supports the username/password method for now.

Q: The user doesn't want to send their data to Cloudamize SaaS server, is there a way to store the data locally in their premises and do assessment on top of it?

A. This is not possible, as the data needs to exist in our collection databases for us to perform processing tasks, and to make it available to view on the portal.

Q: Will SSE server credentials be required to complete the machines discovery?

A. No, SSE credentials are not amongst our requirements for machine discovery and communication to the Cloudamize end point servers.


  • No labels