> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloudstic.com/llms.txt
> Use this file to discover all available pages before exploring further.

# cloudstic store init

> Initialize a configured store by reference from profiles.yaml

Initialize a named store entry from `profiles.yaml`.

This command resolves the store configuration and encryption credentials, checks
backend access, and initializes the repository when the store is reachable but
not yet initialized.

## Usage

```bash theme={null}
cloudstic store init [options] <name>
```

In interactive mode, if `<name>` is omitted, you'll be prompted to select one.

## Options

<ParamField path="-profiles-file" type="string" env="CLOUDSTIC_PROFILES_FILE">
  Path to the profiles YAML file.
</ParamField>

<ParamField path="-yes" type="boolean" default="false">
  Initialize without confirmation prompt.
</ParamField>

## Examples

```bash theme={null}
# Initialize a named store
cloudstic store init prod-s3

# Initialize non-interactively
cloudstic store init -yes prod-s3

# Use a custom profiles file
cloudstic store init -profiles-file ~/.config/cloudstic/profiles.yaml prod-s3
```

## Common outcomes

* Store already initialized: command confirms access and (for encrypted repos)
  verifies configured unlock credentials.
* Store reachable but not initialized: command initializes repository metadata.
* Missing/invalid credentials: command returns a clear error for secret
  resolution or unlock validation.

## See Also

* [cloudstic store verify](/commands/store-verify): Validate credentials and access without initializing
* [cloudstic store new](/commands/store-new): Create or update a store entry
* [cloudstic store show](/commands/store-show): Show one store configuration