3 years ago

Category: Kubernetes, firewall

So you log in to your AWS console with your two scripts, one to log in with your OTA and another one to assume a role. Then you separately log in to the console (again!) and then assume another role which should be easy cause it should be part of the history, as you did this before.

You try to log in to the VPN but something is wrong and it keeps denying you access, after twenty attempts you realise your password, which is managed by a third party SAML authenticator has expired, so you go and change that and you finally manage to log in to your VPN. You try and ssh into the server only to realise that the key pair that was used when this server was provisioned is not in your hands, and you need to find the person who can either do this or have him send you the key in Signal Messenger or with Keybase.

You manage to track the person down after half an hour and they amend the configuration (while in the meantime you just killed their flow of work) and then you can happily go and see all your changes taking effect and your new service in action, however your colleague in a different team tells you that this service also needs to connect to yet another service, and this is not happening.