CDK has a new(ish) feature called hotswap that also bypasses CloudFormation and makes deploys faster.
789 karma · joined September 26, 2023
CDK has a new(ish) feature called hotswap that also bypasses CloudFormation and makes deploys faster.
A lot of web apps are just boring CRUD APIs. The business logic behind these is nothing special. The differentiating factor for a lot of them is how they scale, or how they integrate with other applications, or their performance, or how fast they are to iterate on, etc. The “machine” offers a lot of possibilities these days that can be taken advantage of, so customizing “the machine” to get what you need out of it is a big focus for many devs.
I don’t follow this. Complexity is what leads to vulnerabilities. Reducing complexity by reusing the same, known code is better for security and for compliance. As a security person, if a team came to me and said they were reusing the same container in both contexts rather than creating a new code base, I would say “hell yeah, less work for all of us”.
There are other reasons why using the same container in both contexts might not be great (see other comments in this thread), but security and compliance aren’t at the top of my list at all (at least not for the reasons you listed).
Even the 5x dev who teaches just 2 others to be 5x devs is more impactful than the lone 10x dev that ignores their team, and always will be.
I’m curious what other companies you’re thinking of when you say “like many others”, because all of the ones I can think of have moved significant parts of their operations to Texas.
And yes, other states have this problem as well. See https://poweroutage.us/about/majorevents.
No they aren’t. They’re often repeated, but they aren’t true.
Texas had a catastrophic “grid failure” in 2021. It hasn’t had any actual issues since. There have been no power outages due to “grid failure” since that one event. The past couple winters and summers have seen several situations where the grid operators have issued warnings, but these warnings are completely normal and are part of the process to inform power producers to not go offline, etc. In software terms, it’s basically the equivalent of “it’s going to be a busy day today, try to avoid doing any deployments to prod unless they’re really necessary”.
Just like the train derailments last year, and the airplane issues this year, the media loves to use the fervor around a single bad event to then create big headlines about every similar event.
Back to the software example, imagine if every big shopping holiday there was an CNN headline of “Amazon told its developers they cannot deploy to prod today. Amazon is worried about an outage!!” And because the layperson doesn’t know any better, they fall for it. But in reality, it was business as usual.
Snowflake is susceptible to their SE’s having credentials stolen. These credentials can bypass MFA. And per the article, they have no expiry. That’s strikes one, two, and three.
Snowflake’s security practices lead to a situation where their customers are either required, or at minimum encouraged, to share access to broad datasets with Snowflake employees. That’s strike four.
Yes, there is also issue here that the customers are responsible themselves for not granting too broad access, and that’s on them. But it’s also on Snowflake for not having a better system that doesn’t require this access, or at minimum not having better oversight and control over this transitive access.
Once these accounts are granted access to a customer’s data, they aren’t “demo accounts” anymore. They’re real accounts, with real, very valuable data, and they should be treated as such.
Edit to add: it is worth noting that Snowflake claims the demo account did not have access to customer data and wasn’t the source of the leak, which is in contradiction with what the attackers claim.
Admittedly I don’t have much experience with Snowflake, but as a baseline I expect better from a “cloud storage giant”.
This hail was bigger than 5 inches, so NWS needed a new term for it per their estimation guidelines.
I’ve been involved in a few huge, greenfield projects that were mostly building new things from the ground up. There was an air of “true” building around. But it was astonishing how quickly that faded away. It took less than a year after our first launch for a lot of people to start leaving the team, citing reasons like their job was now just drudgery maintenance work or small feature adjustments, which is definitely less attractive and inspiring.
And that is reinforced by career paths as well. See: the trope about Google promotions based on new launches, not bugs fixed. And people definitely idolize “the engineer that built Linux” more than “the engineer that has patched 1000 linux bugs”.
> The legislation was intended to strengthen the ability of law enforcement agencies to investigate and prosecute cases of domestic violence, sexual assault, trafficking of noncitizens and other crimes, while also protecting victims of crimes who have suffered substantial mental or physical abuse due to the crime and are willing to help law enforcement authorities in the investigation or prosecution of the criminal activity.
This effectively makes it impossible to do what you’re saying. It sucks.
I don’t know exactly what you meant by “our demographic”, but I’m a frequent reader of HN, work in tech, and generally stay up to date with all things tech, and yet… I don’t know if a single person that doesn’t still use Google as their go-to place for information. Before this comment I had never even heard of Perplexity or You.com. /shrug
I’d be blown away if a full recall of the cybertruck wasn’t top headline news.
This team sounds interesting but I get the feeling the WSJ is trying hard to make it seem like some sort of clandestine spy operation. This practice isn’t uncommon… I’ve worked at airlines and they sometimes have people fly on a competitor airline and they don’t broadcast broadly “hey united flight attendant!! I work at American Airlines!” but it isn’t because they’re trying to be a spy.
The subsidiary is literally called “big river” (Amazon is a big river), the employees of Big River listed amazon as their employer on LinkedIn, and it took a simple google search to see the owner of Big River was Amazon… they weren’t exactly trying hard to hide it. A spy operation this was not.
There’s a pic of it here: https://www.twz.com/40859/the-case-for-stripping-the-p-8-pos...
(I have no opinion or endorsement of the other content in that site, just merely was looking for a picture)
However in my experience in a big org, #1 happens frequently enough where it basically would be needed at all times, and would need a security person (or entire team) dedicated solely to that purpose. And sadly in my experience, companies are not willing to spend the money, or able to hire enough security people, to have that level of a dedicated security concierge for every team that needs it.
You can’t rely on that as a fix though, because it’s inherently reactive, when what you really want is proactive protections. By the time you get paged about a breach, it’s already too late.
Honestly, 1 week sounds totally reasonable to me. If you’re at the point where you need an answer immediately or it’s going to delay your timelines, then you didn’t plan your timelines very well, or you waited too long to engage your security team. You have to keep in mind that while you might be laser-focused on your app and think it’s the highest priority, your security team is likely dealing with hundreds of apps, each of which all claim to be the highest priority. Triaging has to happen, and it doesn’t always go in your favor. It really sucks for everyone involved, but I don’t see a good fix for it.
The sweet spot is empowering teams to make most security decisions on their own so the capacity of security people can be spent more wisely and development teams don’t have to wait for an answer except for in very rare cases, but the pessimist in me thinks we’re already too far behind on this and technology (and the opportunity for new security dangers to arise) moves too fast for us to ever catch up.
Data engineering teams need at least part of their team to be designated software or systems engineers that are experts in stuff like how to create a robust cloud environment. This is not only beneficial for security, but also for cost optimization, performance, operations, etc! It drives me crazy when I see a data engineer or marketing team told they have to fend for themselves when trying to figure out how to build a cloud environment.
They inherently desire to work with the company’s Crown Jewels of data. They want unfettered access to, and want to give other people access to, an entire data warehouse of some of our company’s most sensitive customer information. And when it comes to securing it properly, they often do not have the same engineering capabilities as software teams.
Even my friend who lives in rural nowhere is one of those people who in the past has raved to me about how they order everything from Amazon because it’s even faster than going to the store. Parts of my family live about 3 hours from the closest big city and they still love Amazon as well.
There’s definitely got to be a geographic proximity factor to it and I’m definitely not saying your anecdote is invalid, but I find it very interesting that I’ve literally _never_ heard anyone in real life complain about Amazon shipping times, while I see it frequently on HN, to the point where if you only read HN you might think it was the majority viewpoint.