Planning for unified file and object access

Unified file and object access allows use cases where you can access data using object as well as file interfaces. Before using unified file and object access, you need to plan for a number of aspects.

Planning for identity management modes for unified file and object access
As you plan for unified file and object access, it is important to understand the identity management modes for unified file and object access.
Authentication planning for unified file and object access
Planning for a suitable authentication mechanism for a unified file and object access setup requires an understanding of the Identity management modes for unified file and object access and the authentication setups supported with these modes.
ibmobjectizer service schedule planning
The unified file and object access feature allows accessing data ingested through file to be accessed from object. This access is enabled by a process called objectization. Objectization is done by the ibmobjectizer service that runs periodically and converts the file data located under unified file and object access enabled filesets to make it available for object access.
Prerequisites for unified file and object access
To enable unified file and object access, you must enable the file-access object capability.

Parent topic: Planning for object storage deployment

Related concepts:

Load balancing

Cluster host name

Authentication method

Backup and disaster recovery strategy

SELinux considerations

Eventual consistency model

Planning for multi-region object deployment