For teams that are scaling like our team, I have t...
# randomd
Dennis Dang
10/11/2021, 9:37 PMFor teams that are scaling like our team, I have to say that AWS's search UI in their console is totally abysmal. They're all implemented differently, and pagination and searching seems to be done client side.
We have at minimum 2000 lambdas in between all our devs and live envs. Phew! Pretty interesting problem to solve later.
a
Adrián Mouly
10/11/2021, 9:37 PMDid you check IaQ?
Adrián Mouly
10/11/2021, 9:37 PMInfra as query?
Adrián Mouly
10/11/2021, 9:38 PMI agree Console is a pain.
Adrián Mouly
10/11/2021, 9:38 PMAdrián Mouly
10/11/2021, 9:38 PMAdrián Mouly
10/11/2021, 9:38 PMI think this can work for you.
Adrián Mouly
10/11/2021, 9:39 PMApparenlty cloudQuery is down, but I’ve used this code:
https://github.com/cloudquery/cloudquery
Adrián Mouly
10/11/2021, 9:39 PMI’ve been able to query AWS from a SQL console, way better.
Adrián Mouly
10/11/2021, 9:39 PMMaybe you can build some queries and share with your team.
Adrián Mouly
10/11/2021, 9:40 PMThat can prevent also from people to modify AWS resources from Console, which is manual and not wanted.
g
Garret Harp
10/11/2021, 9:44 PMI would recommend setting up AWS organizations and AWS SSO giving each dev their own AWS account and each stage its own account. If you do have tons of functions in your app even whenever its only one stage deployed on the account it will still be somewhat an issue but it wont be as big an issue.
a
Adrián Mouly
10/11/2021, 9:44 PMI agree with that too.
d
Dennis Dang
10/12/2021, 2:59 PM@Adrián Mouly IaQ is very cool! This is my first time seeing such a thing.
Dennis Dang
10/12/2021, 3:00 PM@Garret Harp Great advice. We're moving towards that direction, putting all devs into one account. We hadn't considered spending more time to setup an aws account per dev, but that may be worth it.
Dennis Dang
10/12/2021, 3:00 PMthanks everyone