r/cloudcomputing • • Aug 29 '25

800 Awesome Cloud Projects to gain experience in cloud computing (free and open source)

74 Upvotes

EDIT: Now over 1100 cloud projects, with a free site to search filter sort and save: https://cloudprojects.dev/

Hey community, over the years I got a lot of questions on how to gain cloud experience from beginners and folks who have been working in cloud technologies just looking for real examples, code, diagrams, etc to help them talk about things in their next interview or just learn some new cloud services. I am releasing a free & open source learning resource for AWS, GCP, and Azure. Over 800 projects, with code, to help you learn by doing with real examples.

I spent years building these projects (I call them cloud recipes) to learn myself, and eventually released a book years ago.

I had tons of extra content… life happened, I never found the time to polish them up to the standards I wanted for future publishing. Advancements in generative AI tech and applying some agentic techniques to the repository let me polish up, QA, and tidy up this body of work and I want to donate it to the cloud professionals community.

Have a look, leave a comment, a suggestion, and I hope it helps or inspires someone to learn something new! There is absolutely nothing here for sale, this is free and open source (fork it, use however you want) and I was super motivated to get these out into the hands of the community. Enjoy!

https://github.com/mzazon/awesome-cloud-projects


r/cloudcomputing • • May 25 '22

Is there a FREE cloud based virtual machine?

71 Upvotes

Preferably “free forever” or maybe just a really long free trial?

I’ve tried Azure VMs but the free trial isn’t exactly “free” since the VM uses other additional resources.


r/cloudcomputing • • Jun 05 '24

How is it possible that companies can rent H100s for $2 per *gpu* per hour and still turn a profit?

66 Upvotes

An H100 costs roughly $25,000. Even if it was rented full time, it doesn't seem like it'd ever be profitable. In a single year of 24 hours a day, 365 days a year, you'd only make $17,000, but that doesn't include costs of power, security, facilities, etc.

Edit/Update: This has been pretty informative so far!

If anyone has any resources that I can read regarding an in-depth cost explanation of data centers, I'd appreciate it. It seems like some of my ignorant questions were downvoted, so it's probably one of those situations that I really need to gain some more foundational knowledge - I just don't know where to find it


r/cloudcomputing • • Mar 03 '19

Today's move to cloud computing, versus the move to client-server in the early 1990's.

62 Upvotes

The technology transformation to cloud is similar to other previous transformation in the past. Indeed, this transformation is similar in the many ways to the last great transformation that I worked on, which was the beginning of client-server computing circa 1990. So allow me to compare and contrast these two epochs of computing history.

The transition from mainframe to client server technologies took places in the early 1990's. Within the course of a few years, the development platform of choice moved from mainframe technologies (primarily from IBM and DEC) to client server platforms (primarily from Microsoft.) That transition was not easy - indeed, it was brutally hard on developers and consultants who had to push through it. Some of the issues we faced included:

1) Code conversion - by the 1990's, there were millions of lines of old mainframe code in Cobol, Fortran, and other legacy languages, that had to be translated to new languages such as C and C++. One alternative was to take the existing Cobol code, and simply "lift and shift" it to client-server platforms via tools such as Micro Focus Cobol.

This approach only worked partially, and sometimes gave inadequate results**.** It was relatively cheap and simple, but only gave a portion of the promise that client-server computing offered. The application that were "shifted" to client server via Micro Focus were often little better than their mainframe predecessors. To get the full value of client server computing, applications had to be re-designed and re-built in modern tools such as PowerBuilder, which took up significantly more time and money. And technical expertise.

In this issue, we see the forerunner of what we face today with cloud migration. There are tools today such as AWS Edge and Snowball, for taking on premise platforms and moving them to the cloud. They can be used to an existing VM on premise, and move it to cloud, with little or no changes to code and configuration. However, these tools do not transform technology, but rather postpone their eventual replacement or retirement. Again, they will give you results that may or may not be adequate.

