infra-as-code | Instalação e configuração de serviços de infraestrutura com

Well, I don't know why people get upset about this question. I think it's a fair question to ask. Here are my thoughts and things that I want to point out. Feel free to discuss this in the comments section.

Ansible is slow

Yes, I agree. If you deploy a large and complex system, it can easily take Ansible playbooks dozens of minutes if not hours to run.

Ansible playbook may fail because the package which should be downloaded from open-source repository have been changed/removed sometimes

You don't need to worry about this too much. Chances are it rarely happen. Linux package managers pull from these open-source repos frequently everyday. This has never been an issue, and not to mention these repos are very well maintained and a breaking change like this is unlikely. So I don't think this should count as an Ansible drawback.

Managing AMIs is faster and easier

This is only true in a small scale. If you only have serval dependencies in your environment, it's probably not worthwhile to write everything in IaC and maintain them in version control. However, as systems grows, more complexity needs to be added. You will quick find the IaC approach handy. It allows all changes to the infrastructure to be recorded in the SCM. It enables different developers to work on same infrastructure in parallel etc etc. I can probably tell you a thousand advantages of IaC compared to doing it by hand in AMI. Again, this all depends on your scale. The best approach is the one that fits your need.

Hope this helps.