I’m now relaying outgoing email through #AWS#SES, because if you can’t beat ‘em, join ‘em. It’s worth every penny (costs about $0.03/month) to never worry about my IP getting blocked, and now I can move my infrastructure easily.
Hmmm so question for you #MySQL/#AWS folk out there:
I always thought that, at least for databases that are less than gigantic, "mysqldump --single-transaction" was a good backup option.
Turns out that that doesn't work on AWS Aurora, apparently because it doesn't give you the necessary privileges for FLUSH TABLES WITH READ LOCK.
What am I missing? Is that option obsolete or no longer needed to get a consistent backup? Do people use completely different means to back up Aurora databases?
Me: I need #AWS Session Thingy
AWS: First you must enable Cloud Florper. It’s free!
new tab
AWS: To enable, you must setup Cloud Flurper.
Me: But I just…
AWS: No this one’s different.
new tab
AWS: To use Cloud Flurper, we highly recommend you enable Combobulator. Otherwise you won’t be able to use Identity Blarping in the future!
Me: OK fine.
new tab
AWS: Welcome to Combobulator (formerly Amazon Identity Cromulator)
Me: Please, just enable.
AWS: OK, $500/month
But I'm thinking more about terraform or kubeconfigs where I can reference a role arn and the tooling switches automatically as long as I'm signed into my default profile.
It wasn't my app, turns out it was the AWS firewall blocking the call because the string that contains "system (A)" in it.
"A" in that string can be any value.
Looks like my only way to customize the WAF is to turn off the rule that has the false positive. Which I don't want to do because there could be other good things it catches.
WAF users... any thoughts on the PHPHighRiskMethodsVariables_BODY ruleset on API calls over HTTPS?
This was a fun distraction & taught me about Lambda. I was pleasantly surprised that I could deploy a Vapor application with its own routing and such behind “serverless functions"
I also rewrote (because of course I did) the front-end, as Leaf templates were -let's be honest- not a great experience.
The front-end is now Svelte, and uses Vite as a development server. I'm pretty happy with this combo.
Another #lastweekinaws / @Quinnypig tidbit: #aws#cloudfront has 600+ "embedded POPs" inside ISP networks. You know, the thing Akamai has been doing since the 90s.
Ricardo Sueiras, Principal for open source at #AWS will speak about “Getting started with Apache Airflow - building your first workflow” at #FOSSASIASummit2024#Hanoi#VietNam
First day in newest role at AWS: Still a Developer Advocate but am on the AWS Open Source Strategy & Marketing team now helping folks be better at all the open source things. #OSS#OpenSource#AWS
Today we've discovered that a Python 3.8 Lambda function on AWS was failing to change the desired capacity in an autoscaling group. Updating the runtime to Python 3.12 fixed it; it had been working fine for months but started failing yesterday. Slightly terrifying.
Here is my toot resume in case anyone has open positions:
Experience: staff software engineer, #backend#webdeveloper, #python, #django, #postgresql, #terraform, #redis, #rabbitmq, #kubernetes, #aws, #gcp
I get things done and worked with pretty much any tech out there. I learn fast, have no problem coding in other languages. I have experience leading teams. I helped growing an engineering team from 10 to 150 engineers. I know how to scale things. My code is resilient and has tests. #fedihire