-
Notifications
You must be signed in to change notification settings - Fork 80
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: Improving security and limits sections (#530)
Just trying out to edit the first two pages. After this, I jump on major refactorings :) I changed the display of limits a bit to support the new pricing plan structure where limits will be connected with the plan: <img width="853" alt="obrazek" src="https://user-images.githubusercontent.com/594801/221872325-175a96bf-271e-4d2c-9627-eff12d28c33a.png"> <img width="1133" alt="obrazek" src="https://user-images.githubusercontent.com/594801/221872209-9bcc6f75-4312-43d8-a414-ab631292ec6b.png">
- Loading branch information
Showing
4 changed files
with
143 additions
and
40 deletions.
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,50 +1,134 @@ | ||
--- | ||
title: Limits | ||
description: Learn the Apify platform's resource capability and limitations such as max memory, disk size and number of actors/tasks per user or schedule. | ||
description: Learn the Apify platform's resource capability and limitations, such as max memory, disk size, and the number of actors and tasks per user. | ||
sidebar_position: 7.8 | ||
slug: /actors/limits | ||
--- | ||
|
||
# Limits {#limits} | ||
|
||
**Learn the Apify platform's resource capability and limitations such as max memory, disk size and number of actors/tasks per user or schedule.** | ||
**Learn the Apify platform's resource capability and limitations, such as max memory, disk size, and the number of actors and tasks per user.** | ||
|
||
--- | ||
|
||
The tables below demonstrate the Apify platform's default resource limits. | ||
|
||
If needed, the limits shown below can be increased on paid accounts. For details, contact us on **[email protected]** or using the chat icon in the bottom-right corner. | ||
|
||
* Maximum combined memory of all running jobs. | ||
* Maximum number of actors per user. | ||
* Maximum number of tasks per user. | ||
|
||
## Actor limits {#actor-limits} | ||
|
||
| Description | Value | | ||
|------------------------------------------------------------------|---------------------------------------------------------------------------------------| | ||
| Build memory size | 4,096 MB (2,048 MB on the free plan)<!-- ACTOR_LIMITS.BUILD_DEFAULT_MEMORY_MBYTES --> | | ||
| Run minimum memory | 128 MB<!-- ACTOR_LIMITS.MIN_RUN_MEMORY_MBYTES --> | | ||
| Run maximum memory | 32,768 MB<!-- ACTOR_LIMITS.MAX_RUN_MEMORY_MBYTES --> | | ||
| Maximum combined memory of all running jobs <br/>(Free plan) | 4,096 MB<!-- ACTOR_LIMITS.FREE_PLAN_MAX_MEMORY_MBYTES --> | | ||
| Maximum combined memory of all running jobs <br/>(Personal plan) | 32,768 MB<!-- ACTOR_LIMITS.PERSONAL_PLAN_MAX_MEMORY_MBYTES --> | | ||
| Maximum combined memory of all running jobs <br/>(Team plan) | 131,072 MB<!-- ACTOR_LIMITS.TEAM_PLAN_MAX_MEMORY_MBYTES --> | | ||
| Build timeout | 1800 secs<!-- ACTOR_LIMITS.BUILD_TIMEOUT_SECS --> | | ||
| Build/run disk size | 2x job memory limit<!-- ACTOR_LIMITS.RUN_DISK_TO_MEMORY_SIZE_COEFF --> | | ||
| Memory per CPU core | 4,096 MB<!-- ACTOR_LIMITS.RUN_MEMORY_MBYTES_PER_CPU_CORE --> | | ||
| Build/run maximum log size | 10,485,760 characters<!-- ACTOR_LIMITS.LOG_MAX_CHARS --> | | ||
| Maximum number of dataset columns for xlsx format | 2,000 columns | | ||
| Maximum size of input schema for a task/actor | 100 kB<!-- ACTOR_LIMITS.INPUT_SCHEMA_MAX_BYTES --> | | ||
|
||
## Platform limits {#platform-limits} | ||
|
||
| Description | Value | | ||
|--------------------------------------------------------------------|-------------------------------------------------------------------------------------| | ||
| Maximum number of actors per user | 100<!-- DEFAULT_PLATFORM_LIMITS.MAX_ACTORS_PER_USER --> | | ||
| Maximum number of tasks per user | 1000<!-- DEFAULT_PLATFORM_LIMITS.MAX_TASKS_PER_USER --> | | ||
| Maximum number of schedules per user | 100<!-- DEFAULT_PLATFORM_LIMITS.MAX_SCHEDULES_PER_USER --> | | ||
| Maximum number of webhooks per user | 100<!-- DEFAULT_PLATFORM_LIMITS.MAX_TASKS_PER_USER --> | | ||
| Maximum number of concurrent actor runs per user for free accounts | 25<!-- DEFAULT_PLATFORM_LIMITS.FREE_ACCOUNT_MAX_CONCURRENT_ACTOR_RUNS_PER_USER --> | | ||
| Maximum number of concurrent actor runs per user for paid accounts | 250<!-- DEFAULT_PLATFORM_LIMITS.PAID_ACCOUNT_MAX_CONCURRENT_ACTOR_RUNS_PER_USER --> | | ||
| Maximum number of actors per schedule | 10<!-- DEFAULT_PLATFORM_LIMITS.MAX_ACTORS_PER_SCHEDULER --> | | ||
| Maximum number of tasks per schedule | 10<!-- DEFAULT_PLATFORM_LIMITS.MAX_TASKS_PER_SCHEDULER --> | | ||
The tables below demonstrate the Apify Platform's default resource limits. For API limits such as rate limits and max payload size, see the [API documentation](https://docs.apify.com/api/v2#/introduction/rate-limiting). | ||
|
||
> If needed, the limits shown below can be increased on paid accounts. For details, contact us at **[email protected]** or using the chat in [Apify Console](https://console.apify.com/) under the "Help & Resources → Contact Support". | ||
## Actor runtime limits {#actor-limits} | ||
|
||
<table> | ||
<thead> | ||
<tr> | ||
<th rowspan="2">Description</th> | ||
<th colspan="4">Limit for plan</th> | ||
</tr> | ||
<tr> | ||
<th>Free</th> | ||
<th>Personal</th> | ||
<th>Team</th> | ||
<th>Enterprise</th> | ||
</tr> | ||
</thead> | ||
<tbody> | ||
<tr> | ||
<td>Build memory size</td> | ||
<td>2,048 MB</td> | ||
<td colspan="3">4,096 MB</td> | ||
</tr> | ||
<tr> | ||
<td>Run minimum memory</td> | ||
<td>128 MB</td> | ||
<td colspan="3">128 MB</td> | ||
</tr> | ||
<tr> | ||
<td>Run maximum memory</td> | ||
<td>4,096 MB</td> | ||
<td colspan="3">32,768 MB</td> | ||
</tr> | ||
<tr> | ||
<td>Maximum combined memory of all running jobs</td> | ||
<td>4,096 MB</td> | ||
<td>32,768 MB</td> | ||
<td colspan="2">131,072 MB</td> | ||
</tr> | ||
<tr> | ||
<td>Build timeout</td> | ||
<td colspan="4">1800 secs</td> | ||
</tr> | ||
<tr> | ||
<td>Build/run disk size</td> | ||
<td colspan="4">2× job memory limit</td> | ||
</tr> | ||
<tr> | ||
<td>Memory per CPU core</td> | ||
<td colspan="4">4,096 MB</td> | ||
</tr> | ||
<tr> | ||
<td>Maximum log size</td> | ||
<td colspan="4">10,485,760 characters</td> | ||
</tr> | ||
</tbody> | ||
</table> | ||
|
||
## Apify Platform limits {#platform-limits} | ||
|
||
<table> | ||
<thead> | ||
<tr> | ||
<th rowspan="2">Description</th> | ||
<th colspan="4">Limit for plan</th> | ||
</tr> | ||
<tr> | ||
<th>Free</th> | ||
<th>Personal</th> | ||
<th>Team</th> | ||
<th>Enterprise</th> | ||
</tr> | ||
</thead> | ||
<tbody> | ||
<tr> | ||
<td>Maximum number of dataset columns for tabular formats (XLSX, CSV, ...)</td> | ||
<td colspan="4">2000 columns</td> | ||
</tr> | ||
<tr> | ||
<td>Maximum size of actor input schema</td> | ||
<td colspan="4">100 kB</td> | ||
</tr> | ||
<tr> | ||
<td>Maximum number of actors per user</td> | ||
<td colspan="4">100</td> | ||
</tr> | ||
<tr> | ||
<td>Maximum number of tasks per user</td> | ||
<td colspan="4">1000</td> | ||
</tr> | ||
<tr> | ||
<td>Maximum number of schedules per user</td> | ||
<td colspan="4">100</td> | ||
</tr> | ||
<tr> | ||
<td>Maximum number of webhooks per user</td> | ||
<td colspan="4">100</td> | ||
</tr> | ||
<tr> | ||
<td>Maximum number of actors per schedule</td> | ||
<td colspan="4">10</td> | ||
</tr> | ||
<tr> | ||
<td>Maximum number of tasks per schedule</td> | ||
<td colspan="4">10</td> | ||
</tr> | ||
<tr> | ||
<td>Maximum number of concurrent actor runs per user </td> | ||
<td>25</td> | ||
<td colspan="3">250</td> | ||
</tr> | ||
</tbody> | ||
</table> | ||
|
||
## Usage limits {#platform-limits} | ||
|
||
The Apify platform also introduces usage limits based on the billing plan to protect users from accidental overspending. View these limits and adjust your maximum usage limit in [Apify Console](https://console.apify.com/billing#/limits): | ||
|
||
<img src={require("./images/limits/usage-limits.png").default} title="Apify Security Whitepaper" /> |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -11,6 +11,25 @@ slug: /actors/security | |
|
||
--- | ||
|
||
## Security Whitepaper | ||
|
||
At Apify, security is the top priority of our daily work. Security best practices are reflected in our development, deployment, monitoring, and project management processes. | ||
Read the Apify Security Whitepaper for a full description of Apify's measures and commitments to security: | ||
|
||
<a href="https://apify.com/security-whitepaper.pdf" target="_blank" title="Apify Security Whitepaper"> | ||
<img src={require("./images/security/whitepaper-cover.png").default} width="50%" title="Apify Security Whitepaper" /> | ||
</a> | ||
|
||
## Reporting a vulnerability | ||
|
||
If you notice or suspect a potential security breach, please report this immediately to our security team at [[email protected]](mailto:[email protected]), including all the technical details. | ||
|
||
|
||
The total compensation for your report will be highly dependent on the vulnerability's severity, complexity, and exploitability. Our internal security team always verifies your reports. | ||
We also factor in various risks associated with that vulnerability and the significance of its impact if we experience an attack. | ||
|
||
We strive to reply to all reports within 5 working days. However, depending on the complexity of the issue or our current workload, our response might take longer. | ||
|
||
## Securing your data | ||
|
||
Read the [Apify Security Whitepaper](https://apify.com/security-whitepaper.pdf) for a full description of Apify's measures and commitments to security. | ||
The Apify platform provides multiple ways to secure your data. This includes [encrypted environment variables](./development/environment-variables) to store your configuration secrets and [encrypted input](./development/secret-input) to secure the input parameters of your actors. |