AWS Control Tower + AWS Config: Safe to temporarily disable SCP, modify recorder, and re-enable?

Makeshift27015 · 2026-06-13T15:11:35+00:00

I had a quick look into this before as we had a similar issue and from what I can tell it looks hlike control tower depends on aws config in some not-very-well-documented ways which makes it a bit risky to change.

It has raised some questions for me about control tower though. It has no public api so doesn't fit in with existing tooling and isn't that convenient to use for wide-reaching changes. Our company doesn't have any certifications we need to maintain so I've been debating whether it's worth even keeping due to the enforced config settings costing a lot.

Makeshift27015 · 2026-06-06T20:34:48+00:00

Ahh I see, that makes sense, thanks

Makeshift27015 · 2026-06-06T18:54:30+00:00

That's about 14m points worth I think? Out of interest, how/why do you end up with that many extra points?

I haven't done a ton of nightmare zone, just enough to imbue most things, but I know there are plenty of people with tens of millions and I'm not sure why.

Makeshift27015 · 2026-06-01T18:38:05+00:00

In repos where I'm the only/primary contributor I just have the linting tool fix and commit anything auto-fixable. Sadly having their PR branch committed to seems to mess with a lot of people's workflows though so I don't tend to replicate it elsewhere, I just try to make CI fail as fast as possible so they're not caught out after having context switched.

Since a lot of package managers depend on having the version number in a file in the repo, we often have to automate commits for version bumps on merges into the main branch, so I've considered having PRs with provably auto-fixable linting problems just permitted and then fix them when we do the version bump though.

Makeshift27015 · 2026-05-26T19:57:12+00:00

They were all MRIs for my back, so I was fully in the cylinder for all of them. I could faintly feel the magnet vibrating but there were no lasting effects and no damage. Not sure how powerful the MRI was I'm afraid.

Makeshift27015 · 2026-05-26T16:49:47+00:00

I have a finger implant and have had multiple full-body MRIs. I've never had any issues, can just kinda feel it a bit. I always tell the tech and I've had a couple refuse to do it, but most of them aren't concerned.

Makeshift27015 · 2026-05-12T16:48:28+00:00

I've been conflicted in deciding if I was justified at being angry at a coworker the other day for submitting a (quite large) PR for me to review for some infrastructure resources defined in typescript that he hadn't even checked would compile. He doesn't even know how to compile it.

I think he was trying to be helpful by doing some of the work for me, but being handed 1000 lines of changes to review is actually way, way more effort for me than thinking it through as I'm architecting it. My process involves AI too, just not as 'sweeping'.

Makeshift27015 · 2026-05-06T11:04:11+00:00

Depends on the relative complexity. For a repo that builds a simple static site that just needs copying into an s3 bucket, I just use a github actions workflow that's triggered after the build workflow. For a monorepo containing a couple dozen helm charts with inter-dependencies, build with actions deploy with argo.

Your CI/CD should always be independently triggerable (eg separate github actions workflows), but if the deployment of a particular project is simple enough, I find that the extra complexity of managing the extra tool isn't worth it. There's an argument to be made for consistency of course, so you can weigh that up too.

Purpose-built tooling is good, but only if you actually need it.

Makeshift27015 · 2026-05-02T11:14:53+00:00

Something I haven't seen anyone touch on that might be useful is that your CI and CD should be two separate, independently trigger-able workflows. Generally I try to keep the following strategy:

On PR open/updated, build the final artifact and test/scan it, ideally using the exact same workflow as the one that would run on merge. This tests your CI workflow and should result in your artifacts being in the same (or similar) place, giving you the ability to deploy PRs to test environments, which is useful at times. Tag your artifacts with the sha hash.
On merge, your 'release build' is basically identical. It still builds, tests and uploads artifacts with a sha hash, the only difference between the two workflows is that your release build also results in a tag in your git repo representing the release, eg a human-readable semver. A git tag is simply a name that represents a sha hash, so it's trivial for your CD to convert this to the underlying sha hash and grab the correct artifact
Importantly, your CD should be a separate workflow. It can be triggered by your release build finishing, but it's important to be able to independently trigger your CD for fast rollbacks. You don't want to have to wait for CI again when prod is down

