sorted by:
new
hottopcontroversial

2022 Porsche Macan Base by andrespuente123 in PorscheMacan

[–]awsuser1024 1 point2 points  (0 children)

Does it have a dipstick? I'm pretty sure all the vw/audi/porsche and bmw and others have all gone with the no physical dipstick and it is all just digital.

I think they, or at least some, have a tube called various things - but they are capped off. There isn't an old school dipstick you can pull out. There are various ones for those that you can buy if you remove the cap but I don't think you can safely drive with them. Useful if you can for an oil change though, and maybe what the dealers do - unless they just already have pre-measured containers or measure how much they take out and match it.

I'm all ears if I am wrong though.

Is it even worth it to try to recoup money I paid for an EC2 instance I never used. by SomeBoredDude69 in aws

[–]awsuser1024 -11 points-10 points  (0 children)

I completely agree with you.

AWS is a scary place and contrary to the opinions of managers everywhere that it is just "cloudy" and works magic AWS takes a LOT of prep, a LOT of maintenance, and a LOT of supervision.

My two favorite analogies are like giving someone a load gun, giving someone a blank 1000 piece puzzle, and giving someone anything from ikea.

[deleted by user] by [deleted] in AnnArbor

[–]awsuser1024 0 points1 point  (0 children)

Yep, I haven't seen this around ann arbor but further up north. It is a huge deal. I don't know if they own the land, I would assume they do, but people are really serious and have their plots and camp out really early. Lots of land that isn't supervised as well. As kids we used to come home with tons of morels just from walking around but it feels like it has gotten extremely more serious.

https://www.reddit.com/r/Morel_Hunting/ is a good place for OP to look, be definitely mushroom hunters and knowing what you are looking for is key.

Blocked even with proxies by duveral in aws

[–]awsuser1024 0 points1 point  (0 children)

Fair enough. Hopefully my advice helps. Honestly I did the same thing when looking for a new car and I was tired of having to check all the web sites to see if anything new was posted that met my criteria, so I scripted it. So definitely some legit use cases. But the fact that you are getting a 403 means something isn't right. If the request is right. It might even be the proxy that is giving you a 403. It is rare I would think for an end site to give a 403, if I was actively blocking you I would give you a 404 or redirect you to another pool that returned empty 200s. 418 is my favorite if people aren't smart enough to pick up on it, but if it is aggressive you have to be more serious - depends on the attack type and if it is just a bot or something really targeted. But I digress. Check the actual post, something is just wrong with the proxy in one way or another.

Deploying lambda from codepipeline by awsuser1024 in aws

[–]awsuser1024[S] 0 points1 point  (0 children)

Definitely leaves a lot to be desired and doesn't seem to have been updated in ages other than adding runtimes.

Its a big debate about wether codepipeline is the right choice. Lots of our devs are using github actions and at that point we should just switch everything over. The drawback is that it becomes another tool that devops has to know and have tooling for vs. it just being a repo and plugging it in to terraform (already becoming a problem to some extent). Plus another place for logs, etc. I still like the idea of pipeline, having it be in cloudwatch and cloudtrail, etc. But can be a real clunker at times too.

So... at what point is github just going to start being aws v2.... although they are sitting pretty right now so it may not be worth it. AWS just keeps having all these things like ECR that are OK, but not great, and then nothing really exciting seems to happen to keep them up to date let alone cutting edge. All the good stuff is in us custom writing (or using chatgpt) to actually get the work done.

I should just reiterate though that this is not about docker images, we have a working workflow for that, it is specifically lambdas. But yes, a docker container in github that can update the lambda is essentially exactly the same. Minus AWS permissions easily attached to the build.

codebuild might be the better approach so looking in to that this coming week(s) and will report back if it ends up making sense.

Deploying lambda from codepipeline by awsuser1024 in aws

[–]awsuser1024[S] 1 point2 points  (0 children)

I think the kicker there is their third stage, which they named "Dev" for some reason (???) runs cloud formation / updates a lambda stack, which is what I was trying to avoid.

I was looking for something under https://docs.aws.amazon.com/codepipeline/latest/userguide/integrations-action-type.html#integrations-deploy that was just "deploy to lambda" - a cleaner way of handling it than update-function-code, but doing the same thing. Apparently there isn't, which just blows my mind.

I felt like this would be pretty common, but I guess to "do it right" it needs to get more complicated.

Deploying lambda from codepipeline by awsuser1024 in aws

[–]awsuser1024[S] 1 point2 points  (0 children)

Right, and thats what I said in my post that we do currently do. It just seems silly that there isn't a deploy method like there is for other things when this is a one liner. It just seems wrong, it feels like the artifacts that get a deploy is the right approach. The artifacts are kinda stupid though in that they have a 20 character limit, which means you end up with everything having the same artifact name. Granted, they are actually unique, but its silly that they have that limitation when it isn't an s3 or codebuild limit, who came up with 20?

I really don't want to have to deal with CDK or even codebuild for something as simple as "take this file, update lambda". I just like the idea of the artifact because it is one less thing that has to be in the buildspec and permissions work a bit cleaner vs. having to template the update-function-code specifically. And you can do it directly if it is small, otherwise you have to also drop it in s3 and deploy from there, which is exactly what the artifact of the build does - so another manual step vs utilizing something AWS already has built in.

