Quick Start¶
Get Arca running and perform your first S3 operations.
Start the Server¶
No build needed. With the repository checked out:
Or with plain Docker, without even cloning the repository:
docker run -d --name arca -p 9000:9000 -v arca-data:/data \
ghcr.io/dxc-technology/arca:latest
docker logs arca | grep "Access Key"
The image is public and multi-arch. See Installation for the available tags.
Arca serves your certificate and key if you put their PEM files in certs/
at the repository root. Otherwise it creates a local CA and a certificate
for localhost on the first start, and keeps them valid. See the
TLS guide for how to trust the local CA.
Tip
Drop the -d flag to run in the foreground and see logs in real time. Press Ctrl+C to stop the server.
On first startup, Arca auto-generates a root credential and prints it to the logs:
========================================
Root credential created automatically
========================================
Access Key: GHUZM9QTHSJKE3N6P50O
Secret Key: aNdrqpNvsbI9BeU/O+3AA508Xtey4Sp3EILSXRQy
========================================
WARNING: This will only be shown once.
Store these credentials securely.
========================================
Configure your S3 client:
Your First Bucket¶
Upload and Download Objects¶
Start the Web Console¶
Arca includes a browser-based web console for managing buckets, objects, and credentials:
Open http://localhost:9080, enter the Arca endpoint (http://localhost:9000) and your credentials.
No build needed. With the repository checked out:
Or with plain Docker, without even cloning the repository:
docker run -d --name arca-console -p 9080:8080 \
-e ARCA_ENDPOINT=http://localhost:9000 \
ghcr.io/dxc-technology/arca-console:latest
The image is public and multi-arch. The container listens on port 8080 (mapped to 9080 here) and runs as the unprivileged user 10001:10001. ARCA_ENDPOINT is the Arca URL the browser connects to. See Installation for the available tags.
Tip
As with bin/arca, drop the -d flag to see console container logs in real time. Stop it with bin/console stop (docker stop arca-console for the plain Docker run).
Admin credentials unlock additional features like credential management and server stats.
See the Web Console guide for details.
Development Scripts¶
Convenience scripts in bin/ wrap docker compose commands:
| Script | Description |
|---|---|
bin/build |
Build the Docker image |
bin/arca |
Manage the Arca server (start, stop, status, logs). Use --tls for HTTPS, -c <path> for a custom config. |
bin/console |
Manage the web console (start, stop, status, logs). Inherits TLS and the other features from the running Arca. |
bin/test |
Run unit + integration tests (unit, integration, or both) |
bin/screenshots |
Take automated console screenshots for documentation |
bin/s3-tests |
Run Ceph s3-tests compatibility suite |
bin/perf-test |
Run performance tests (suite benchmarks Arca against MinIO, see Performance Testing) |
bin/docs-build |
Build the documentation site |
bin/docs-serve |
Serve docs locally with live reload |
bin/docs-publish |
Build, commit, and push docs to update GitHub Pages |
Next Steps¶
- Configuration — customize server settings and manage credentials
- S3 API Reference — full details on supported operations
- Web Console — browser-based bucket and credential management