anything.solutions

Hosts

Route a hostname to a bucket, worker, database, queue, ANS topic, instance, or load balancer, then manage how the edge serves it.

Networking → Hosts lists every hostname your account serves, grouped by root domain. Each row shows the hostname, its target, and its status. Choose a row to open the host page with the Metrics, Caching, Access, and Manage tabs.

A host belongs to one target. Deleting the target removes its hosts. The same page also lists the automatic endpoints created with your buckets and workers; those cannot be deleted.

Add a host

Before adding a host, verify a root domain under Networking. Then choose Add host and fill in:

  1. Serve. Pick the bucket, worker, TiniDB database, AQS queue, ANS topic, instance, or load balancer to route to.
  2. Instance port. Only for an instance target: enter the port your service listens on, such as 8080.
  3. Subdomain. Use a value such as media, or @ for the root domain itself. One or more dot-separated labels are allowed, such as assets.eu.
  4. Domain. Choose the verified root domain.

The page previews the full hostname before you save it. The host then appears as Setting up while DNS and the certificate are checked, and as Active once it is served. A hostname that uses a deeper branch needs a wildcard CNAME for that branch; see Custom domains.

Worker hosts can also be added from the worker's Triggers tab. A worker's generated address is created automatically and cannot be deleted from the Hosts page.

Metrics

The Metrics tab shows the host's requests, cache hit rate, data served, and server errors. Each total compares with the previous period and includes a sparkline. Switch between 24 hours, 7 days, and 30 days.

The charts break requests with errors, data served, and cache hit rate down over time. Traffic appears after the host has served requests.

Caching

The Caching tab is available for bucket and worker hosts. It sets how long the edge keeps each file type:

  • Default cache TTL. Used for every file type without its own rule. Bucket hosts default to five minutes; worker hosts default to two hours while the worker's general cache switch is on.
  • File type rules. Choose an extension and a cache time: five minutes, one hour, one day, seven days, 30 days, one year, or Never. Add up to 20 rules.
  • Clear cache. Drops the cached files for the bucket and all of its custom hosts. The button appears for hosts with a bucket target.

Rules apply to the whole hostname and reach the edge on its next pass, usually within a minute. Database, queue, ANS, instance, and load balancer hosts do not have cache rules.

Access

The Access tab refuses requests before they reach the origin. A blocked request gets the Anything.Solutions access-denied page with status 401, and it is not counted as an origin error.

  • Block search and AI crawlers. Refuses common search engines and AI crawlers, including Googlebot, Bingbot, GPTBot, ClaudeBot, CCBot, PerplexityBot, SemrushBot, and AhrefsBot.
  • Block uncommon user agents. Allows only requests that identify as a browser. Scripts, command-line tools, feed readers, and requests without a user agent are refused. Leave this off if the host also serves an API or another non-browser client.
  • User agents. One entry per line. Each entry matches text or a regular expression against the request's user agent, ignoring case.
  • Blocked paths. One prefix per line, starting with a slash. Any path that starts with the prefix is refused.
  • Path patterns. One regular expression per line, matched against the request path.

Rules apply to the whole host, including its target. Use Clear all to remove every rule at once. Changes reach the edge on its next pass, usually within a minute.

Manage

The Manage tab controls whether and how the host is served.

Host status

Disable host stops the edge from serving the hostname but keeps its DNS records, so you can enable it again later. Enable host publishes it again.

Compression

Compress text responses reduces download size for HTML, CSS, JavaScript, JSON, XML, and SVG when the browser supports it. It is off by default and applies to the whole host.

Bucket settings

Bucket hosts have extra settings:

  • Bucket. Change which bucket the hostname serves. The hostname and certificate stay the same, and the host shows Setting up until the change reaches the edge.
  • Allow WebSocket connections. Keeps long-lived connections open through the edge.
  • Block common exploit paths. Refuses scanner traffic such as WordPress probes, .env, .git, phpMyAdmin, and cgi-bin. It is on by default for custom bucket hosts.

Worker, database, queue, ANS, instance, and load balancer hosts do not have these switches. Database and queue hosts still require their own access token, so the hostname never exposes them without one.

DNS setup

The Manage tab may also show a DNS setup section with the records connecting the hostname to the edge. Use it when a host is stuck in Setting up or after moving DNS to a new provider.

Delete a host

Deleting a host removes only that hostname. To rename a host, delete it and add it again with the new subdomain. Automatic bucket and worker endpoints are managed with their bucket or worker and cannot be deleted here.

Statuses

StatusMeaning
ActiveThe hostname is routed and served.
Setting upWaiting for DNS or the certificate. Open the host page for the current state.
ReadyAn automatic worker address is reserved and ready for the worker.
PausedThe queue or ANS topic is paused. The host resumes when the target resumes.
DisabledThe host was turned off on the Manage tab. DNS is kept.
ErrorThe host could not be set up. Open it for the reason and the DNS records.

Traffic

Networking → Traffic totals requests, cache hits, data served, and server errors for all of your hosts, with the change from the previous period. The charts show the same data over time, and the table at the bottom breaks it down per hostname. Switch between 24 hours, 7 days, and 30 days. Hourly samples are rolled into one row per hour and kept for 120 days.

Automatic endpoints

Every bucket gets an endpoint at <bucket>.s3.anything-cloud.com. It serves public reads when the bucket is public, and signed reads and writes in both cases. A custom host replaces it in the console, but the generated endpoint keeps working. Its visibility is controlled on the bucket's Access tab.

Every worker can have an address under workers.anything-cloud.com. That address is managed with the worker and cannot be deleted from the Hosts page.

Automate hosts

The REST API can list, update, and delete hosts. Use PATCH /api/v1/hosts/{hostname} to change enabled, compression, cache, or access. The access object accepts crawlers, uncommon_user_agents, user_agents, paths, and patterns. Sending an access object replaces the whole rule set, so include every rule you want to keep.