# Log archive in Vespa Cloud Enclave

[](/en/operations/enclave/archive.html.md "View as Markdown") 

 **Warning:** The structure of log archive buckets may change without notice

After Vespa Cloud Enclave is established in your cloud provider account using Terraform, the module will have created a storage bucket per Vespa Cloud zone you configured in your enclave. These storage buckets are used to archive logs from the machines that run Vespa inside your account.

Since the buckets are in your own cloud account, you do not need to register an IAM role or configure access through the Vespa Cloud Console — you can access the archive buckets directly using your existing cloud credentials.

![Enclave archive view](/assets/img/archive-aws-enclave.png)

There will be one storage bucket per Vespa Cloud Zone that is configured in the enclave. The name of the bucket will depend on the cloud provider you are setting up the enclave in.

Files are synchronized to the archive bucket when the file is rotated by the logging system, or when a virtual machine is deprovisioned from the application. The consequence of this is that frequency of uploads will depend on the activity of the Vespa application.

## Directory structure

The directory structure in the bucket is as follows:

```
<tenant>/<application>/<instance>/<host>/logs/<logtype>/<logfile>
```

- `tenant` is the tenant ID.
- `application` is the application ID that generated the log.
- `instance` is the instance ID of the generated log, e.g. `default`.
- `host` is the name prefix of the host that generated the log, e.g. `e103a`.
- `logtype` is the type of log in the directory (see below).
- `logfile` is the specific file of the log.

## Log types

There are three log types that are synced to this bucket.

- `vespa`: [Vespa logs](../../reference/operations/log-files.html)
- `access`: [Access logs](../access-logging.html)
- `connection`: [Connection logs](../access-logging.html#connection-log)

 Copyright © 2026 - [Cookie Preferences](#)