The quota system on the platform sets limits on specific features, resources, and account usage for users using AccuWeb.Cloud dashboard.<\/p>\n
These limits can be managed by cluster administrators via JCA:<\/p>\n
Below is a complete list of all existing quotas, sorted alphabetically, with detailed descriptions. The last two columns display example option values for different group types (like trial and billing), which cluster admins can manually adjust if needed.<\/p>\n
Quotas<\/strong><\/td>\n| Units<\/strong><\/td>\n | Trial<\/strong><\/td>\n | Billing<\/strong><\/td>\n<\/tr>\n | account.charge.balance.first<\/strong><\/p>\n | This quota controls how charges are applied to accounts. If the value is 1, it means the main balance is charged first. If the value is 0, bonuses are used first, and then any remaining amount is taken from the main balance.<\/td>\n availability<\/td>\n | 0<\/td>\n | 0<\/td>\n<\/tr>\n | account.convert.after.first.fund.enabled<\/strong><\/p>\n | Choose 1 if you want to enable account upgrades to the billing group only when the balance is funded, not immediately after submitting the upgrade form.<\/td>\n availability<\/td>\n | 0<\/td>\n | n\/a<\/td>\n<\/tr>\n | account.convert.after.login.enabled<\/strong><\/p>\n | Set it to 1 if you want accounts to be automatically converted to the billing group immediately after registration.<\/td>\n availability<\/td>\n | 0<\/td>\n | n\/a<\/td>\n<\/tr>\n | account.destroy.period<\/strong><\/p>\n | The time after which a deactivated account gets permanently deleted. This depends on the account.trial.destroy and account.destroy system settings.<\/td>\n day<\/td>\n | 30<\/td>\n | 60<\/td>\n<\/tr>\n | account.minbalance<\/strong><\/p>\n | The minimum amount of money (in the currency used) that needs to be in the account balance to prevent deactivation (it can be a negative amount).<\/td>\n money<\/td>\n | 0<\/td>\n | 0<\/td>\n<\/tr>\n | account.personal.min.threshold<\/strong><\/p>\n | When the account balance goes below this value, the platform begins sending warning emails to the user. Set this quota to 0 to stop these notifications.<\/td>\n money<\/td>\n | n\/a<\/td>\n | 50<\/td>\n<\/tr>\n | account.post.invoice.generation.enabled<\/strong><\/p>\n | This allows turning off invoice creation for users in the POST group, which might be needed for complex billing setups. For instance, if users are billed through an external billing system.<\/td>\n availability<\/td>\n | n\/a<\/td>\n | 1<\/td>\n<\/tr>\n | account.subscriptions.enabled<\/strong><\/p>\n | Allowing users to buy a subscription-based service.<\/td>\n availability<\/td>\n | 0<\/td>\n | 1<\/td>\n<\/tr>\n | account.subscriptions.resources.destroy.period<\/strong><\/p>\n | The number of days environments suspended due to unpaid subscriptions should be kept before they are destroyed.<\/td>\n day<\/td>\n | 14<\/td>\n | 14<\/td>\n<\/tr>\n | account.subscriptions.withdraw.type<\/strong><\/p>\n | Select how subscription invoices are paid: 1 for using account balance and bonuses, 2 for using an external invoice.<\/td>\n type<\/td>\n | 1<\/td>\n | 1<\/td>\n<\/tr>\n | account.trial.bonus<\/strong><\/p>\n | The amount of bonuses (in the currency used) a user receives for using a trial account. Once all the bonuses are used up, the account will be deactivated. To prevent the account from being permanently deleted afterward, it should be converted to a billing account.<\/td>\n money<\/td>\n | 0<\/td>\n | n\/a<\/td>\n<\/tr>\n | account.trialperiod<\/strong><\/p>\n | The duration that a trial account can be used. After this period ends, the trial account is deactivated. To prevent the account from being permanently deleted afterward, it should be converted to a billing account.<\/p>\n You can set this quota to “-1”<\/strong> to disable the time limit for the trial period.<\/td>\n The time allowed for transferring money to the account after upgrading. This prevents unnecessary deactivation while waiting for the payment to complete.<\/td>\n Amount of bonuses (according to the currency used) an existing billing user can receive as a bonus upon each refill of the account balance.<\/td>\n The percentage of the payment that an existing billing user can receive as a bonus each time they refill their account balance.<\/td>\n The amount of bonuses (in the currency used) that a destroyed or deactivated billing user can receive when they refill their account balance and reactivate their account.<\/td>\n The percentage of the payment that a destroyed or deactivated billing user can receive as a bonus when they refill their account balance, thereby reactivating their account.<\/td>\n The amount of bonuses (in the currency used) a user can get for their first payment after converting their account (can be zero).<\/td>\n The number of days after signing up when the reward system for converting a newly registered trial account ends.<\/td>\n The percentage of the first payment made after converting the account that a user can receive as a bonus (can be zero).<\/td>\n The number of days after signing up when the reward system begins for converting a newly registered trial account.<\/td>\n Allowing users to create and control custom rules for account collaboration features.<\/td>\n The maximum disk cache size (hard type) for containers.<\/td>\n The minimum disk cache size (hard type) for containers.<\/td>\n The disk cache size (hard type) for containers, based on the number of cloudlets, is calculated as follows:<\/p>\n dcachesize = MIN(MAX(dcachesize.per.cloudlet * cloudlets, dcachesize.minimum), dcachesize.maximum)<\/td>\n The maximum disk cache size (soft type) for containers.<\/td>\n The minimum disk cache size (soft type) for containers.<\/td>\n The disk cache size (soft type) for containers, based on the number of cloudlets, is calculated as follows:<\/p>\n dcachesize = MIN(MAX(dcachesize.per.cloudlet * cloudlets, dcachesize.minimum), dcachesize.maximum)<\/td>\n The bandwidth of a container for disk input\/output operations. This value is set when the container is created, so changing it won’t affect existing containers.<\/td>\n The maximum number of disk input\/output operations a container can do per second. This limit is set when the container is created, so changing it won’t affect existing containers.<\/td>\n The maximum disk space users can allocate per container (excluding Shared Storage).<\/td>\n Choose the confirmation type for removing an environment: 0 for password, 1 for environment name.<\/td>\n Allowing end-users to use custom Docker containers.<\/td>\n The maximum number of extra domains allowed per environment.<\/td>\n The maximum number of connections allowed for a single node endpoint.<\/td>\n Allowing users to use the endpoints feature.<\/td>\n Allowing users to use the Environment Export\/Import option.<\/td>\n Allowing end-users to bind custom domains to environments and swap domains.<\/td>\n Allowing users to assign Public IPv4<\/a> addresses to their containers.<\/td>\n The maximum number of Public IPv4 addresses allowed per environment.<\/td>\n The maximum number of Public IPv4 addresses allowed per node.<\/td>\n Ability to delete a node’s primary IP address, even if it’s not the last one added to the container.<\/td>\n Allowing users to assign Public IPv6 addresses to their containers.<\/td>\n The maximum number of Public IPv6 addresses allowed per environment.<\/td>\n The maximum number of Public IPv6 addresses allowed per node.<\/td>\n Allowing users to enable the High Availability<\/a> option.<\/td>\n Enabling Built-In SSL<\/a> functionality for end-users.<\/td>\n The maximum number of cloudlets cloudlets that can be allocated for each container.<\/td>\n The highest number of environments that users are allowed to create.<\/td>\n The maximum total number of nodes allowed to be added to a single environment.<\/td>\n The maximum number of nodes of the same type is allowed<\/a> to be added within a single environment.<\/td>\n Enabling environment migration between regions.<\/td>\n The maximum number of additional node subdomains allowed per environment.<\/td>\n Enables or disables the ability to attach additional node subdomains using “-“<\/strong> format, like ${subDomain}-${envName}.${platformDomain}.<\/strong><\/td>\n The maximum number of additional subdomains per environment layer.<\/td>\n Enables or disables the ability to attach additional layer subdomains using “-“<\/strong> format, like ${subDomain}-${envName}.${platformDomain}<\/strong>.<\/td>\n Allowing restriction of end-users’ SSH access to specific nodes listed in the jelastic.ssh.nodetype.restriction.list system setting.<\/td>\n Allowing users to create Virtual Private Server (VPS)<\/a> containers.<\/td>\n Enabling the container firewall<\/a> feature for users.<\/td>\n Enabling an anti-phishing banner for all trial account environments.<\/td>\n The maximum number of connections allowed from a specific IP address per container.<\/td>\n The maximum amount of data (per container) allowed to be transmitted within a specific timeframe.<\/p>\n Note:<\/strong> This limit is set during container creation and cannot be changed for existing containers.<\/td>\n If the system setting jelastic.remove.data.enabled is true, it automatically deletes personal data from destroyed accounts after a specified number of days. You can choose the removal mode using the jelastic.data.remove.mode setting.<\/td>\n Enabling built-in platform notifications for billing-related events, such as account upgrades, deactivation, destruction, and receiving bonus funds for conversions.<\/td>\n Enabling users to use a sendmail service directly from a container without needing a Public IP attached.<\/td>\n The maximum number of user Custom SSL certificates can be attached through a Shared Load Balancer.<\/a><\/td>\n The amount of time an environment can idle before it goes into hibernation. Setting it to 0 disables the automatic suspension of inactive environments.<\/td>\n The number of hours before a hibernated environment will be completely stopped. Setting it to -1 disables automatic stopping of suspended environments, while 0 causes an immediate stop (skipping the hibernation state).<\/td>\n Enabling users to connect to their containers using SSH protocol.<\/td>\n The most disk space users can assign to each Shared Storage container.<\/a><\/p>\n This amount must be at least as large as the disk.limitation quota.<\/td>\n Allowing users to connect an internal IP address to a VPS node instead of the usual external one.<\/p>\n Note: It is not recommended to enable this option for all users due to security concerns. When an internal IP is used with a VPS node, users can access and scan the internal platform network, identify servers, and more. Therefore, this option should only be enabled for specific users upon request and with caution.<\/td>\n Enabling users to create virtual machines (VMs).<\/td>\n Allowing end-users to use .NET\/Windows hosting support.<\/td>\n |