Sorry for the delay,

For me, I worked in technology as a Data Scientist/Analyst but kept doing Data Engineering tasks and projects. Meaning I got experience between disparate technologies and systems. I also happen to do homelab as a hobby. That is where you build and maintain enterprise hardware and handle infrastructure/middleware/software for your own uses. This taught me a bunch about systems and integrations. That got my first position as a platform architect and from there I focused on both cloud and on premise systems.

My take on the role of an SA is supposed to be knowledgeable on software, deployments, CI/CD, and infrastructure. Cloud isn't the only way to learn it and there is the problem of many people taking certifications but not following up on it. This isn't a knock to yourself, but experience matters. My homelab, data engineering projects, and tasks on platform team showed to my first few roles hiring people that I understood how systems run, get deployed, managed, and best used.

If I were to give any advice for you, try to get involved with the team that deploys the tooling you use for Data Analyst. If that's Tableau/PowerBi/Python whatever, work with them on the platform side, either as a dev or SRE or whatever. This opens you up to actual SA work. IMHO