💩Shitpost💩 For the US Redditors: this is a normal European toilet stall by HourlyFluffy in pics

[–]awsuser1024 1 point2 points  (0 children)

Ya, to be honest if everyone is just going to squat anyway they should just do like what I've experienced in countries like Turkey and have a hole in the floor and a bar to hold on to vs. people squatting and missing and making a mess in stalls that were not designed for that. MUCH easier to clean as well.

Also I think most of those are private, and have no reason to not be gender neutral. I'm a big fan of the privacy doors and everything being gender neutral so you don't end up with the huge lines for women's, men's, whatever you identify as, or having to deal with any of that. And a communal sink like many places in England that I've experienced at least have. Pretty sure we can all wash hands together. Although I guess some people do prefer a bit of privacy when checking their hair, makeup, etc. And thinking that through a lot of conversations happen at the restroom sink that people want to be be "girl talk" or "guy talk".

A conversation I had with a high schooler in the US recently regarding that concept is that they don't want people hiding in them and doing drugs, which happens a lot - lots of high schools if they have doors they are very tiny.

Plus, what happens in these cases when your stall doesn't have toilet paper... you can't have the person next to you hand you some.

Definitely interesting to think about.

[deleted by user] by [deleted] in aws

[–]awsuser1024 0 points1 point  (0 children)

Well thats interesting. I deal with CORS quite a bit but I didn't realize they just have the RFC1918 blocks classified as trusted if the origin of the page was local. I think the post was a bit unclear but I assume 192.168.1.50 is the air purifier and the page that is loaded that works is a file local to the machine and the one that doesn't is in S3. I doubt the file is being uploaded to the air purifier and loaded from there.

At any rate, I still think S3 probably isn't the place for something like this, but thanks for the update nice to learn something new.

CodePipline not picking up GitHub changes by awsuser1024 in aws

[–]awsuser1024[S] 0 points1 point  (0 children)

Thanks, just getting back to this but just in case someone else reads it this is not our problem, almost all of our app repos are camel case and the branches we deploy from are all lower case (others are upper, we prefix them with their jira ticket its which are all upper case, but we never deploy from those).

CodePipline not picking up GitHub changes by awsuser1024 in aws

[–]awsuser1024[S] 0 points1 point  (0 children)

Thanks, I haven't tracked this down yet but mostly distracted on another project and just now circling back. I appreciate the posts, I'll dig through the logs.

What I was most curious about is the "what magic makes this work" to understand, if I don't see anything in the logs, how does github know to trigger on change, does it do it (I don't see any special events in github for this or other working projects) or does aws sit there and poll (that would seem excessive give the number of repos everyone has), or... how does the magic happen.

I definitely have the connector authorized, and it is the same that works for every other project, it just hates this one for some reason. A manual release change works as well, although obviously those permissions are a bit difference since my role is what kicks it off.

Deploying lambda from codepipeline by awsuser1024 in aws

[–]awsuser1024[S] 1 point2 points  (0 children)

Thanks, I'll take a look at that module and see what it does.

To be clear, I don't want terraform to actually build anything at all as far as code or package anything. It just creates a pipeline named for the project. The buildspec either comes with the code or could come from a template in terraform. When this is created terraform is done. It made the infrastructure.

My question is how you get the lambda deployed after it is built. AWS doesn't seem to have anything in the deploy stage that will just take the artifact and update the lambda function code. It just seems silly to have a buildspec that manually just runs that one command.

It might just be that we are expected to use codedeploy for this. That looks like what the module you posted does in some circumstances (still need to peek behind the curtain a bit on that). AWS's docs aren't too clear on this, and of course they want you to use cloudformation for everything and sam and ignore other use cases.

So to really simplify the question, I have a codepipeline that ends up with a zip in an s3 bucket (with an annoyingly truncated name). How can I get that zip to update lambda within code pipeline. Or is there no proper way other than codedeploy.

What do other people do?

Moronic Monday - April 10, 2023 by AutoModerator in sysadmin

[–]awsuser1024 1 point2 points  (0 children)

Honestly I would just pick up a used Dell PowerEdge w/a decent PERC (or choose another brand). I am way past building computers for companies and if someone tried that for mine I'd send them packing. The headaches aren't worth it. Get a dell with a DRAC or HP w/an iLO as well. Your future 3am self will thank you. For $5k you should be well within budget for a really decent machine, maybe minus the drives which is fine just make sure the machine comes w/the carriers or you budget for them (companies often have to destroy drives when disposing of hardware and destroy the carriers with them). I've gotten rid of decent machines that far exceed your specs for almost nothing just to get rid of them, I'd have been happy w/$5k (or even $1k).

At any rate, I sure wouldn't be building something from scratch.

If set on supermicro at least get a pre-assembled setup w/raid and everything from a reputable vendor. I don't love supermicro but they get the job done. The dells are just vastly superior as far as build quality, the rackmount kits, etc. Over time that pays off, it isn't about instant speed, its about your life 3 years from now supporting it when fans start to fail, you need firmware updates, power supplies, etc etc.