diff --git a/portal-ui/src/screens/Console/Configurations/SiteReplication/SiteReplication.tsx b/portal-ui/src/screens/Console/Configurations/SiteReplication/SiteReplication.tsx
index b108bed2d..99bc5d9d9 100644
--- a/portal-ui/src/screens/Console/Configurations/SiteReplication/SiteReplication.tsx
+++ b/portal-ui/src/screens/Console/Configurations/SiteReplication/SiteReplication.tsx
@@ -17,7 +17,7 @@
import React, { Fragment, useEffect, useState } from "react";
import PageHeader from "../../Common/PageHeader/PageHeader";
import PageLayout from "../../Common/Layout/PageLayout";
-import { Box, DialogContentText } from "@mui/material";
+import { Box, DialogContentText, Grid } from "@mui/material";
import useApi from "../../Common/Hooks/useApi";
import ReplicationSites from "./ReplicationSites";
import TrashIcon from "../../../../icons/TrashIcon";
@@ -39,6 +39,7 @@ import {
setErrorSnackMessage,
setSnackBarMessage,
} from "../../../../systemSlice";
+import AButton from "../../Common/AButton/AButton";
export type ReplicationSite = {
deploymentID: string;
@@ -174,19 +175,46 @@ const SiteReplication = () => {
) : null}
{!hasSites && !isSiteInfoLoading ? (
-
- Site Replication is not configured.
-
- ) : null}
+
+
+ }
+ help={
+
+ This feature allows multiple independent MinIO sites (or clusters) that are using the same external
+ IDentity Provider (IDP) to be configured as replicas.
+
+
+ To get started,{" "}
+ {history.push(IAM_PAGES.SITE_REPLICATION_ADD);}}>
+ Add a Replication Site
+ .
+
+ You can learn more at our{" "}
+
+ documentation
+
+ .
+
+ }
+ />
+
+
+
+ ) : null}
+ {hasSites && !isSiteInfoLoading ? (
}
@@ -196,30 +224,21 @@ const SiteReplication = () => {
that are using the same external IDentity Provider (IDP) to be
configured as replicas. In this situation the set of replica sites
are referred to as peer sites or just sites.
-
-
-
- -
- Initially, only one of the sites added for replication may
- have data. After site-replication is successfully
- configured, this data is replicated to the other (initially
- empty) sites. Subsequently, objects may be written to any of
- the sites, and they will be replicated to all other sites.
-
- -
- All sites must have the same deployment credentials (i.e.
- MINIO_ROOT_USER, MINIO_ROOT_PASSWORD).
-
- -
- All sites must be using the same external IDP(s) if any.
-
- -
- For SSE-S3 or SSE-KMS encryption via KMS, all sites must
- have access to a central KMS deployment. server.
-
-
-
-
+
+ Initially, only one of the sites added for replication may
+ have data. After site-replication is successfully
+ configured, this data is replicated to the other (initially
+ empty) sites. Subsequently, objects may be written to any of
+ the sites, and they will be replicated to all other sites.
+
+ All sites must have the same deployment credentials (i.e.
+ MINIO_ROOT_USER, MINIO_ROOT_PASSWORD).
+
+ All sites must be using the same external IDP(s) if any.
+
+ For SSE-S3 or SSE-KMS encryption via KMS, all sites must
+ have access to a central KMS deployment server.
+
You can learn more at our{" "}
{
}
/>
+ ) : null}
{deleteAll ? (