GRAVE STATUS UPDATES AND CEMETERY NEWS' Journal

AWS downtime followup (bold is my anger)

http://new-shit.deadjournal.com/60343.html

Warped Sun Aug 07 2022 15:58:44 GMT-0700 (Pacific Daylight Time)	We finished moving over to a VPC today, and ran into a snag of moving the IP to the VPC. It's locked (probably because we had you do the rdns entry before we could modify it, plus we had the port 25 allow enabled). We'd really like to keep the old IP because we've had it for so long and there is reputation scores for email that would be affected. old IP: 22.23.24.24 ( rdns is deadjournal.com ) new vpc: vpc-0[redacted] new instance i-0[redacted] NOTE: We also had the port 25 enabled and that would need to move to the VPC as well.
Warped Sun Aug 07 2022 16:31:49 GMT-0700 (Pacific Daylight Time)	[edited for time and to fit your tv screen] 11:34:03 PM Warped: I suspect someone needs to remove the RDNS from the IP, unlock it, move it to the VPC scope, then reset RDNS and the enable for port 25 for it [...] 11:39:08 PM AWS: One moment, please. I am still filling the internal ticket to request the IP release. 11:40:10 PM Warped: oh, it's not a release.. it's a change to VPC scope. release might be read as letting the IP go (which is not what we want) [Edited to remove stuff... and more explaining...] 00:07:16 AM Warped: so I suspect the process is "remove SMTP port 25 on the IP", "remove RDNS of deadjournal.com on the IP" change the scope to VPC for the IP, then add the RDNS back and the SMTP allow" [...]
	[more sparse contact omitted, more explaining ... more waiting...]
Amazon Web Services Thu Aug 11 2022 04:25:00 GMT-0700 (Pacific Daylight Time)	Thank you very much for getting back to me, and I fully understand the inconvenience this issue is causing to your production. I would like to apologize for the time it takes to resolve your case. To speed up resolution for your case, I have reached out to the internal team directly and worked with one of their engineers to resolve this for you. I was informed that due to the way EC2 classic and VPCs are structured, the system will not allow transferring IP to VPC without removing rDNS. To speed up resolution, our team removed rDNS for you manually, and you should be able to move your IP in a console to VPC now. When the transfer is done, you can add rDNS back, which according to our internal team should not take too long. I hope that the above solution helps you with your task, and please let me know if you have any additional questions or concerns. I hope you have a great day ahead. We value your feedback. Please share your experience by rating this and other correspondences in the AWS Support Center. You can rate a correspondence by selecting the stars in the top right corner of the correspondence.

So, if left to AWS, DJ would have been down completely from Sunday until early Thursday morning because someone couldn't figure out how to go flip a switch. If they weren't expiring their old network method that's been this way SINCE THE BEGINNING OF TIME, none of this would have happened. Clearly their playbook team didn't actually consider ancient VMs running... which is going to bite them badly on the 15th (tomorrow).

Anyway, I had moved everything where it needs to be on Thursday/Friday and finally got around to this nice little post-mortem.

You can follow us on the bird shitpost site: Follow @deadjournal