3 ms·

Without going into too much detail, this "coupled account" problem is taken very seriously internally (AWS Identity dev, my opinions are my own and I don't spea

by mabbo 5y ago

Without going into too much detail, this "coupled account" problem is taken very seriously internally (AWS Identity dev, my opinions are my own and I don't speak for the company). There is a very large project to fix this. But as you can probably imagine, with a system this large and complex making changes to fundamentals like identities is hard, and done with a lot of care. All new accounts created today are "decoupled". They are not your Amazon account, and (barring some special internal tools for testing) you cannot make them the same account. But migrating all the existing accounts without causing harm is a messy business. My own AWS account has the same problem.

cj 5y ago
> detail, this "coupled account" problem is taken very seriously internally I can say for certain that no, it is not something taken seriously. I (loudly) complained to AWS enterprise support in 2017, 4 years ago, about this issue. Got escalated as high as could possibly be escalated (team leads of IAM calling my cell phone). 4 years later and the issue is unresolved. This is Amazon we’re talking about. There’s very little that can’t be fixed in 4 years.
mcharezinski 5y ago
Could you please share some of the technical challenges about the migration?
- mabbo 5y ago
  I'm not a spokesperson for the company and really don't feel comfortable saying anything specific about this. Generically: Identity is a very hard space. It's one of those things that sounds really simple but the deeper you go the more edge cases you find. With an complex systems, changing fundamental designs of the system- while users and other systems are currently using that system- is like trying to upgrade the engines on a plane while in flight. Technically possible, with a lot of planning, but any wrong move or bad assumption and you're going to crash.
FridayoLeary 5y ago
Is there work on Amazon.com itself? Because basically everything there needs fixing. But the filters would be a very good place to begin a sorely needed facelift.

by mabbo 5y ago

cj 5y ago

> detail, this "coupled account" problem is taken very seriously internally I can say for certain that no, it is not something taken seriously. I (loudly) complained to AWS enterprise support in 2017, 4 years ago, about this issue. Got escalated as high as could possibly be escalated (team leads of IAM calling my cell phone). 4 years later and the issue is unresolved. This is Amazon we’re talking about. There’s very little that can’t be fixed in 4 years.

mcharezinski 5y ago

Could you please share some of the technical challenges about the migration?

mabbo 5y ago
I'm not a spokesperson for the company and really don't feel comfortable saying anything specific about this. Generically: Identity is a very hard space. It's one of those things that sounds really simple but the deeper you go the more edge cases you find. With an complex systems, changing fundamental designs of the system- while users and other systems are currently using that system- is like trying to upgrade the engines on a plane while in flight. Technically possible, with a lot of planning, but any wrong move or bad assumption and you're going to crash.

FridayoLeary 5y ago

Is there work on Amazon.com itself? Because basically everything there needs fixing. But the filters would be a very good place to begin a sorely needed facelift.