AWS Built a Security Tool. It Introduced a Security Risk
token.security
AWS Built a Security Tool. It Introduced a Security Risk
1–10 of 85 posts
Re: AWS Built a Security Tool. It Introduced a Security Risk
#2[dead]
Re: AWS Built a Security Tool. It Introduced a Security Risk
#3Someone invented the two-sentence clickline. Now even blogs do it.
Re: AWS Built a Security Tool. It Introduced a Security Risk
#4Someone invented the two-sentence clickline. Now even blogs do it.
Are HackerNews Comments the Next Victim of this Crazy Trend?
Re: AWS Built a Security Tool. It Introduced a Security Risk
#5As an AWS-focused practitioner, I started doing Google Cloud training and it blew my mind when I found out that the multiple account sub-account mess that AWS continues to use just doesn’t exist there. GCP sensibly uses a folder and project system that provides a lot of flexibility and IAM control.
It also blew my mind that Google Cloud VPCs and autoscaling groups are global, so that you don’t have to jump through hoops and use the Global Accelerator service to architect a global application.
After learning just those two things I’m downright shocked that Google is still in 3rd place in this market. AWS could really use a refactor at this point.
Re: AWS Built a Security Tool. It Introduced a Security Risk
#6Re: AWS Built a Security Tool. It Introduced a Security Risk
#7This so called “security risk” is a role in a nonprod that can list metadata about things in your production accounts. It can list secret names, list bucket names, list policy names, and similar.
Listing metadata is hardly a security issue. The entire reason these List* APIs are distinct from Get* APIs is that they don’t give you access to the object itself, just metadata. And if you’re storing secret information in your bucket names, you have bigger problems.
Re: AWS Built a Security Tool. It Introduced a Security Risk
#8As an AWS-focused practitioner, I started doing Google Cloud training and it blew my mind when I found out that the multiple account sub-account mess that AWS continues to use just doesn’t exist there. GCP sensibly uses a folder and project system that provides a lot of flexibility and IAM control. It also blew my mind that Google Cloud VPCs and autoscaling groups are global, so that you don’t have to jump through ho…
I think Google scares a lot of people away with their approach of not being able to talk to any human whatsoever unless you spend a lot of money on a monthly basis.
I read a lot of horror stories of people getting in troubles with GCP and not being able to talk to a human person, whereas you would get access to some human presence with AWS.
Things might have been changed, but I guess a lot of people have still this in the back of their mind.
Re: AWS Built a Security Tool. It Introduced a Security Risk
#9As an AWS-focused practitioner, I started doing Google Cloud training and it blew my mind when I found out that the multiple account sub-account mess that AWS continues to use just doesn’t exist there. GCP sensibly uses a folder and project system that provides a lot of flexibility and IAM control. It also blew my mind that Google Cloud VPCs and autoscaling groups are global, so that you don’t have to jump through ho…
One of the stand-out things at AWS Summit London was the number of talks basically saying:
"Yes accounts is a mess but they're what we have".
Re: AWS Built a Security Tool. It Introduced a Security Risk
#10The link is ironically blocked by my companies security suite.