To get the full value of cloud, applications will need to be rebuilt. This means switching to newer technologies such as Kubernetes, Lambda, Aurora, etc. Again, this will require substantially more effort than simple "lift and shift" approaches. But this is the only way to get full value out of the switch to cloud. Companies who have tried "lift and shift" may find themselves paying for the cloud twice - once to move there, andonce to take advance of the benefits.

Amazon currently publishes their 6 migration methods to move to the cloud. Some companies are using rehosting or replatforming for all or most of their move to the cloud. This can produce some cost savings, but not technology (or business) transformation. You need to perform at least some refactoring of your applications, in order to get the full set of benefits you are expecting.

2) Security. Early client-server computing had really inferior security. This was due in large part to the original operating system that was available for this purpose - MS-DOS. DOS effectively had no security, and any application built on top of it needed custom, bespoke security. This was made even worse by the fact that many hardware vendors were slow to implement their own security. In effect, MS-DOS computing was essentially a free for all - and this inhibited many of the early adopters of client-server computing. In truth, many applications were likely moved prematurely to client server due to the platform's lack of built-in security.

Indeed, many application designers gave up trying to install security at the client level, and simply implemented security at the server level. Fortunately, many of the server level products - particularly Oracle - had these components built in. So the data had to be secured at the server level - and the security at the client level had to adopt that as well.

Later, MS DOS was replaced with the Windows product from Microsoft, and the situation slowly improved. Windows eventually offered encryption, single sign on, and other capabilities that are needed for truly secure computing. Products such as Active Directory finally gave client-server computing the security capabilities that approach that of mainframe computing. Microsoft platforms finally offered security capabilities that mainframe computing realistically never had - such as biometric scanning,etc.

Fortunately, with the transition to cloud, the major vendors recognized this issue from the very start. It would be impossible today to sell a product to corporate CIOs with the security gaps that client-server computing originally had. So the major cloud providers - AWS, Microsoft, etc. - all have implemented security tools that equal, or in some cases exceed, those of on premise computing. Amazon, for example, has its VPC and Directory Services offerings that are as good, if not better, than what is available on premise. Amazon has a marketing slogan that "Security is job one", and they are endeavoring to make that slogan a reality.

In truth, many CIOs are looking to the cloud as a way to get around existing security deficiencies in their on premise environments. Many companies have legacy environments that haven't been patched effectively, or haven't been encrypted effectively - and they are looking to SAAS and PAAS solutions to alleviate these issues, quickly and simply. In short, the issue from the 1990's exists today - but the issue has actually been inverted, so that now the destination technology can address the problems with the source technology.

3) Talent - When client server computing first came into vogue, there was an extreme talent gap. There were nowhere near enough analysts, developers, architects, or managers, with the knowledge or experience in the technology, to deploy it effectively. Many of those who moved into client-server were old-school mainframe developers, who had to be re-tooled and re-skilled, in order to work on the new technology. This hampered the switch to client-server technology to a significant degree. For much of the 1990's, there simply were not enough people to do this job.

Fast forward today, and there is still a skills gap - except that now, it is in consultants with cloud skills. What is particularly lacking are persons with knowledge in cloud architecture; skilled cloud architects are ata a real premium. And as in the past, many of those who are selling themselves as cloud experts are, in fact, individuals with on-premise skills who have repackaged themselves as cloud experts. This skills gap will need to be addressed, as more and more applications are moved to the cloud.

Some cloud providers are actually offering training at discounts, to try to bridge this gap. AWS for one has the Amazon Educate program, to help students make this transition in a rapid fashion.

4) Networking - Networking capacity has seemingly always held up technology transformation. In the switch to client-server, in many cases, networking capabilities simply did not exist, and had to be built from scratch, in order for these client-server technologies to actually work.

