An Amazon EC2 instance was provisioned to host Nexus Repository Manager. Deploying Nexus on a cloud-based virtual machine provides a dedicated environment for artifact storage, repository management, and CI/CD integration.
A secure SSH connection was established to the EC2 instance for remote administration. SSH provides encrypted command-line access, enabling engineers to configure and manage Linux servers securely.
Since Nexus Repository Manager is a Java application, the required Java Runtime Environment (JRE) was installed before deployment. Installing the correct runtime is a prerequisite for running Java-based services reliably.
The installed Java version was verified to confirm that the runtime environment met Nexus system requirements. Validating software installations helps prevent compatibility issues during deployment.
The Nexus installation package was downloaded using wget, allowing the application to be installed directly from the official distribution source. Retrieving software from trusted sources helps maintain deployment integrity.
The downloaded Nexus archive was extracted to make the application files available for configuration and execution. Extracting packaged software is a standard step in preparing server-based applications for deployment.
The Nexus configuration was updated to run under a dedicated nexus system account instead of the root user. Running services with least-privilege permissions improves system security and aligns with Linux administration best practices.