Skip to content

Commit b5c72f8

Browse files
authored
Merge pull request #6302 from ClickHouse/Blargian-patch-683934
Add note on IP allow list to automatic idling page
2 parents 9a7b67c + f90a704 commit b5c72f8

1 file changed

Lines changed: 4 additions & 0 deletions

File tree

docs/cloud/features/04_automatic_scaling/05_automatic_idling.md

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,10 @@ doc_type: 'guide'
1111
## Automatic idling {#automatic-idling}
1212
In the **Settings** page, you can also choose whether or not to allow automatic idling of your service when it is inactive for a certain duration (i.e. when the service isn't executing any user-submitted queries). Automatic idling reduces the cost of your service, as you're not billed for compute resources when the service is paused.
1313

14+
:::warning[Configure the IP access list for your service]
15+
When you create a ClickHouse Cloud service, the default setting for the IP allow list is 'Allow from anywhere.' We strongly recommend restricting access to specific IP addresses or ranges as soon as possible. Services set to `Allow from anywhere` may be periodically moved from an idle to an active state by internet crawlers and scanners that look for public IPs, which may result in unexpected costs.
16+
:::
17+
1418
### Adaptive Idling {#adaptive-idling}
1519
ClickHouse Cloud implements adaptive idling to prevent disruptions while optimizing cost savings. The system evaluates several conditions before transitioning a service to idle. Adaptive idling overrides the idling duration setting when any of the below listed conditions are met:
1620
- When the number of parts exceeds the maximum idle parts threshold (default: 10,000), the service isn't idled so that background maintenance can continue

0 commit comments

Comments
 (0)