Top Pitfalls in Cloud Infrastructure
Architect-ing on cloud can be complex, and given AWS’ wide diaspora of services available, it can be quite a challenge.
In this note, I just want to list out some common pitfalls that if we avoid, not only makes our IT estate more resilient, but also saves $!
Managed NAT Gateway — e.g. traffic leaving the AWS ecosystem to the internet, and coming back again to the AWS ecosystem to access another AWS resource
Data transfers — e.g. data replication across multiple regions/AZs
EBS — idle EBS volumes, unattached even; over-provisioned IOPS
Insecure S3 bucket — needless to say, can be a major risk if its left open unintended
Cloudwatch logs everywhere, no expiry configured
EMR — Ideal to use spot fleets, but not using
Of cause, this is not an exhaustive list as AWS continues to overwhelm us with more great service offerings. Happy architecting!
