These type of articles make me wanna quit doing anything in IT. It's not a criticism of the author, more the current state of technology in AWS. I'd really like to have just 1 AWS account where I can see and do everything there and not keep switching and think about account IDs or which account has what S3 bucket/server whatever.
An AWS account just for getting into other AWS accounts
81–90 of 109 posts
Re: An AWS account just for getting into other AWS accounts
#82Earlier quoted context omitted.
In the meantime, check out Substrate https://src-bin.com/substrate/ > and don’t worry about waiting for AWS to improve.
Far out - that website looks dodgy as. What on earth is going on with its fonts - it looks like a newspaper vomited onto the screen.
Re: An AWS account just for getting into other AWS accounts
#83Earlier quoted context omitted.
In the meantime, check out Substrate https://src-bin.com/substrate/ > and don’t worry about waiting for AWS to improve.
Far out - that website looks dodgy as. What on earth is going on with its fonts - it looks like a newspaper vomited onto the screen.
Re: An AWS account just for getting into other AWS accounts
#84What 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.
Python, multiprocessing and boto3 with assume role. 1000+ accounts takes a few minutes.
Re: An AWS account just for getting into other AWS accounts
#85Earlier quoted context omitted.
> There aren‘t any DMs on Hacker News 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.
> , there's nothing good about snippy public comments. It didn't seem snippy to me. "Why aren't you disclosing your ties" would be IMO. The message that was actually posted seemed quite diplomatic.
Turns out it is more diplomatic to reach out to someone privately first. God forbid we set a better example than the one being set.
Re: An AWS account just for getting into other AWS accounts
#86Earlier quoted context omitted.
> There aren‘t any DMs on Hacker News 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.
> Good thing they... (checks notes) ...know exactly who made the post and can reach out to them on LinkedIn or email them. Which I wouldn’t see. I’m glad they posted the comment.
Re: An AWS account just for getting into other AWS accounts
#87Earlier quoted context omitted.
"1500 AWS accounts" You just blew my mind. We have two accounts and it gets messy sometimes.
Messy? Isn't one of the points of having multiple accounts to reduce mess?
I use Firefox for the prod console and Chrome for the test console. Obviously that system doesn't scale past 3-4 accounts. ;)
Re: An AWS account just for getting into other AWS accounts
#88These type of articles make me wanna quit doing anything in IT. It's not a criticism of the author, more the current state of technology in AWS. I'd really like to have just 1 AWS account where I can see and do everything there and not keep switching and think about account IDs or which account has what S3 bucket/server whatever.
The really frustrating things is that while AWS make the "Account" their best isolation layer they make managing those accounts with their tooling absolutely awful.
Re: An AWS account just for getting into other AWS accounts
#89Earlier quoted context omitted.
> , there's nothing good about snippy public comments. It didn't seem snippy to me. "Why aren't you disclosing your ties" would be IMO. The message that was actually posted seemed quite diplomatic.
> seemed quite diplomatic Turns out it is more diplomatic to reach out to someone privately first. God forbid we set a better example than the one being set.
Why
Re: An AWS account just for getting into other AWS accounts
#90These type of articles make me wanna quit doing anything in IT. It's not a criticism of the author, more the current state of technology in AWS. I'd really like to have just 1 AWS account where I can see and do everything there and not keep switching and think about account IDs or which account has what S3 bucket/server whatever.
With everything in one account someone might accidentally destroy your production environment. That'll be awkward to explain. And with IAC, it could be as simple as one change to a VPC config that recreates instead of updates the VPC.
In normal IT (not Twitter) you usually have a production and test environment at least. The inconvenience more than makes up for accidentally destroying something in production. And before you say anything, if you haven't done that you haven't been in IT for long enough.
However, if you want to do it your way you should become the director and make it that way. You'll be sorry, but that'll be on your head.
I'm not sure if that's possible, but I haven't checked.