4 ms·
Few easy ones as well: 1) Terminating instances that had ephemeral disks with stuff you needed while thinking the EBS volumes would remain 2) Leaving NAT gate
by tedk-42 5y ago
Few easy ones as well:
1) Terminating instances that had ephemeral disks with stuff you needed while thinking the EBS volumes would remain
2) Leaving NAT gateways lying around or ELBs that do nothing and have no instances attached.
3) Public S3 buckets - arguably the most common one that can lead to security incidents
4) Debugging security groups/Network ACLs and straight up break networking for something without knowing it. Reverse of that would be you want to fix something quickly and open 0.0.0.0/0 to everyone and never get around to tightening up the firewall later on.
- jnieminen 5y agoI was playing with the Azure "free" tier. Even I tried to be extremely careful with it, after a while noticed that I had left a storage blob for a VM hanging around and some external IPv4 address. I will continue to use Hetzner online for my own stuff instead running this on "public cloud".
- hacker_newz 5y agoI don't understand how anyone could complain about public S3 buckets. You have to go out of your way to do this.