(no title)
time0ut | 4 months ago
The biggest miss on our side is that, although we designed a multi-region capable application, we could not run the failover process because our security org migrated us to Identity Center and only put it in us-east-1, hard locking the entire company out of the AWS control plane. By the time we'd gotten the root credentials out of the vault, things were coming back up.
Good reminder that you are only as strong as your weakest link.
SOLAR_FIELDS|4 months ago
citizenpaul|4 months ago
Thats some nice manager deactivating jargon.
jordanb|4 months ago
nahumba|4 months ago
1970-01-01|4 months ago
crote|4 months ago
bcrl|4 months ago
Thankfully none of my 10 Gbps wavelengths were impacted. Oh did I appreciate my aversion to >= layer 2 services in my transport network!
ttul|4 months ago
beefnugs|4 months ago
vladvasiliu|4 months ago
Is it possible to have it in multiple regions? Last I checked, it only accepted one region. You needed to remove it first if you wanted to move it.
raverbashing|4 months ago
AndrewKemendo|4 months ago
I’m unaware of any common and popular distributed IDAM that is reliable
barbazoo|4 months ago
shdjhdfh|4 months ago
ej_campbell|4 months ago
jpollock|4 months ago
We learned that lesson by having to do emergency failovers and having some problems. :)
shawabawa3|4 months ago
i don't think any method of auth was working for accessing the AWS console
kondro|4 months ago
nijave|4 months ago
e.x. https://us-east-2.console.aws.amazon.com/console/home
reenorap|4 months ago
sroussey|4 months ago
hinkley|4 months ago
Who watches the watchers.
ej_campbell|4 months ago
The usability of AWS is so poor.
skywhopper|4 months ago
ct520|4 months ago
ransom1538|4 months ago
ozim|4 months ago
michaelcampbell|4 months ago
ct_list|4 months ago
[deleted]
saltserv|4 months ago
[deleted]