Automation has improved proactive monitoring and currently supports efficient cloud operations
What is our primary use case?
In my day-to-day work, the main use cases for Amazon Linux involve a wide variety of tasks with a common theme of optimization for Amazon Cloud. Since recently updating my project, I have been using it for automation to monitor CPU utilizations and hosting backend services including REST APIs and web applications on EC2 instances, running production microservices that integrate with services including Amazon ECS and AWS Lambda, and as the defaulting operating system for EC2 instances in a SaaS platform. Additionally, I use Amazon Linux as base images for Dockerfile, node groups for Amazon EKS Kubernetes clusters, and powering CI/CD pipelines acting as Jenkins agents or building servers, using it with infrastructure as code to spin up consistent environments for development, staging, and production.
The most valuable use case involving my work is the scripting that runs automatically via cron, which is a time-based scheduler on Amazon Linux EC2 instances. The script accomplishes mainly two groups: resource dashboarding and proactive monitoring. In resource dashboarding, I utilize the command line interface, specifically AWS CLI, to list all running resources including EC2 instances, S3 buckets, Lambda functions, and configurations to implement in the daily dashboard sent to management. Additionally, I check logs and help prevent unexpected storage issues, and these are the activities I have been using in my daily work.
In my organization, Amazon Linux is deployed using a multi-cloud hybrid approach, supporting all four environments we have mentioned. Public cloud is the most common deployment, where I use Amazon Linux directly on Amazon EC2 to scale from small web servers to massive machine learning clusters. I also deploy it on private premises for added security.
I primarily use AWS for my Amazon Linux deployments.
What is most valuable?
In my experience, the best features Amazon Linux offers are the resource dashboarding and proactive monitoring systems that I have been utilizing in day-to-day work. Most cases are centered around using a Linux base image for containerizing applications, particularly in production on ECS or by deploying on ECS, and I am deploying my servers in EKS. Currently, I also manage automation scripting and container-based images to find EC2 instances and what servers are running in the background as part of my day-to-day activities using Amazon Linux.
Since using Amazon Linux, I have noticed a positive impact on my organization as it has become an industry standard for AWS native development. The benefits include much better resource isolation and more accurate monitoring for memory, CPU, and input-output. It makes running Docker or Kubernetes yield more predictable container performance with fewer out-of-memory kills that are hard to diagnose. Using Amazon Linux smooths the application running on Docker and Kubernetes, making it very efficient for deploying applications on cloud platforms including Amazon, Azure, and GCP.
What needs improvement?
I see definite areas where Amazon Linux could improve because it is not a one-size-fits-all solution. The single biggest pain point for long-time users is the lack of direct in-place upgrades from Amazon Linux to AL2, as moving to a new version requires launching new instances and manually migrating applications instead of simply running a command similar to some DNF system update. A migration tool that could handle the heavy lifting and configurations would save thousands of engineering hours. I have noticed that since 2023 does not support EPEL directly, AWS has introduced supplementary packages for Amazon Linux, which has been an adjustment.
I chose eight out of ten because, while there are many positives, some issues arise at the end of the line for Amazon Linux. I have faced some challenges when deploying clusters in AWS, particularly with some recent updates that have changed since version twenty-three, leading me to believe there is room for improvement.
What do I think about the stability of the solution?
Amazon Linux is stable and more flexible, allowing easy scalability at no cost. It is designed by the same engineers who created the underlying hardware, EC2, as well as the orchestration services, ECS and EKS, effectively removing many traditional bottlenecks associated with scaling large fleets.
In terms of container scalability, I find it to have deterministic reliability, no broken scale-outs, and it boosts speed and safety in container orchestrations with dynamic scaling. It provides resource control and consistency, contributing to Amazon Linux's reputation for stability.
How are customer service and support?
The customer support for Amazon Linux is good, as they quickly guide me through issues whenever I contact them, resolving problems within a short time.
Which solution did I use previously and why did I switch?
Before switching to Amazon Linux two thousand twenty-three, I typically used Amazon Linux two, Ubuntu, CentOS, and Red Hat. The end of life for those older distributions was a primary reason for switching, as security updates for Amazon Linux are ending in June two thousand twenty-six. Amazon Linux two thousand twenty-three provides modern features such as cgroup v2 and systemd-timers that older versions lack, and while Ubuntu is good for development, it is not tuned for AWS hardware out of the box. Amazon Linux two thousand twenty-three offers better performance under Graviton chips and significantly faster operations.
How was the initial setup?
My experience with pricing, setup costs, and licensing for Amazon Linux is very straightforward and completely free. I simply select it from the quick start tab when launching an EC2 instance with no additional cost or complex licensing terms to manage. The operating system is free, and I only pay for infrastructure, such as approximately zero cost for a T3 small instance, where the EC2 instances charge about zero point zero two one per hour.
What was our ROI?
I see that return on investment is usually measured in efficiency gains rather than in a simple monetary form. Since the operating system itself is free and by using Amazon Linux two thousand twenty-three, many organizations have been qualifying this transaction through a mix of cloud-based operations.
Since switching to Amazon Linux, I have seen improvements clearly shown in infrastructure metrics. Some wins commonly seen after switching, particularly when moving from general-purpose distributions such as Ubuntu, include approximately twenty to forty percent better price-performance ratio. The outcomes combine massive savings of over one million in under a year by migrating workloads to Graviton-based instances running Amazon Linux, as AL two thousand twenty-three is optimized for ARM at the compiler level, allowing applications to run more effectively and function on smaller instances. I have also noted faster deployments, including a forty to sixty percent reduction in AMI size, significantly faster boot times, and a boost in faster auto-scaling to reduce cold start latencies, with zero downtime regarding patching for critical vulnerabilities.
Which other solutions did I evaluate?
I evaluated several options, including Ubuntu and CentOS. As previously mentioned, Ubuntu is great for development but not optimized for AWS, and CentOS's move to a streamed model is less stable for production. Many organizations moved to Amazon Linux for a more flexible long-term support cycle.
What other advice do I have?
The biggest advantage I find in using Amazon Linux is the ability to determine updates throughout the version repositories. In older versions, I ran a yum update, but now I can pin different packages based on commands I run. This advantage allows me to test updates in a staging environment and be one hundred percent certain that the exact same packages will be applied in production, eliminating issues where something worked on one machine or worked yesterday. It is also beneficial as it boosts faster boot times, supports Amazon Graviton ARM processors, and optimizes the operating system for those processors. Moreover, it efficiently uses fewer resources including CPU and RAM, allowing my applications to run on smaller, cheaper instance types with secure by default configurations.
I recommend Amazon Linux for its free use, stable performance, faster control, and scalability, making it suitable for everyone.
To clarify, I did not purchase Amazon Linux through the AWS Marketplace because it is directly provided by AWS at no additional cost, so a purchase or subscription is not required. Unlike many other enterprise Linux distributions, such as Red Hat Enterprise Linux that require a paid subscription, Amazon Linux is offered by AWS as a free operating system for use on EC2 instances. There is no need to visit the marketplace to buy it.
Overall, I would rate Amazon Linux at an eight out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Cloud platform has transformed security and cut operating costs for high-traffic workloads
What is our primary use case?
My main use case for
Amazon Linux is cloud-optimized application hosting. I use it as a standard OS for
Amazon EC2 instances to run web servers, container hosts, and microservices. Because it is tuned for
AWS infrastructure, it is provided at low latency and best performance. During peak traffic, our system automatically launches new
EC2 instances running
Amazon Linux. These instances come pre-baked with
AWS CLI and security tools, which allows them to integrate with our
S3 buckets and
RDS database immediately.
What is most valuable?
The best features Amazon Linux offers include remote sharing features such as AWS Systems Manager Session Manager. This allows our remote DevOps team to share secure terminal access to an instance via the browser, which eliminates the need for us to manage SSH keys or open port 22. This makes it much easier and safer for remote collaboration and troubleshooting.
Amazon Linux has significantly improved our security and deployment speed. By using an OS that is secure by default and pre-integrated with AWS tools, our team spends less time on basic configuration and more time on high-value application development. Around 75% of our time has been reduced since the basic hardening concepts are reduced. We do not need to apply all the hardenings to the new VMs that we are creating. By default, the image provided by Amazon has hardening applied, so our 75% of time has been reduced and has been allocated to application development purposes.
What needs improvement?
Amazon Linux could be improved by providing more third-party software packages. They could expand the repositories for many cutting-edge development tools that are not included in the core release yet. I feel Amazon Linux offers the best balance of modern features and security. Making sure about the kernel live patching is a great game changer that it is already offering. So there is still room for improvement.
For how long have I used the solution?
I have been using Amazon Linux for about three years as our primary operating system for hosting production workloads and cloud-native applications on AWS.
What do I think about the stability of the solution?
Amazon Linux is extremely stable. AWS provides long-term support for versions such as Amazon Linux 2, and the newer Amazon Linux 2023 is designed with a predictable release cycle. Since it is purpose-built for the cloud, it lacks the bloat of traditional desktop-focused distributions, which leads to fewer crashes and higher uptime.
What do I think about the scalability of the solution?
Amazon Linux is built for hyperscale because it is highly optimized for the AWS Nitro System and lightweight in nature. We can launch hundreds of instances in an auto-scaling group. It scales effortlessly from the smallest nano instance to high-performance computing clusters.
How are customer service and support?
The customer support for Amazon Linux is providing great help. All the requirements that we give to them are met immediately with their assistance, and they are doing a great job.
Which solution did I use previously and why did I switch?
We previously used CentOS. We switched to Amazon Linux because we wanted an OS with a more predictable lifecycle and tighter integration with AWS support. Moving to a distribution that is officially maintained by Amazon gave us better peace of mind regarding long-term security patches and performance tuning.
How was the initial setup?
The experience with Amazon Linux pricing, setup cost, and licensing was seamless. The standard Amazon Linux image is provided for free by AWS. We have used the AWS Marketplace to deploy the CIS hardened versions of Amazon Linux. The licensing is straightforward and billing is consolidated directly into our AWS account, which makes the procurement very easy.
What about the implementation team?
I purchased Amazon Linux through the AWS Marketplace.
What was our ROI?
The ROI with Amazon Linux is high because there are zero licensing fees. By switching the compute fleet from a paid distribution to Amazon Linux, we have reduced our OS-related overhead cost by 100%. Additionally, optimized performance has allowed us to run the same workloads on slightly smaller instance types, saving us roughly 10% on monthly compute spend.
Which other solutions did I evaluate?
Before choosing Amazon Linux, CentOS was the major solution we considered, but we finally ended up choosing Amazon Linux.
What other advice do I have?
My advice for others looking into using Amazon Linux is to embrace Amazon Linux 2023 for all new projects. It offers the best balance of modern features and security. The live kernel patching is a great feature that Amazon Linux offers for people who are going to use the system securely without having a scheduled maintenance window for reboots.
Amazon Linux is truly a performance-first choice for anyone operating in the cloud. It turns the operating system from a management burden into a strategic advantage, providing a high-security environment without the premium price tag of other enterprise Linux distributions. I would rate this product a 9 out of 10.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Efficient cloud workflows have improved how we deploy microservices and manage user data
What is our primary use case?
Amazon Linux is used for hosting back-end applications created in Node.js, databases, and DevOps purposes. Microservices, such as Docker services, are deployed on Amazon Linux.
Amazon Linux is used with EC2, the AWS EC2 service, which is the primary service for deploying back-end services. A microservice architecture is implemented using EC2 instances for deploying particular services in Amazon.
Amazon Linux is also used for RDBMS and SQL databases deployed in Amazon for database purposes.
Amazon S3 bucket is used for storing resumes of candidates because the application is a hiring platform, requiring resume file storage for retrieval and pre-signed URL generation. Whenever resumes need to be stored, an S3 bucket is used. CloudWatch is used to monitor the changes occurring during application deployment in EC2 instances.
What is most valuable?
Amazon Linux offers multiple services such as EC2, S3 bucket, EKS, and CloudWatch, which are valuable for application requirements.
A specific example of how Amazon Linux has positively impacted the organization involves storing images and resumes with quick and faster retrieval. Although other options were checked, S3 was the quickest option because it provided 99.9% availability and very reliable performance. Resumes are stored in an S3 bucket in the respective file, and pre-signed URLs are fetched and stored in the SQL database tables. Whenever a resume is needed, the S3 URL is used directly to fetch the resume.
Amazon Linux and S3 services, including live trail functionality, provide better visibility of changes being deployed to particular services. When a service is deployed, the ability to check if it is failing and at what point it is failing is crucial. After deployment, live trails can be checked and logs put in the code can be viewed in the live trail. The EC2 instance is very effective because it can be scaled according to application needs. With currently over 10,000 users, scalability becomes important if growth reaches over 1 lakh users. Amazon Linux provides very good scalability.
What needs improvement?
Amazon Linux could be improved in the user interface part, as it is quite complicated for new users. Compared to Ubuntu or CentOS, Amazon Linux has a smaller community, resulting in fewer available tutorials. Additionally, there is less flexibility outside of AWS services. Amazon Linux is best optimized for AWS but is not ideal for local development or multi-cloud environments.
For how long have I used the solution?
Amazon Linux has been used for two years throughout my career.
What do I think about the stability of the solution?
Amazon Linux is quite stable and very reliable for the type of application in use.
What do I think about the scalability of the solution?
Amazon Linux is very scalable. The organization has grown from 10,000 users to 1 lakh users, and the service provided is very reliable and highly scalable.
How are customer service and support?
Customer support is great, though it has not been needed because the service is working quite well and has not required customer support assistance.
Which solution did I use previously and why did I switch?
Previously, Linux on Amazon or Ubuntu was used, but Ubuntu was not very beginner-friendly and the setup was more difficult. Amazon Linux was chosen due to its advantages over Ubuntu.
How was the initial setup?
Deployment is faster and visibility is achieved very quickly, making it more reliable overall.
Amazon Linux setup is somewhat challenging initially, but once familiarity with the system is gained, it works very well for applications. For full-stack web-based applications or mobile applications, Amazon Linux provides very good support for back-end and front-end deployments and the entire CI/CD process. The service can be utilized directly without extensive preliminary work.
What about the implementation team?
Amazon Linux is deployed independently; since it runs on AWS infrastructure, separate deployment is not necessary as it is publicly available.
What's my experience with pricing, setup cost, and licensing?
Pricing is very good. The setup could be more beginner-friendly, and regarding licensing, there is limited knowledge, but it is free to use. Payment is only required for the EC2 instance and for data transfer or storage. Setup on AWS EC2 is very quick, typically within minutes, making it cost-effective and easy to deploy.
Which other solutions did I evaluate?
No other options have been searched for or considered except for Amazon Linux.
What other advice do I have?
Amazon Linux and S3 services, including live trail functionality, provide better visibility of changes being deployed to particular services. When a service is deployed, the ability to check if it is failing and at what point it is failing is important. After deployment, live trails can be checked and logs put in the code can be viewed in the live trail. The EC2 instance is very effective because it can be scaled according to application needs. With currently over 10,000 users, scalability becomes significant if growth reaches over 1 lakh users. Amazon Linux is highly scalable and very reliable, making it an excellent choice overall. This review has been rated 9 out of 10.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Cloud-native workloads have become secure, automated, and efficient for continuous delivery
What is our primary use case?
My primary use case was Amazon Linux as the default operating system for EC2 instances supporting Docker-based container deployments, CI/CD pipelines using Jenkins, Kubernetes worker nodes, back-end application servers, and monitoring and logging agents. I used Amazon Linux as an operating system in the service known as Amazon EC2 in Amazon Web Services. Our workflow typically involved provisioning EC2 instances with Amazon Linux, configuring IAM roles, installing Docker and runtime dependencies, setting up services, and deploying applications via automated CI/CD pipelines. Amazon Linux acted as the core layer in our cloud architecture. After provisioning EC2 instances, we used yum as the package manager to install and manage system dependencies. Security updates were applied automatically through AWS managed repositories, ensuring compliance and organizational security standards. Amazon Linux was used for both learning projects and production-like client deployments. Client identities cannot be disclosed, but its predictable update cycle and stability made it suitable for long-running services.
We used Amazon Linux for Docker daemon and container runtimes, for Jenkins agents and build servers, for NGINX and many back-end services, for CloudWatch agents for metrics, and for log collection. During my internship at Cognizant, I extensively worked with Amazon Linux as the primary operating system for workloads deployed on AWS. Amazon Linux served as the base OS for EC2 instances, running Docker containers, CI/CD tools, monitoring agents, and back-end services. Amazon Linux is a purpose-built Linux distribution maintained by AWS, optimized for AWS infrastructure, and designed to deliver long-term stability and enhanced security. The tight integration with native AWS services provides a production-ready environment with minimal overhead, making it suitable for enterprise-grade cloud deployments. It significantly reduces operational complexity in AWS environments. A solid understanding of Linux system administration and AWS fundamentals is required for efficient usage.
I strongly recommend learning Linux system administration fundamentals and AWS core services such as EC2, IAM, VPC, and CloudWatch for setting up the instance and giving basic permissions for users to use it, and security and network basics. When combined with Docker, CI/CD pipelines, and AWS infrastructure, Amazon Linux becomes a powerful and reliable operating system for cloud-native applications.
What is most valuable?
The best features Amazon Linux offers is that it has many packages installed as an operating system. I can directly use tools such as Docker runtime, Jenkins, and any DevOps features such as Ansible and many other tools. I can directly access it in the Linux environment using Amazon Linux. What stood out to me and made my experience better were the security updates. I continue to receive security updates so that bugs cannot come through the system.
Technical benefits include the AWS-optimized kernel, which is tuned for better EC2 performance, native IAM integration for secure access without static credentials, and CloudWatch compatibility for system-level monitoring. It has a security-first design, including SE Linux support and rapid patching. Amazon Linux reduces operational risk by minimizing incompatibilities between the OS and AWS infrastructure.
Amazon Linux is highly stable. In my experience, EC2 instances run continuously for long periods without unexpected OS failures. Combined with AWS managed infrastructure, it provides enterprise-grade reliability suitable for production workloads. Amazon Linux scales efficiently with AWS. It supports horizontal scaling using EC2 Auto Scaling groups and vertical scaling by resizing instance types. It performs consistently under high CPU, memory, and input-output workloads. It is well-suited for microservices and container platforms and for high-traffic back-end systems.
What needs improvement?
From a technical perspective, Amazon Linux could improve in broader availability of third-party packages, simplified system-level troubleshooting tools, and more beginner-focused system administration documentation. New users often need time to understand the permissions of Linux, networking, system services, and AWS security models together.
Amazon Linux has some limitations, such as a smaller package ecosystem compared to Ubuntu. It requires deep Linux knowledge for troubleshooting. The AWS-centric design makes it less portable outside AWS.
For how long have I used the solution?
I am not currently using Amazon Linux, but I used it during my entire internship with Cognizant, probably for five to six months.
What do I think about the stability of the solution?
Amazon Linux is highly stable. In my experience, EC2 instances run continuously for long periods without unexpected OS failures. Combined with AWS managed infrastructure, it provides enterprise-grade reliability suitable for production workloads.
What do I think about the scalability of the solution?
Amazon Linux scales efficiently with AWS. It supports horizontal scaling using EC2 Auto Scaling groups and vertical scaling by resizing instance types. It performs consistently under high CPU, memory, and input-output workloads.
How are customer service and support?
Regarding community support and customer services, AWS provides extensive documentation and security advisors for Amazon Linux. Most issues can be resolved using official AWS documentation, AWS knowledge bases, community forums, and internal support teams.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
Previously, I used general-purpose Linux distributions such as Ubuntu. I switched to Amazon Linux because it is fully optimized for AWS infrastructure. It integrates more naturally with AWS services, and it provides long-term support without license costs.
How was the initial setup?
The initial setup is moderately complex. Launching an EC2 instance with Amazon Linux is straightforward, but configuring IAM roles, network security such as setting up VPC and security groups, and user permissions and services requires some foundational Linux and AWS knowledge. Once configured, daily operations are efficient and low-maintenance.
What was our ROI?
Amazon Linux delivers a positive return on investment by eliminating OS licensing costs, reducing maintenance overhead, improving operational stability, and accelerating DevOps and deployment workflows. While specialized knowledge is required, the long-term cost and reliability benefits outweigh the learning curve.
What's my experience with pricing, setup cost, and licensing?
Amazon Linux is provided at no additional charge by AWS. This means I will not pay anything extra for the OS itself. AWS distributes and maintains Linux images free of licensing fees. Although Amazon Linux itself is free, I still incur AWS usage charges for the services I host on it.
If I am a new AWS customer, the AWS Free Tier typically includes, for the first six months, micro instances such as t2.micro or t3.micro for free, so I can use that.
What other advice do I have?
Amazon Linux is an operating system, and I can install any of the other tools such as DevOps tools and other back-end services, back-end servers, and also AWS tools. I primarily used it in an EC2 instance, and an EC2 instance can be combined with any AWS tool, per my knowledge.
Amazon Linux is open to all AWS services. I can integrate any AWS service using Amazon Linux.
It is a cloud service that I use. The updates will be done by Amazon. I do not need to do anything. Amazon and AWS will handle the updates of Amazon Linux.
I rated this product nine out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Secure, optimized environment has supported cost savings and reliable monolithic deployments
What is our primary use case?
I normally use Amazon Linux for monolithic applications or websites as a web server. Amazon Linux helps me run those monolithic applications or web servers by allowing us to install NGINX or HTTPd using the package managers, RPM. Amazon Linux provides a secure, stable, and high-performance environment that is optimized for the AWS ecosystem itself. It features deep AWS services integration, long-term support, and performance tuning for EC2, making it a reliable choice for monolithic applications.
I normally use Amazon Linux for containerized applications as well, such as EKS. As node groups in EKS, we use Amazon Linux AMIs. Since it is reliable, secure, and gives long-term support from Amazon AWS itself, it serves our needs well.
What is most valuable?
Considering the best features Amazon Linux offers, I would say the security and reliability stand out. The operating system has been optimized by AWS itself, so it is highly optimized. There are various pre-installed AWS tools inside it. It is Graviton optimized for Arm-based workloads and has security by default with enhanced security, lifecycle, and deterministic updates. Upgrades are also good in this offering. It is cost-effective and works well with the modern toolchain.
Regarding those features, Amazon Linux benefits my day-to-day work by enhancing creativity and content generation with visuals in slides, video productions, and it is quite time-saving.
Regarding how Amazon Linux has impacted my organization positively, it helped us mostly with the costing part. Beyond that, the security posture has improved, which is always a big challenge in larger organizations.
Using Amazon Linux gives us a pay-as-you-go model, paying for fewer resources instead of a large upfront investment in hardware servers. I have seen various case studies which have helped save a lot of costs. Regarding security, I have seen very few incidents related to Amazon Linux. There are various kernel issues which we face in other operating systems, but not in Amazon Linux.
What needs improvement?
While VM images exist in other virtualization platforms, Amazon Linux is primarily designed for EC2 itself. Expanding official support for on-premise and hybrid scenarios would improve the flexibility for companies with multi-cloud setups. Additionally, expanded package repositories for third-party software would be beneficial. Compared to Ubuntu or Red Hat, Amazon Linux has smaller communities and fewer third-party repositories. Documentation examples could be improved by providing more real-world, varied use case examples rather than just command references.
Amazon Linux should be easily upgradable. From Amazon Linux 2 to Amazon Linux 2023 requires a complete migration, as there is no direct in-place upgrade path. Having an easier upgrade path for migrating from one version to another would be really helpful. Standardized Yum behaviors would also help because Amazon Linux 2023 defaults to DNF, while Amazon Linux 2 was established using Yum workflows. This creates minor compatibility hurdles. Although we can use Yum, it would be better if those behaviors were standardized. Minor improvements could also be made regarding an enhanced terminal experience.
I did not rate Amazon Linux as a perfect ten because of the upgrade path and standardizing the package behaviors. The improvements I needed in Amazon Linux included the upgrade path, standardizing the package behaviors, and support for third-party software. That is why I rated it nine instead of ten.
For how long have I used the solution?
I have been using Amazon Linux for the past seven years.
What do I think about the stability of the solution?
In my experience, Amazon Linux is stable. I have not faced any issues with stability.
What do I think about the scalability of the solution?
In my experience, Amazon Linux's scalability is not an issue. I have not faced any issues with that.
How are customer service and support?
The experience with customer support for Amazon Linux was very good. I interacted with them a couple of times and they were very helpful.
Which solution did I use previously and why did I switch?
Previously, I was on a private cloud setup where we used to use Ubuntu or Red Hat as per the customer requirements. Later on, I switched to Amazon Linux because of its security and compatibility and everything else it offers.
How was the initial setup?
My experience with pricing, setup cost, and licensing was really good. The cost is comparatively less, and since there is no license involved when we are using it within AWS itself, the setup was also quite simple. Overall, it was a good experience.
What about the implementation team?
I took Amazon Linux from the Marketplace itself.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing was really good. The cost is comparatively less, and since there is no license involved when we are using it within AWS itself, the setup was also quite simple. Overall, it was a good experience.
Which other solutions did I evaluate?
I have not explored any other options because Amazon Linux itself has a lot of options and features which really helped me with my applications deployment and everything else. If I wanted to explore alternatives, I would have considered Ubuntu, which is also similarly very good.
What other advice do I have?
Most of what I would recommend relates to the security, performance, compatibilities, and support of Amazon Linux that I mentioned earlier. My advice is to not perform in-place upgrades. Try to identify the differences that exist between Amazon Linux 2 and 2023 before upgrading. I rated this product nine out of ten overall.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Optimized performance and tight cloud integration have delivered secure, low‑cost app deployments
What is our primary use case?
My main use case for Amazon Linux is deploying Java microservice applications, Python applications, and .NET applications. I chose Amazon Linux most of the time because my platform and infrastructure are hosted in Amazon, so the compatibility is fine with Amazon Linux while using Amazon.
I deploy applications on Amazon Linux by writing scripts in the user data script and deploying the web application from there.
Amazon Linux is deployed in my organization in a private cloud where we deploy everything.
What is most valuable?
The best features Amazon Linux offers include optimized performance and tight AWS integration. SELinux is enabled on Amazon Linux and performs automatic security patching and CVE fixes. Critical vulnerability fixes and those security features have helped me significantly. The integration with AWS CLI, Cloud-init, and services such as SSM Agent and CloudWatch agent has been useful.
Amazon Linux has positively impacted my organization primarily by providing cost savings, as we do not want to spend on the OS portion.
What needs improvement?
Amazon Linux can be improved by integrating other cloud features so that other cloud providers can also use Amazon Linux. GCP and Azure could benefit from Amazon Linux compatibility as well.
For how long have I used the solution?
I have been using Amazon Linux for seven years.
What was our ROI?
I have saved approximately five percent.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing includes working on multiple other vendor licenses for the software licensing portion. The setup cost involves initial migration planning and related activities.
What other advice do I have?
Amazon Linux cost is free to use, which provides significant cost optimization benefits that we always leverage. My advice to others looking into using Amazon Linux is to use it and save your cost. I would rate this product nine out of ten.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Running secure, automated workloads has reduced costs and simplifies cloud-native operations
What is our primary use case?
My main use case for Amazon Linux was running production workloads, primarily using it to host backend services for the company and web applications on EC2 instances while helping DevOps with several tasks, one related to QA, as a QA Analyst and QA Engineer.
I hosted a production REST API backend on EC2 using Amazon Linux which handled user authentication and core transactions for a customer-facing web application, and it scaled reliably using AWS Auto Scaling and load balancing.
Using Amazon Linux delivered ROI in several practical ways, notably eliminating OS licensing costs, saving thousands of dollars per year compared to licensed enterprise Linux options, and reducing operational effort with an estimated 25 to 30% reduction in OS-related operational work due to AWS-native defaults and predictable updates.
What is most valuable?
Amazon Linux fit very naturally into our automation and security practices, regularly used with infrastructure as code and automated provisioning, which made it easy to spin up consistent environments across development, staging, and production, aligning closely with AWS best practices.
The strongest features of Amazon Linux are its tight AWS integration, security, and long-term stability, with one of the biggest advantages being how well it integrates with AWS services out of the box.
The tight AWS integration of Amazon Linux made my day-to-day operations much simpler and more reliable, as IAM roles work seamlessly at the OS level, eliminating the need to manage static AWS credentials on instances, which improved security and reduced configuration effort when deploying new EC2 instances or scaling automatically.
Another feature I found very useful in Amazon Linux is its predictable and well-curated package ecosystem, with stable and tested repositories for AWS environments reducing dependency issues and making system updates safer in production, along with smooth integration with automation and containerized workloads.
What needs improvement?
While Amazon Linux worked very well overall for us, there could be a few areas for improvement. For instance, the package ecosystem compared to more community-driven distributions like Ubuntu, where some packages can lag slightly behind in terms of versions, occasionally requiring extra effort when newer language runtimes or tools were needed.
For how long have I used the solution?
I have been working in my field as a manual tester and then moved into automated testing for seven years in total, performing and executing test cases on some freelance platforms.
What do I think about the stability of the solution?
Amazon Linux is very stable, especially for long-running production workloads on AWS, having been able to run it on production EC2 instances for extended periods with minimal issues.
What do I think about the scalability of the solution?
Amazon Linux scales very well, especially when used in AWS-native environments, working seamlessly with AWS Auto Scaling and load balancing to scale from a small number of instances to dozens or more during traffic spikes without needing OS-level changes.
How are customer service and support?
Amazon Linux customer support is generally good, understanding that support is structured through AWS support plans and official documentation, relying on AWS for issues directly related to Amazon Linux behavior on EC2, with timely and helpful responses for performance, updates, or AWS integration issues.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
We have not used any other solution before Amazon Linux.
What was our ROI?
Using Amazon Linux delivered ROI in several practical ways, notably eliminating OS licensing costs, saving thousands of dollars per year compared to licensed enterprise Linux options, and reducing operational effort with an estimated 25 to 30% reduction in OS-related operational work due to AWS-native defaults and predictable updates.
What's my experience with pricing, setup cost, and licensing?
The pricing and licensing model of Amazon Linux is one of its biggest advantages, having no additional licensing cost and no per-core and per-instance OS fees, making cost planning straightforward by only paying for the underlying AWS infrastructure.
Which other solutions did I evaluate?
Before choosing Amazon Linux, I evaluated a few alternatives, specifically considering Ubuntu Server, Red Hat Enterprise Linux, and CentOS.
What other advice do I have?
I would advise that if you are planning to run workloads on AWS, Amazon Linux is a strong and practical choice, best suited for AWS-native, cloud-first architectures where tight integration with AWS services, security, and long-term stability matter. I would rate this product an 8 out of 10.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Automation has boosted server deployments and command tools make daily web operations efficient
What is our primary use case?
My main use case for Amazon Linux is mostly deploying servers using NGINX and application runner, and I use it as a base image in Amazon Linux itself when I write any Docker file.
In my current project, investment.in, I use Amazon Linux as a web server as well.
What is most valuable?
The best features Amazon Linux offers, in my opinion, are the yum command and the packages that are already included, along with other packages that I can easily install in the Linux environment.
These features help me in my daily work by making automation very easy.
Amazon Linux has positively impacted my organization by increasing productivity since automation is easy and fast, allowing me to set up servers easily, thus productivity increases and efficiency improves as soon as possible while deploying my application using Amazon Linux.
What needs improvement?
For the improvement of Amazon Linux, I think there should be UI features in the future, as Amazon Linux currently has only terminal capabilities without a UI, and I hope to see documentation updates as soon as possible so when documentation expires, I am updating it and referring to it soon.
When using Amazon Linux, I would prefer if any command goes wrong that an auto-command feature would appear there.
I chose eight out of ten because command line improvement is needed along with UI features, and the second thing is that you can use auto-command line features.
I do not think there are any other improvements Amazon Linux needs right now, maybe something related to security, performance, or compatibility.
My advice for others looking into using Amazon Linux is to make sure the command line is easy and that Amazon Linux has more performance than other Linux environments and is more secure than other Linux environments as well.
For how long have I used the solution?
I have been using Amazon Linux for more than five years, because I started using Amazon Linux in college.
What other advice do I have?
I have more to add about how I use Amazon Linux; using the command, using shell machines, and using the terminals in Amazon Linux could be a great experience.
I would like to add that Amazon Linux is easy to use with the command line and also user-friendly, with no need to download any third-party updates like RPM packages and then install; I just use the command line only to download directly and install directly.
I purchased Amazon Linux through the AWS Marketplace.
I think next time with Amazon Linux, whenever a bad command is returned, it could be auto-generated to create the perfect command, and that is something you can implement.
I give this product a rating of eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)