In the 1990's, many corporate offices had no LAN capabilities whatever. Client-server and networking had to be deployed in parallel, or in other cases, in close sequence, in order for client-server to actually work. Ethernet cabling had to be strung in order for some client-server projects to actually proceed. Stand-alone desktop PCs needed to have NIC cards deployed, in order to connect to networks on which the client-server technologies had to be deployed. Network routers had to be upgraded, in many cases, in order for the client servers to have enough bandwidth capacity.

Today, many cloud migration efforts are being hampered by networking issues. The major cloud providers themselves are not the bottleneck; in fact, their networking architecture is typically state of the art. Rather, the architectures of cloud customers are often lacking the necessary bandwidth to move all of the content to the cloud. In some cases, petabytes of on premise customer data need to move to cloud - and the existing networking architecture simply cannot move all that data in the necessary timeframes. Again, technologies such as Snowball can help get past the issues with networking capacity - but this can be expensive.

In short, many of the problems of the past have been visited on the technologists of the present. Those technologists should learn as to how those issues were resolved a quarter century ago, so that the issues can be resolved in this transformation. All these issues have to be part of your risk planning and assessments before attempting any cloud migration. How will you transition your code? How will you secure your data? What will be your networking infrastructure? And where will you get your skilled workforce from? Answer these question first.


r/cloudcomputing • • Oct 29 '19

Data centers, fiber optic cables at risk from rising sea levels

Thumbnail
datacenterdynamics.com
53 Upvotes

r/cloudcomputing • • Aug 24 '26

How should I start learning cloud computing as a Beginner?

48 Upvotes

Hello guys! I’m a final-year student and I’m very interested in cloud computing. As a beginner, where should I start, and what topics should I learn first?

Are there any free resources, WhatsApp groups, communities, or other platforms where I can learn cloud computing with hands-on projects?

I’d really appreciate any recommendations. Thanks!


r/cloudcomputing • • Nov 27 '25

Anyone else seeing a shift toward rack level BBUs in new 800V cloud builds?

48 Upvotes

I’ve been going through some of the newer 800V HVDC reference designs from Nvidia and Meta, and something that stands out is the move toward putting a small BBU/energy buffer inside each rack instead of relying only on room-scale UPS systems. The goal seems to be handling fast transient loads locally so the upstream power gear doesn’t get slammed every time the accelerators sync.

One example I’ve run across is the KULR ONE Max, which is basically a rack-level buffer designed for these high density setupss. But I’m more curious about the cloud architecture side, does distributing the buffering change how you think about pod design, redundancy, and how big clusters scale?

If anyone here works on cloud infra or high-density deployments I’d love to hear how this trend is showing up in real environments


r/cloudcomputing • • Apr 23 '21

Google Cloud vs AWS vs Azure (which should I learn in 2021?)

48 Upvotes

I’m fairly knowledgeable on the basics of all 3 platforms and have some basic understanding of cloud computing which I use to run Linode and DO servers.

I’d like to know what the general consensus is. I’m looking to further my professional career and gain on demand cloud skills to compliment my marketing skills and take on higher roles.

So which platform do you recommend I gain certification in? I know AWS has the biggest market share but is the market currently saturated? Are companies still hiring AWS engineers?

Thanks guys!


r/cloudcomputing • • Mar 11 '21

2021 Analysis of cloud provider market share, based on IaC developer interest.

44 Upvotes

https://steampipe.io/blog/aws-azure-gcp-where-to-build

tl;dr AWS is as big (duh) and still growing faster than others. CloudFormation is a huge competitive advantage for AWS but Terraform is leveling the playing field for Azure, Google, Oracle, DigitalOcean and Alibaba.

Couple interesting facts:

  • Although released at the roughly the same time, the Terraform AWS provider has 268M downloads; over 6x more than Terraform Azure (41M) and GCP (38M)

  • Looking at Google search trends, there was a huge drop off in interest (searches) for all cloud providers in the second half of last year and continuing into 2021.


r/cloudcomputing • • 18d ago

Where to start from as a beginner?

41 Upvotes

