Default configuration files vary by distribution. You might need to add these sections and options rather than modifying existing sections and options. Also, an ellipsis (...) in the configuration snippets indicates potential default configuration options that you should retain. Obtain the /etc/swift/swift.conf file from the Object Storage source repository: # curl -o /etc/swift/swift.conf \ https://git.openstack.org/cgit/openstack/swift/plain/etc/swift.conf-sample?h=stable/kilo Edit the /etc/swift/swift.conf file and complete the following actions: In the [swift-hash] section, configure the hash path prefix and suffix for your environment. [swift-hash] ... swift_hash_path_suffix = HASH_PATH_PREFIX swift_hash_path_prefix = HASH_PATH_SUFFIX Replace HASH_PATH_PREFIX and HASH_PATH_SUFFIX with unique values. Keep these values secret and do not change or lose them. In the [storage-policy:0] section, configure the default storage policy: [storage-policy:0] ... name = Policy-0 default = yes Copy the swift.conf file to the /etc/swift directory on each storage node and any additional nodes running the proxy service. On all nodes, ensure proper ownership of the configuration directory: # chown -R swift:swift /etc/swift On the controller node and any other nodes running the proxy service, restart the Object Storage proxy service including its dependencies: # service memcached restart # service swift-proxy restart On the controller node and any other nodes running the proxy service, start the Object Storage proxy service including its dependencies and configure them to start when the system boots: # systemctl enable openstack-swift-proxy.service memcached.service # systemctl start openstack-swift-proxy.service memcached.service On the storage nodes, start the Object Storage services: # swift-init all start The storage node runs many Object Storage services and the swift-init command makes them easier to manage. You can ignore errors from services not running on the storage node. On the storage nodes, start the Object Storage services and configure them to start when the system boots: # systemctl enable openstack-swift-account.service openstack-swift-account-auditor.service \ openstack-swift-account-reaper.service openstack-swift-account-replicator.service # systemctl start openstack-swift-account.service openstack-swift-account-auditor.service \ openstack-swift-account-reaper.service openstack-swift-account-replicator.service # systemctl enable openstack-swift-container.service openstack-swift-container-auditor.service \ openstack-swift-container-replicator.service openstack-swift-container-updater.service # systemctl start openstack-swift-container.service openstack-swift-container-auditor.service \ openstack-swift-container-replicator.service openstack-swift-container-updater.service # systemctl enable openstack-swift-object.service openstack-swift-object-auditor.service \ openstack-swift-object-replicator.service openstack-swift-object-updater.service # systemctl start openstack-swift-object.service openstack-swift-object-auditor.service \ openstack-swift-object-replicator.service openstack-swift-object-updater.service