Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Setting up a server in Amazon ec2. Running all the commands to install nginx and everything.
Only to realize I have been running those commands in my local VM instead of ssh.2 -
I'm a DevOps engineer. It's my job to understand why this type of shit is broken, and when I finally figure it out, I get so mad at bullish players like AWS.
It's simple. Install Python3 from apt.
`apt-get update && apt-get install -y python3-dev`
I've done this thousands of times, and it just works.
Docker? Yup.
AWS AMI? Yup.
Automation? Nope.
WTF? Let's waste 2.5 hours and figure out why this morning.
In docker: `apt-cache policy python3-dev` shows us:
python3-dev:
http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
But in AWS instance, we see we're reading from "http://us-east-1.ec2.archive.ubuntu.com/... focal/main" instead!
Ah, but why does it fail? AWS is just using a mirror, right? Not quite.
When the automation script is running, it's beating AWS to the apt mirror update! My instance, running on AWS is trying to access the same archive.ubuntu.com that the Docker container tried to use. "python3-dev" was not a candidate for installation! WTF Amazon? Shouldn't that just work, even if I'm not using your mirror?
So I try again, and again, and again. It works, on average, 1 out of every 5 times. I'm assuming this means we're seeing some strange shit configuration between EC2 racks where some are configured to redirect archive.ubuntu.com to the ec2 mirror, and others are configured to block. I haven't dug this far into the issue yet, because by the time I can SSH into the machine after automation, the apt list has already received it's blessed update from EC2.
Now I have to build a graceful delay into my automation while I wait for AWS to mangle, I mean "fix up" my apt sources list to their whim.
After completely blowing my allotted time on this task, I just shipped a "sleep" statement in my code. I feel so dirty. I'm going to go brew some more coffee to be okay with my life. Then figure out a proper wait statement.7 -
Ok, this is my first post here...and I came here to rant - I had heard about this place, but I guess I just hadn't had a bad enough day...until today...the day I found my ec2 instance was playing hide and seek with me. I just found out that my aws billing dashboard is going to swoosh 2000rs (30$) out of my wallet. Imagine ranting about this to a layperson... ok anyway, I had taken a t2-medium (my first one ever) for a hackathon and I was just playing with the regions I guess and it somehow ended up in the ohio region. I had given IAM access to some of my teammates and they were using it. We were supposed to shutdown the instance after 1 day. The next day I check the dashboard (for N.Virginia - which is the default) and I see no running instances. I thought ok my teammates must've turned it off and I left it at that. A month after the hackathon, I login today and I have this jaw-dropping moment. I now have to pay 30$ for nothing!
2 -
Day 0: thank you for being an Amazon Customer, your database is about to be upgrade in the near future with or without your consent! Tough titties motherfucker!
Day 16: ok, every upgraded by hand in the test environment, everything seems stable, let's go make preparations for production!
Day 16.5: ssh user@<prod_bastion_ip> --yada --yada
Unable to connect
Oooook, let's try again,
Unable to connect
Day 16.5.1: WHY THE FUCK NOT, the IP is fucking right, the cert is right, the user is right, the..... fucking.... EC2 instance has been......... terminated.....
FML!
---
Why! why can't people leave things alone.
Excuse me while I hit the bourbon 🥃 -
my job went from being a programmer ==> technical support girl for the whole company D:
its kinda annoying because its mostly about amazon ec2 instances and i have to chat with the support team from amazon when something goes wrong while following the steps (that the others could have followed instead of going to directly to me to make me do it)
now i have to try and fix all the problems occuring in the servers :((6 -
I spent 4 hrs today setting up an Amazon ec2 instance. I screwed up one configuration file and broke everything. Grrrrrrr.2
-
I decided to use Docker Compose on a tiny project that essentially consists of an API and a Caddy server that serves static files and proxies to the API, all of this running on an EC2 t1-nano. I made this admittedly odd choice because I wanted to learn Compose and simultaneously forego figuring out why the node-gyp bindings for sqlite3 refuse to build on EC2 even though it builds just fine on my machine.
I am storing secrets in .env which is committed into the private GH repo. Just now I came across a rant that described the same security practice and it sounded pretty bad from an outside perspective so I decided to research alternatives.
Apparently professional methods for storing secrets generally have higher system requirements than a t1-nano. I'm not looking for a complex service orchestration system, I'm not trying to run an enterprise on this poor little cloud-based raspberry pi. I just want to move my secrets out of the Git repo,
Any tips?9 -
Anyone else having trouble with apt-get install in EC2 instance of region US-East-1? Seems it's too slow currently!
-
What's the most cost effective way of hosting a Lamp stack website? I have a pretty basic website with less than 50 viewers per week.
I am so confused with all the options: GCP, Amazon lightsail, Ec2, godaddy, heroku, etc.
What would you guys recommend for such a small website? Currently, I've hosted it on Ec2 for the first year but I don't think that's cost effective at all after the first year.4
Top Tags
Weekly Rant
View