S3 Topology - Realms, Zonegroups and Zones
The Topology tab exposes Ceph RGW topology concepts in the eEKAS GUI.
Screenshot reference: S3 topology (../eekas-s3-screenshots/13-s3-topology.png)
Topology Fields
The captured test system shows:
- Realm:
realm_eu-central-2 - Zonegroup:
zonegroup_eu-central-2 - Zone:
zone_eu-central-2
The tab provides controls for:
- Applying default realm/zonegroup/zone.
- Committing the period after applying defaults.
- Refreshing topology.
- Refreshing sync status.
- Committing the current period.
What These Terms Mean
| Term | Practical meaning |
|---|---|
| Realm | The top-level RGW namespace for a multi-site S3 deployment. |
| Zonegroup | A grouping of one or more zones, often representing a region or service domain. |
| Zone | A concrete storage/service location that handles S3 data and metadata. |
| Period | The committed topology configuration state used by RGW. |
Why Topology Awareness Matters
S3 deployments become risky when administrators do not know which site or service domain they are changing. eEKAS reduces this risk by showing the active realm, zonegroup and zone directly in the S3 Service Console.
This is especially important for:
- Multi-site deployments.
- Service-provider environments.
- Separating internal and customer-facing domains.
- Planned failover and maintenance workflows.
Sync Status
The sync status area reports the current realm, zonegroup, zone and metadata sync state. On the captured test system, the zone is the master and metadata sync is not required from another master.
Review sync status after topology changes, site changes or failover testing.
Operational Recommendations
- Avoid topology changes during active customer maintenance windows.
- Commit period changes deliberately.
- Capture the current period info before changing defaults.
- Verify endpoints and client access after changing topology.
Source: eEKAS live test cluster and supplied euroNAS eEKAS documents, prepared on 2026-07-09.