CentOS is a Linux operating-system project whose current general-purpose distribution is CentOS Stream. It installs a complete operating system or supplies a ready-made cloud or container image; it is not a Windows installer that runs alongside ordinary desktop programs. Stream sits in the Red Hat Enterprise Linux development process after Fedora work has matured and before the next RHEL minor release. That position means its packages arrive continuously as the RHEL engineering branch moves, rather than waiting for a finished RHEL release and rebuilding it afterward.
Stream, not legacy
Older references often use the name for CentOS Linux, the downstream rebuild that many servers ran for years. The project now separates those historical releases from Stream. The old CentOS Linux trees in the CentOS Vault receive no maintenance and exist for historical access. Installing one because an old tutorial names it leaves the machine without the normal security-update path expected from a current distribution.
Stream is closer to upcoming RHEL work. Its packages can therefore move before the corresponding RHEL minor release. Administrators who need exact compatibility with a certified RHEL point release should account for that relationship instead of treating Stream as a byte-for-byte substitute. The model is useful for testing the package set that RHEL engineers are preparing and for contributing fixes before those changes enter RHEL.
Pick the artifact
The CentOS download area separates installation ISOs, RPM repositories, generic cloud images, container archives, and Vagrant boxes. An ISO boots an installer and can repartition a physical or virtual disk. A cloud image already has a disk layout intended for a cloud platform. A container image contains a userspace base and does not boot its own kernel. Choosing the wrong artifact changes the entire deployment path, even when all of them carry the project name.
Architecture matters as well. The project publishes artifacts for x86-64, ARM64, IBM Power, and IBM Z where the branch supports them. An image built for another processor will not turn into a compatible installer after it reaches the USB stick. The project also publishes checksums and asks users to verify an ISO before booting it. A successful download size alone cannot reveal every corrupted byte.
Installation changes disks
Writing a CentOS ISO to removable media replaces the selected device’s previous layout. The project’s download guidance points users to its USB instructions specifically to avoid damage. The same care applies inside the installer: automatic storage can create a workable layout, while manual partitioning can preserve or erase existing systems depending on the selected disks and mount points. A snapshot or file backup made before partition changes is the practical recovery path.
After installation, the system uses RPM packages and DNF-managed repositories. Installing an extra repository changes which signed packages and updates the machine can receive. Special Interest Group repositories have their own release packages and signing material, so administrators should add the intended repository rather than copying a package command from another branch.
Cloud identity
Official cloud images avoid the ISO installer and start from a prepared virtual disk. The image still needs the correct region, processor architecture, network rules, and login identity. Current AWS images use a different default cloud username from older CentOS Linux images. Reusing an old automation script with the historical username can look like an SSH or firewall failure even when the instance has booted normally.