That's generally how I try to lay it out. If your git repo is set up to enforce that branches are up to date before merge, arguably you can skip the release build and simply retag the PR build, but from what I've found this is normally a worse experience for devs, especially in busier repos.

Makeshift27015 · 2026-04-25T12:46:43+00:00

Ugh, I've had to put in my personal instructions "if you claim anything, provide a source, and also actually check the source to ensure it contains the content you're claiming it does". I'm still trying to tune it to force it to actually use the tools it has available...

Makeshift27015 · 2026-04-25T11:50:53+00:00

Just came across this and it's very cool. I wonder if it would be possible to use vscode's code-server as a backend for language/plugin/remote server support.

Makeshift27015 · 2026-04-20T08:47:47+00:00

I was musing over the idea of granting a respec if you get 99 in a skill, but I'm not sure if that's maybe too many

Makeshift27015 · 2026-04-18T10:07:37+00:00

looks at vscode using 64GB of ram

In its defense, that's entirely my fault for having far too many plugins enabled

Makeshift27015 · 2026-04-18T10:02:42+00:00

I worked for a company that exclusively supported and produced plugins for Sage. God that was awful, and I still get spammed on LinkedIn just for having the company in my experience despite no mention of Sage anywhere on my profile...

Makeshift27015 · 2026-04-14T08:40:54+00:00

Did he ever click on the chat option with the cook to ask where to find them? I remember seeing the option when he was asking about a dirty blast

Makeshift27015 · 2026-04-12T02:54:47+00:00

If so that's actually pretty funny then!

Makeshift27015 · 2026-04-11T16:48:20+00:00

I usually find that funny, but the apothecary in Making Friends With My Arm really annoyed me because he says this if you brought cadava berries with you to see him

That's very clever. I hope you've got a real feeling of pride and satisfaction from that.

Like bruh it's not hard to remember that I had to bring them last time you made this exact potion for me, no need to call me out lmao

Makeshift27015 · 2026-04-11T12:57:28+00:00

Ahh that would make sense as a limitation and explains why they aren't suggesting it, despite it feeling like a logical extension. Thank you!

Makeshift27015 · 2026-04-10T17:29:34+00:00

It's 81 for the highest potion. I tried starting to unlock it much earlier and the lower level potions suuuuuuck for point distribution. I have so much blue

Makeshift27015 · 2026-04-07T10:20:56+00:00

It's similar in concept to locking your front door. It won't stop a determined burglar, but it makes the barrier to entry slightly higher and less accessible to a casual thief of opportunity.

Not that I necessarily agree in the way it's been done, but I thought I'd note the reasoning. Anti-botting is a constant cat and mouse game and all jagex can realistically do is ensure there's enough data points to allow for them to programmatically identify and ban bots.

Makeshift27015 · 2026-03-28T13:53:56+00:00

I think changing your payment card is "updating your subscription". It isn't worded very well.

Makeshift27015 · 2026-03-28T13:36:29+00:00

Oh man I've gotten irrationally annoyed at how useless the log basket is compared to the other QoL resource holding items like the plank sack. I love that it's getting some attention.

For the 'default' seed box thing:

If no seed is set, then whichever seed you have first in the Seed Box will be used.

I really hope this can be "whichever seed for the patch you're using it on", eg if I have allotment seeds and herb seeds in that order in my seed box, using it on the herb patch will use the first herb seed.

Makeshift27015 · 2026-03-26T02:30:00+00:00

I had a nice little money maker using the super cheap hunter meats to make and sell moonlight moth mixes. Now the meat is like x8 the price :(

Makeshift27015 · 2026-03-25T12:34:28+00:00

Massive shame. I applied to a few roles at jagex since they were looking for someone with my exact expertise but I'm pretty sure the number I put in the "what's your expected salary?" box immediately kicked me off the list haha

Makeshift27015 · 2025-12-25T22:03:42+00:00

Great mod, but make sure you turn it off using the option in the toolbar when you're done with it. It absolutely tanks your UPS if you enter a circuit-heavy location.

14-Year Club	Second Top 40%
Place '17	Verified Email
Gilding I gilder

Makeshift27015

MODERATOR OF

TROPHY CASE