You should probably focus on your contribution and what you did.
Lets take fixing the bug that would have cost money. What are the chances any of your colleagues would have fixed that bug just the same you did? Was it just chance who ducked last when the supervisor dealt issues to fix to each of you? And why was it 5%? Would it have been only 4% if someone else had fixed it? Or lets take the 33% savings on the cloud provider move. Was it something you came up with on your own? Why was it 33%?
My point is: none of those "accomplishments" tell me anything about you. Try to find out what stands out about you that made those accomplishments possible in the first place.
Maybe you were on top of the market rates of cloud providers and could support the decision with facts and numbers. Maybe you knew the technology to switch to. Maybe you had the skills to fix the bug that nobody else had. Tell those stories. They don't need monetary value, because you don't actually have any influence over that. You saved 33% on cloud providers because one was 33% cheaper than the other. If you own neither of the two providers, then that's not exactly your accomplishment. If it had been only 10% cheaper, you would have saved only 10%. The point is that your skills enabled a company to switch providers at all, that is the useful bit of information to sell yourself, that is a big project to have worked on and advertise.
Don't tout numbers. They are meaningless. Tell the story of what you did to make that happen, what skills you have to help their business.
Related question: Contributions in a CV for developers
As a real world example of what I mean: I once fixed a bug that would have cost the company half a million Euros. Not in some obscure estimated or "opportunity lost" way, but in the hard cash way where the companies contract says they will pay half a million in penalty for breach of contract if it isn't fixed in 24 hours. What did I do? I got the bug ticket, I opened my IDE, I saw that the previous developer had ignored a warning that warned of exactly the bad behavior we were observing, I fixed it and deployed it. It was nothing special. Just a day at the job. Most of my apprentices could have done it. "I saved the company 500.000€ in a day" is both true and completely meaningless without context. I made sure that nobody would ever again be able to check in code that had unsolved warnings, so this would not happen again. That was my accomplishment. Not everybody would have done that. And I'm happy to talk about that.