I want to explore and learn cloud computing, especially GCP and AWS. I have about a month to get myself acquainted with it.

Suggest me some good resources to learn. Youtube videos, textbooks, blogs, anything works. If there's anything that helped you when you started learning cloud, please share them!!

I'm feeling all over the place. I'm extremely confused as to how to begin. Help me out guys.


r/cloudcomputing • • Jul 10 '21

NEWS: Pentagon cancels $10 billion JEDI cloud contract that Amazon and Microsoft were fighting over

37 Upvotes

r/cloudcomputing • • Jul 13 '24

Which cloud provider do you prefer: AWS, Azure, or GCP? Why?

36 Upvotes

I'm trying to decide on a cloud provider for my next project an app which will include user to upload photos videos I'm curious about the community's experiences and preferences. Which of the big three cloud providers do you think is best: Amazon Web Services (AWS), Microsoft Azure, or Google Cloud Platform (GCP)?

I'd love to hear your thoughts on:

  • Ease of use and learning curve

  • Pricing and cost management

  • Service offerings and unique features

  • Performance and reliability

  • Documentation and community support

  • Database used along with it


r/cloudcomputing • • Sep 27 '21

What are some cool things I can add to my cloud portfolio?

31 Upvotes

Looking to get a job in cloud and I have some AWS certs. I now need a 'cloud portfolio' of things I've been able to do in the AWS cloud. Where can I start? It seems so vast.


r/cloudcomputing • • Sep 12 '20

Clouddraw - draw cloud architecture diagrams with ease

30 Upvotes

Hi guys

Two weeks back I decided to convert my side project and personal tool to public. It is finally live.

Clouddraw (https://clouddraw.app) allows you to create beautiful cloud architecture diagrams with ease.

I downloaded and organized more than 1000 official images from AWS, Google Cloud, Azure, Firebase and others like Digitalocean, Slack etc and built this tool. I use this to generate quick architecture diagrams for my personal projects.

Here are some of the features

  1. Offline support - Save your diagram offline in browser local storage to continue later.

  2. PNG - Export your diagrams to png to embed anywhere.

  3. Keyboard shortcuts

  4. Font Awesome support

  5. Embed anywhere - You can embed your diagram anywhere and show up-to-date diagrams in your documentation (coming soon).

There is no signup required. You can start creating your diagrams right away.

Please let me know what you think :)


r/cloudcomputing • • Dec 03 '21

Which cloud platform would you learn (first)?

29 Upvotes

I want to learn and get certified in either AWS, GCP, or Azure in 2022 but I don't know which one to go for. AWS seems like an obvious choice given its sheer dominance, however, I would like to hear opinions of other people as well. My main scales are documentation, support, tutorials, demand, pay, and how much value does the certification hold (if you have something additional, I'd be glad to hear it)


r/cloudcomputing • • Sep 14 '26

The infra mistakes I keep seeing in pre-seed startups

25 Upvotes

I've reviewed quite a few pre-seed cloud setups, and the pattern is surprisingly consistent.

10 customers, 50 microservices.

Kubernetes for two services.

Multi-region before product-market fit.

Separate databases for everything.

Managed services everywhere.

Complex CI/CD and observability stacks before there's meaningful traffic.

Infrastructure is built for millions of users when there are barely 1,000.

The cloud bill still shows up.

We're offering free cloud architecture + FinOps audits for early-stage startups.

Here's how it works:

You walk us through your current cloud setup on a short call.

Within 48 hours, we send you a report covering your architecture and cloud spend.

We identify where infrastructure can be simplified and costs reduced.

We highlight the 3 things we'd fix first: infra/security risks, scaling problems waiting to happen, and quick wins.

Our philosophy is simple:

Build infrastructure for your first 1,000 users, not the million you don't have yet.

Keep it lean. Keep cloud costs under control. Add Kubernetes, microservices, multi-region and other complexity when the product actually demands it.

