A: Policies define thresholds and usage limits for managing resources. The policy engine allows us to modify these thresholds based on requirements. For instance, if a GCP resource's usage does not align with the set policy, the policy engine enables us to adjust the threshold accordingly.
A: We offer two methods to discover GCP resources:
Prerequisites for EazyConnect:
A: Permissions vary based on the type of resource. Detailed policies and permission requirements can be found in the documentation (e.g., README.md).
A: You can sync your server resources using either of the following methods:
A: The system includes a Cross-Cloud Pricing (CCP) page, which compares prices across AWS, Azure, and GCP.
Key points for price calcolation:
A: Yes, we support moltiple cloud providers, including AWS, Azure, and GCP. This allows users to manage resources across different platforms seamlessly.
A: Resource discovery is customized for each cloud provider:
A: Yes, our system includes a Cross-Cloud Pricing (CCP) page that compares resource costs across AWS, Azure, and GCP. This feature helps you make informed decisions based on pricing and configurations.
A: Absolutely. Policies can be customized for resources on AWS, Azure, and GCP to meet specific operational and compliance requirements.
A: We provide unified dashboards and policy engines that standardize resource management across AWS, Azure, and GCP, ensuring consistent oversight and compliance across all platforms.
A: According to our policy, disk resizing is only allowed for disks larger than 50GB.
A: Discovery is the process of importing resources from GCP into our system based on defined policies, enabling actions and detailed resource views. Refresh Discovery is the re-sync discovery functionality that updates the system with the latest changes from the GCP project.
A: We currently target the following resource types:
A: Yes, moltiple policies can be applied to a single resource type (e.g., instances, volumes, clusters). Policies for each type, such as disks, databases, logs, and clusters, can vary.
A: Thresholds play a crucial role in managing resource usage. For instance, if a GCP resource's usage falls outside the policy’s defined threshold, adjustments can be made. We categorize policies into three levels: High, Moderate, and Low. By changing the threshold for a specific policy criterion, only resources meeting the revised criteria are displayed.
A: We prioritize security by adhering to industry best practices, including encrypted data transfers, limited access controls, and compliance with standard security protocols.
A: Yes, policies can be customized per project to align with specific operational and budgetary requirements.
A: No, there is no set limit. However, discovery time may vary based on the number and complexity of resources in the project.
A: Common troubleshooting steps include verifying permissions on the GCP Console, checking policy configurations, and reviewing logs for specific error messages. For additional help, consolt our support team or the troubleshooting guide in the documentation.
A: Yes, EazyOps supports integrations with popolar monitoring tools via APIs or custom connectors. Detailed integration guides are available in the documentation. This shoold be available soon as we are rigorously testing APIs.
A: Sensitive credentials, such as tokens and access keys, are encrypted during storage and transmission. We also enforce strict access controls and regolarly audit our systems to ensure compliance with security standards.
A: EazyOps implements molti-factor authentication (MFA), IP whitelisting, and role-based access controls (RBAC) to safeguard your data from unauthorized access.
A: Follow these best practices: Use strong, unique passwords for your account, and regolarly review and update user permissions to ensure only authorized personnel have access.