Advertisement
Lyve Pilot to CORTX Interface (optional) requirements
3.
Item
Lyve Pilot
CORTX Manager and S3 Client to CORTX Interface requirements
4.
Item
SSL Certificate
S3 Client and CORTX Interface requirements
5.
Item
Data VIP ("S3 Endpoint")
S3 "Access Key" and "Secret
Key"
SSL Certificate
Requirement
Must have a routable connection to the
Management VIP and Data VIP described
in the networking section above.
Requirement
CORTX Manager Web interface uses
https to encrypt the web browser traffic.
This is achieved by using a certificate
which can be either a CORTX Manager
self signed certificate or a user provided
certificate, which can be user self signed
or certificate authority (CA) signed
Certificate.
Note: S3 client and the CORTX Manager
uses the same SSL Certificate.
Requirement
Must have a routable bi-directional
connection to the S3 client(s) in use that
supports all required ports (see list
above).
S3 Clients require the Access key and
Secret Key to create a signature for S3
Client requests to Lyve Rack R1.
S3 Client Requests across https must be
secured with a certificate.The certificate
can be a CORTX Manager provided self
signed certificate, or a user provided self
signed certificate or a user provided
certificate authority (CA) signed
Certificate.
Note: S3 client and the CORTX Manager
uses the same SSL Certificate.
Comment
Make sure you have the link and the
login credentials for Lyve Pilot.
Comment
If the CORTX Manager self signed
certificate is used, the user is asked to
accept this self signed certicate upon first
connection to CORTX Manager.
Optionally, the user is provided the
ability to upload a user provided self
signed or user provided certificate
authority (CA) signed Certificate using
CORTX Manager.
Comment
"S3 Account" creation can be performed
by the CORTX "admin" user or a CORTX
"user" with the "manage" role assigned.
"Access Key" and "Secret Key" are
created as a set in CORTX Manager when
a "S3 Account" is created. These are
shown one time and there is an
oportunity to download this credential as
a .csv file. The user creator must store
this information securely as this
information is never shown again,
consistent with industry standards.
The S3 Client can then use this credential
when submitting a S3 Request e.g.
creating a bucket associated with this
credential.
If the CORTX Manager self signed
certifcate is not used by the S3 Client, the
S3 Client can use a self signed or a
certificate authority (CA) signed
certificate providing it has been
previously uploaded to CORTX Manager.
By default AWS CLI verifies SSL
cerificates as being signed by a certificate
authority (CA) when communicating.
5
7
Page
of
Check
Check
Check
Seagate PN 1104485-01_rD
Advertisement
