Nexus Repository Manager helps to create a repository for your organization where you store application artifacts and you can use it as a proxy for public repositories. t supports various formats, such as Maven, APT, and Go
In this article, we will see what is Nexus blob store and what are the available types in Nexus Repository Manager.
Nexus Blob is the storage place linked to repository where the repository data are saved. By default, nexus uses the local file system as the blob store. The sonartype-work directory holds the default blobs data.
The configuration for a soft quota can be found in the Blob Stores feature to view, located in the Blob Stores sub-menu of the Administration menu. A soft quota is a feature that monitors a blob store and raises an alert when it exceeds a constraint.
Types of Blob Stores
NFS File system
Nexus supports NFS filesystems mounted to the Nexus server as a blob store. Make sure the NFS filesystem version is v4. Older to v4 is not supported by Nexus
Nexus supports the AWS EFS filesystem as a blob store mounted to Nexus Server. AWS EFS performance is low compared to Normal NFS share. EFS also need to mount using NFS v4
AWS Simple Storage Service ( S3 )
Another filesystem supported by Nexus is S3, S3 can be configured using REST API or Nexus Web UI console can be used to configure S3.
The below screenshot is for reference.
Make sure that you have created an IAM user for accessing the s3 bucket.
below is the required policy which needs to be attached to the IAM user to access the bucket.
For configuring s3, make sure that Type is selected as s3.
Name: blob name
Region: s3 bucket region
Bucket: Bucket name
Bucket prefix: folder inside the bucket to store the data
Enable Authentication with Access and Secret Key
Below is the IAM required IAM Policy
It’s recommended that by Nexus that Glusterfs and Fuse file systems are unreliable.
Happy Learning 🙂
© 2020, Techrunnr. All rights reserved.