Is there a better solution for assuming an AWS role inside a #kubernetes pod, rather than changing our code to assume the role at runtime? I feel there's got to be something out there. #aws#kubernets#k8s#oidc
We've used a janky initContainer, which drops the assume role credentials into a file which is shared with the main container and changed the entry point to expose the credentials in the environment to the container before. But still feel like there's a better way that im missing
@1Password Hey, is there something up with your downloads section? I am unable to download the CLI tool via the link on your site :( (https://t.co/zWyccpj5do)
About an hour ago, some Signal users experienced delays sending and receiving messages. One small cluster of servers got confused and thought that Sunday was a day of rest for them too. We apologize for the brief inconvenience while everything automatically recovered.
@jd0dd @aws_shd Yes all good thanks Jonathan. Busy as ever! Yup, I'm thinking the RSS feeds from https://t.co/eG5ZdqYLgT is the best place to start. It's just getting alerted on that is providing a little more difficult than I thought :P
How are people being #alerted when #aws is down? I'd like to use something like #RSS feeds to pick which services I care about and have them in #grafana
@jd0dd So I'm looking for something that we can alert on from outside AWS :( (Our monitoring setup is currently running in AWS but that's another problem :P)
@jd0dd Hey Jon, long time no speak. How you doing? Yeah I've got a bit of terraform (https://t.co/qqX14N1r6I) to do something similar (PHD -> CloudWatch -> SNS -> Lambda -> Slack) but I'm a little worried if something in that chain is down, I won't get the alert :( 1/2