Earlier quoted context omitted.
I'm assuming you're saying a dedicated account for Google Workspace (GSuite) and a separate account for anything GCP?
Yeah, that's what I'm saying. There's a lot of overlap with people who are using GSuite for things like email and people who are using GCP for production systems. It isn't great that the login/2FA for email automatically give access to GCP. Email is used so often, it's hard to be as cautious with it all the time as one can be with a something used less often.
An AWS account just for getting into other AWS accounts
51–60 of 109 posts
Re: An AWS account just for getting into other AWS accounts
#52Earlier quoted context omitted.
Kind of .. I think it's good that people are encouraged to disclose their interests on HN as a matter of course.
A DM is reasonable. Calling someone out in public like that is childish.
Re: An AWS account just for getting into other AWS accounts
#53> If you wish to provide access via SSH… Don’t do this. I can’t think of a single reason that anyone ever needs to SSH directly into a server on AWS in 2022. Use System Manager Session Manager https://docs.aws.amazon.com/systems-manager/latest/userguide... Short explanation: it allows you to access a Linux instance via SSH using SSM as an IAM controlled proxy or use RDP for Windows. You don’t need ingress access to y…
A lot of us are busy solving business needs in smaller companies/startups and don't have the time nor expertise to learn every single AWS service and come up with a justification for utilizing it.
ControlTower for example. Takes about 30 mins to setup on normal AWS (on GovCloud it was much more complicated, took me half a day). But then setting up new accounts is one click and it’s preconfigured with correct restrictions and security measures, which individually would take several hours per account to do without controltower. So it’s an easy savings from the beginning. The only real cost is the cost of AWS config. So if you’re using that already (for SecurityHub for example) then it’s nothing additional.
IAM Identity Center makes user management not only more secure but faster and easier. It will take half a day to maybe a full day to setup the first time. But now every new user will be a few clicks with access across multiple AWS accounts. You can remove them in one click across all accounts. So these are just really simple additions to your workflow that save you time and improve security.
SSM is another example. It’s adding a policy to your instance role and checking a box (or adding a flag in Terraform or CLI) and it’s enabled. It’s no additional cost. It saves you time because you don’t need to manage user accounts on the server anymore (they are managed broadly through IAM or PermissionSets). No more copying around SSH keys or rotating them when people leave. It improves security and saves you time.
There’s little (if any at all) downside to any of these things. It’s all upside. For the most part, these don’t even have any significant costs associated with them. They are generally provided for free where you’re only cost is the underlying resources that you’re managing, which of course your paying for regardless.
Re: An AWS account just for getting into other AWS accounts
#54Earlier quoted context omitted.
A lot of us are busy solving business needs in smaller companies/startups and don't have the time nor expertise to learn every single AWS service and come up with a justification for utilizing it.
A lot of these tools actually make your life easier and faster in the long run. ControlTower for example. Takes about 30 mins to setup on normal AWS (on GovCloud it was much more complicated, took me half a day). But then setting up new accounts is one click and it’s preconfigured with correct restrictions and security measures, which individually would take several hours per account to do without controltower. So it…
Not to mention the quality of life on this tool is incredible. When you truly have tens or hundreds of AWS accounts, the SSO tool makes it so nice to jump between them as an actual user. And I’m actually a huge fan of the CLI integration to get CLI access to any of them with a simple command on the AWS CLI. It’s super slick and will save you probably 5 hours the first week you use it.
We started using it a year ago and it’s been a game changer at our organization. As a user I don’t ever want to go back to normal IAM. Such a pain.
Re: An AWS account just for getting into other AWS accounts
#55Earlier quoted context omitted.
What a weird comment.
Kind of .. I think it's good that people are encouraged to disclose their interests on HN as a matter of course.
That’s not to say his opinion is not wanted, just that the potential bias should be made transparent.
Re: An AWS account just for getting into other AWS accounts
#56Earlier quoted context omitted.
A DM is reasonable. Calling someone out in public like that is childish.
There aren‘t any DMs on Hacker News, and if he didn’t post that comment I would have thought it was a disinterested commenter recommending something they had used, not somebody who works on the project. The cultural norm here is to disclose when you are recommending your own product and it’s not childish to point out when people fail to do that, it’s reinforcing that cultural norm.
Good thing they... (checks notes) ...know exactly who made the post and can reach out to them on LinkedIn or email them.
Cultural norms are reinforced by good examples, there's nothing good about snippy public comments. Reaching out to them privately isn't hard, and, dare I say it: is more inclusive. I don't think I need to explain the origin of the word assume.
Re: An AWS account just for getting into other AWS accounts
#57Earlier quoted context omitted.
Kind of .. I think it's good that people are encouraged to disclose their interests on HN as a matter of course.
If they had disclosed their involvement in their profile at least I could give them the benefit of the doubt but in this case, like the other commenters, I assumed he had used the tool as a customer and had a positive experience, not that he was literally the founder of the group making the tool. That’s not to say his opinion is not wanted, just that the potential bias should be made transparent.
You're bikeshedding.
Re: An AWS account just for getting into other AWS accounts
#58Earlier quoted context omitted.
Mr. Crowley, did you forget to mention / disclose your association and financial interest tied to this product? For context, https://www.linkedin.com/in/richarddcrowley indicates he works there.
What a weird comment.
It gives me a bit more confidence that I can trust what people recommend here and isn't just hidden marketing.
Re: An AWS account just for getting into other AWS accounts
#59https://aws.amazon.com/controltower/ If we all started using Control Tower perhaps they'd get funded enough to continue to build it out and make it awesome.
In the meantime, check out Substrate https://src-bin.com/substrate/ > and don’t worry about waiting for AWS to improve.
Re: An AWS account just for getting into other AWS accounts
#60What tool do people here use to search across AWS accounts? Disclaimer: we are building a search engine to search for resources across “workspaces”. In AWS, this unit is the Account. In GCP, this unit is the Project.
CloudHealth. 1500 AWS accounts, it does the job well enough
You just blew my mind. We have two accounts and it gets messy sometimes.