Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.aspect.build/llms.txt

Use this file to discover all available pages before exploring further.

A remote cache is a type of smart, centralized storage that saves the results of your software builds, making future builds significantly faster. It acts as an extended definition of your build system’s mechanism, helping explain how it fits into a broader framework. The cache’s core purpose is to avoid redundant work. When a build tool (like Bazel) compiles your code, it saves the final, successful output in the remote cache. If you or a teammate build the same code again, the tool skips the process and quickly retrieves the saved result from the cache. This mechanism allows teams to align and collaborate more easily, as everyone shares a central source for pre-built components, drastically saving time and compute resources.

​
Setup of the remote cache

The setup involves networking steps because the cache lives inside a highly protected, isolated private network called a Virtual Private Cloud. This is for security. To allow your external build tools that are outside this protected Virtual Private Cloud to reach the cache safely and securely, you need to establish three levels of access:
  1. Physical Connection with Virtual Private Cloud Peering: This creates a secure, private tunnel between your company’s existing network and the cache’s protected network. Think of it as laying a direct, dedicated wire between two office buildings.
  2. Entry Permission with Security Group: This acts like a bouncer at the door. You must explicitly open a specific channel through TCP Port 8980 to allow the build traffic in.
  3. Identity with Certificate: You must present a security certificate to the cache. This proves that your tool is trustworthy and ensures that only authorized clients can access the stored data.