What I like most about AWS Backup is how it centralizes and automates what is usually a very fragmented, manual process. Instead of managing backups separately across services, you can define policies once and apply them across resources like EBS, RDS, and DynamoDB. The built-in scheduling, retention rules, and cross-region/cross-account backup capabilities make it easy to stay compliant and resilient without constant oversight. It basically turns backup management into a “set it and trust it” system, which is a huge win for both efficiency and risk reduction. Análise coletada por e hospedada no G2.com.
One of the biggest downsides of AWS Backup is that it can feel overly complex and not very transparent when something goes wrong. Error messages and job failures aren’t always easy to diagnose, which can slow down troubleshooting. The pricing model can also be a bit opaque, especially when you factor in cross-region storage and restore costs. On top of that, while it centralizes backups, not every AWS service is equally supported or configurable, so you sometimes still have to manage edge cases outside the platform. Análise coletada por e hospedada no G2.com.
