Nodeum Docs
HomepageBlog
  • ✨What is Nodeum?
    • Data Management Software
  • 👣GETTING STARTED
    • Step by Step
  • 🏨ARCHITECTURE
    • Standalone
    • High Availability
    • Fully Scalable & Resilience
  • Install and Deploy Nodeum
    • Platform Support
    • Nodeum v1
      • Ansible based installation
    • Nodeum v2 - Data Mover
      • Ansible based Installation
        • Customize your Installation
      • Docker Based Deployment
    • SLURM Integration
    • Software License Application
  • Interfaces
    • ND Client
    • Console
      • Manual for Administrator
        • Login
        • Dashboard & Reports
        • Catalog
        • Data Mover Management
        • Advanced Task Management
        • Data Container
        • Primary Storage Configuration
        • Pool Management
        • TCO Calculator
        • Toolbox
        • System Settings
          • Information
          • Configuration
          • Date & Time
          • Backup
          • Services
          • Hostname and DNS Configuration
          • NAS Storage Configuration
          • Object Storage Configuration
          • Tape Library Configuration
          • User Management
          • Audits
      • Manual for End User
    • For Developers
      • RESTful API
      • Configuration through RestAPI Console
      • Software Developement Kits (SDK)
      • Nodeum API
        • API Terms of Use
        • release v1.x
        • release v2.x
  • DATA MOVER
    • Policy-Based Task orchestration
      • Pool Management
      • Scheduler
      • Data Integrity
      • Priority Management
      • Filtering (Basic or Advanced)
      • Hook service (callback)
    • Content traceability
    • Metadata Management
  • IDENTITY MANAGEMENT
    • Right - Authentication & Authorization
    • LDAP Plugin for JWT Token
  • Container Configuration
    • Prerequisites
    • About Container
    • Authorization and Authentication
    • Access your Container
  • HYBRID STORAGE MANAGEMENT
    • File System Managment
    • Object Storage Management
      • Customize your S3 connection
    • Tape Library Management
      • Tape Writing Format : LTFS
      • Tape Compression
      • Tape Rehydratation
      • Import a LTFS Tape
      • Task Maintenance for Tapes
  • ⏰Alert & Monitoring
    • Alerts
    • Monitoring
    • Log Management
  • 🏥Recover after Hardware Failure
    • Failover - Active/Passive
    • Failover Procedure - One Site
    • Backup & Restore
  • 🔐Security Guide
    • Advanced Network Configuration
    • Add a SSL Certificate on Web Console
    • Enable SSL Certificate Container accessible on S3 Protocol
  • Compatibility guide
    • Software requirement
    • Supported Storage
  • PRODUCT SPECIFICATIONS
    • Character Set Support
    • Limitations
    • Files Status
    • Task Status
Powered by GitBook
On this page

Was this helpful?

  1. Security Guide

Enable SSL Certificate Container accessible on S3 Protocol

By default, the Containers are accessible on S3 with HTTP protocol. You can add a SSL Certificate to allow data encryption.

There are multiple types of certificates that can be used to enable SSL.

Self-Signed Certificate

Preamble

We consider in this example the following parameters

  • Certificate validity period of key SSL is 365 days

  • Private key file name is "private.key"

  • Certificate file name is "public.crt"

  • Server IP address is "10.x.x.x"

Creation of the self-signed certificate

$ cd /root/.minio/certs/ 
$ sudo openssl11 req -x509 -newkey rsa:4096 -sha256 -days 365 
-nodes -keyout ./private.key -out ./public.crt -subj "/CN=nodeum.domain.local" -
addext "
subjectAltName=DNS:nodeum.domain.local,DNS:localhost,IP:0.0.0.0,IP:127.0.0.1,
IP:10.x.x.x"
Generating a RSA private key
................................................................................++++
................................................................................++++
writing new private key to './private.key'
-----

Once done, it's required to restart the MINIO service :

$ systemctl restart minio

You need to change the following configuration file /root/.mc/config.json and there change the URL of localminio configuration from http to https.

$ vi /root/.mc/config.json
$ vi nodeum.conf 
... 
"localminio": {
              "url": "",
              "accessKey": "6aIo3CBHhKa35stGKAME",
              "secretKey": "lFRHd0MixbrrrMXESMjsqLfGHLl2KmJ419fCrUww",
              "api": "S3v4",
              "path": "auto"
              },
... 

Then you can test the configuration in using the mc admin command :

$ sudo mc admin user info localminio user1 --insecure
AccessKey: user1
Status: enabled
PolicyName:
MemberOf:

Last updated 1 year ago

Was this helpful?

🔐