If you're building an early-stage product and want a second set of eyes on your cloud infrastructure, happy to connect.


r/cloudcomputing • • Oct 20 '25

What we can learn from the AWS North Virginia Outage

25 Upvotes

From time to time global services cease to work from a incidence in AWS's North Virginia region. This just happened today 20th October , it has become a cyclical event that happens at least once a year.

North Virginia (or us-east-1 in AWS terms) is know to be the first region of Amazon's cloud provider. Not only is the oldest one, it is the first one to receive updates, making it the Guinea Pigs of the features released on this Cloud. Many companies still use it as their primary region for this exact reason, they want to develop with the latest features of the provider.

But then instead of trading off the reliability of your system, have your production environment in another region ( for example Ohio us-east-2 is a good candidate for US based companies ) and keep your development environment in us-east-1. This way you get to develop with the latest features in the most experimental region while having the chance of promoting them to a more stable region like Ohio. Personally, Stockholm is my preferred region, since in Europe it's the most cost/effective and it's the most stable, even if it comes to the trade off of new features (for example it doesn't have the t3a instances yet).

Did you experience any issue with the AWS outage? Our team had some minor issues with Framer and Jira. What's your multi region strategy if you have one?


r/cloudcomputing • • May 07 '26

Cloud migration was easy. Managing Azure costs later was the hard part.

24 Upvotes

We migrated a few workloads to Azure last year thinking the difficult part would be the migration itself.

Honestly, the migration went smoother than expected.

What became difficult later was:

  • cost visibility

  • scaling correctly

  • storage growth

  • performance tuning

  • cleaning up unused resources

  • balancing security vs spend

Especially once multiple teams started deploying resources independently, the monthly bill became a moving target.

Curious if others here found cloud management harder than the actual migration phase.


r/cloudcomputing • • Jul 18 '22

Azure vs AWS vs Google?

24 Upvotes

Hello all,

I'm not asking what you guys think is best to use as a service, but rather which platform did you all decide tonstudy and pursue?

I have heard that since AWS is the most popular, that means they pay the least and vice versa. Is this true? My plan is to do cloud security after the CCNA. I know it isn't needed, but wanted a solid grasp of networking before learning a bit of coding and cloud security. I'm not sure if this matters, but, I live in Texas.

I guess my big question is, which platform would be best to pursue here for cloud security? Should I gonfor AWS since they are the biggest?


r/cloudcomputing • • Jun 21 '21

WikiLeaks created a map showing where Amazon’s data centers are located

24 Upvotes

Amazon, which is the largest cloud provider, is notoriously secretive about the precise locations of its data centers. While a few are publicly tied to Amazon, this is the exception rather than the norm. More often, Amazon operates out of data centers owned by other companies with little indication that Amazon itself is based there too or runs its own data centers under less-identifiable subsidiaries such as VaData, Inc. In some cases, Amazon uses pseudonyms to obscure its presence. For example, at its IAD77 data center, the document states that “Amazon is known as ‘Vandalay Industries’ on badges and all correspondence with building manager”.

Amazon is the leading cloud provider for the United States intelligence community. In 2013, Amazon entered into a $600 million contract with the CIA to build a cloud for use by intelligence agencies working with information classified as Top Secret. Then, in 2017, Amazon announced the AWS Secret Region, which allows storage of data classified up to the Secret level by a broader range of agencies and companies. Amazon also operates a special GovCloud region for US Government agencies hosting unclassified information.

While one of the benefits of the cloud is the potential to increase reliability through geographic distribution of computing resources, cloud infrastructure is remarkably centralised in terms of legal control. Just a few companies and their subsidiaries run the majority of cloud computing infrastructure around the world. Of these, Amazon is the largest by far, with recent market research showing that Amazon accounts for 34% of the cloud infrastructure services market.

Until now, this cloud infrastructure controlled by Amazon was largely hidden, with only the general geographic regions of the data centers publicised. While Amazon’s cloud is comprised of physical locations, indications of the existence of these places are primarily buried in government records or made visible only when cloud infrastructure fails due to natural disasters or other problems in the physical world.

https://wikileaks.org//amazon-atlas/


r/cloudcomputing • • Feb 19 '21

Curated GitHub repository on how organisations around the world use AWS

24 Upvotes

I’m curating engineering blog posts, videos and other cool resources on AWS

https://github.com/upgundecha/howtheyaws


r/cloudcomputing • • May 16 '26

teams managing access visibility across SaaS environments?

23 Upvotes

I’ve been noticing that as organizations move more workflows into SaaS platforms like Google Workspace, Slack, and Salesforce, access management becomes much more difficult to reason about than traditional infrastructure permissions.

In cloud infrastructure environments, access boundaries are usually centralized and relatively structured, but SaaS collaboration tools introduce a much more dynamic model where files, folders, links, and third party integrations continuously change who can access sensitive data.

What makes this especially challenging is that exposure often happens gradually over time through inherited permissions, external sharing, and accumulated access rather than a single obvious security event.


r/cloudcomputing • • Aug 24 '24

Azure - racked up a masiive bill of 34,000 USD / 28 lakhs INR - HELP

23 Upvotes

Azure - racked up a masiive bill of 34,000 USD / 28 lakhs INR - HELP

I am doing my undergrad in ENTC and for one my projects I tried to use Azure Open AI services. I first used the free trial which got over almost immediately and then I picked the pay as you go subscription because there was no other option available. I tried to deploy chat gpt 3.5 but didn’t connect to any API and didn’t use any tokens either. I haven’t actually used the account for anything and didn’t deploy anything and nothing was in production either. Before using azure I did watch a hour long deployment videos none of which mentioned these costs and these costs were not visible anywhere either while selecting the paid option. I also set a 20 USD limit on my credit card and thought that any charges would be automatically cancelled since I’ve set this limit and so the amount CANT go through. I have raised a ticked to Microsoft. I am unemployed and in university and I don’t have any way of acquiring this kind of money. Please help


r/cloudcomputing • • Aug 29 '22

Cheaper alternative to AWS?

23 Upvotes

AWS is ridiculously expensive when comes to running a database, and a web server 24.7. To be honest, I can't afford it. Is there a cheaper alternative to it?


r/cloudcomputing • • May 13 '22

7 ways to save on AWS

23 Upvotes
  1. Overused resources 💰
    Do you really need more than one load balancer in an AWS account, for example? Such resources can unintentionally multiply when added by different automation pipelines, or because architecture patterns change over time.

  2. Underused resources 💰
    Large AWS EC2 (or RDS, Redshift, ECS, etc) instances may have been created and sized to handle peak utilization but never reviewed later to see how well the storage, compute, and/or memory is being utilized.

  3. Abandoned resources 💰
    AWS Load balancers may not have associated resources or targets; RDS databases may have low or no connection counts; a NAT gateway may not have any resources routing to it. Even if an EBS volume is unattached, you are still billed for the storage.

  4. Generation gaps 💰
    New generations of cloud resources often deliver better performance and capacity at a lower unit price. For example, when you switch from the previous generation of EBS volumes, gp2, to the current generation, gp3, you can realize up to 20% cost saving!

  5. Stale data 💰
    How long should Amazon EBS snapshots be retained? How long can data in a DynamoDB table remain unchanged? You'll want to set policies that define when data becomes stale, and review snapshots or tables that exceed those limits.

  6. Capacity planning 💰
    If you have long-running resources, it's a good idea to pre-purchase reserved instances at a lower cost. This can apply to long-running resources including EC2 instances, RDS instances, and Redshift clusters.

  7. Cost variance 💰
    Have your per-service costs changed more than allowed between this month and last month? You'll want to pay close attention to cost spikes. When there's been an increase, can the app owner explain why?

Further reading: https://steampipe.io/blog/aws-thrifty-top-savers