Geoff Baskwill

@geoff_baskwill

Learning daily. He/him. 🇨🇦

Ottawa, Ontario, Canada
Vrijeme pridruživanja: prosinac 2009.
193 fotografije ili videozapisa Fotografije i videozapisi

Tweetovi

Blokirali ste korisnika/cu @geoff_baskwill

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @geoff_baskwill

  1. 2. velj

    Sometimes revisiting the SLOs for a service can help you realize that you’re doing things wrong. Just figured out a redesign so my service doesn’t *have* to be 99.95% available and p99<10ms. 🙃 It might still be, but if it misses consequences will be less.

    1 korisnik označava da mu se sviđa
    Poništi
  2. 1. velj

    Getting back into AWS in earnest, not finding what I’m looking for with (seems mostly limited to hooking up lambdas, docs on direct svc integrations seem nonexistent). Should I look at SAM? Something else?

    5 replies 1 proslijeđeni tweet 7 korisnika označava da im se sviđa
    Poništi
  3. 31. sij

    “You know what we should do? We should break it up. We’re gonna break it up and somehow find the engineering discipline we never had in the first place.” - < 💯🔥

    Poništi
  4. 30. sij

    ICYMI: Awesome talk about things you might not know about AWS API Gateway, thanks for the continuous stream of knowledge bombs.

    5 korisnika označava da im se sviđa
    Poništi
  5. 28. sij

    In today’s todo list: epic breakdown. Hmm. That could have been phrased better.

    Poništi
  6. proslijedio/la je Tweet
    25. sij

    TIL: RFC1925 - The Twelve Networking Truths In particular Truth Seven, "It's Always Something", applies to pretty much every aspect of my tech career. (Not necessarily in a bad way, though.) (via ; Thanks!)

    3 proslijeđena tweeta 9 korisnika označava da im se sviđa
    Poništi
  7. proslijedio/la je Tweet
    25. sij

    (A few) Ops Lessons We All Learn The Hard Way -- a Twitter 🧵:

    68 replies 1.721 proslijeđeni tweet 3.357 korisnika označava da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  8. proslijedio/la je Tweet
    24. sij

    Give me all your apis. I’m ready!

    1 reply 1 proslijeđeni tweet 2 korisnika označavaju da im se sviđa
    Poništi
  9. 25. sij

    🤯 once again raises the bar.

    The Stripe API now makes suggestions in response to misspellings!
    1 korisnik označava da mu se sviđa
    Poništi
  10. 24. sij

    arch diagrammers ... what icon do you use for S3 bucket policy? OAI?

    1 reply
    Poništi
  11. proslijedio/la je Tweet
    22. sij

    I've learned a ton of things from Yan, but this is probably my favorite one. So simple and such a big difference. TL;DR: Set "AWS_NODEJS_CONNECTION_REUSE_ENABLED=1" if you're using the AWS SDK with Node 💥

    ICYMI - Here's a simple and effective performance tip for Lambda - enable HTTP keep-alive! The cost of establishing TCP conn is often greater than the HTTP req itself.
    7 replies 26 proslijeđenih tweetova 89 korisnika označava da im se sviđa
    Poništi
  12. proslijedio/la je Tweet
    19. sij

    The moral of the story is that Y2038 isn't "coming". It's *already here*. Fix your stuff. ⏹️

    12 replies 293 proslijeđena tweeta 1.462 korisnika označavaju da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  13. 20. sij

    This. 1000% this.

    Your org is ready for chaos engineering when you are able to budget your reliability work instead of performing it reactively, and when you have enough observability* to reliably identify the chaos you have injected. *Not monitoring. Raw events and high cardinality are key here
    1 proslijeđeni tweet 1 korisnik označava da mu se sviđa
    Poništi
  14. proslijedio/la je Tweet
    19. sij

    Babies born today will turn 18 on January 19, 2038, the first date when time becomes unrepresentable using a standard 32-bit unsigned Unix timestamp. It's not far off.

    2.558 proslijeđenih tweetova 6.573 korisnika označavaju da im se sviđa
    Poništi
  15. proslijedio/la je Tweet
    19. sij

    Specifically, it would resolve this issue: I should be able to go from any state of the service to any other state in a single stack update. I shouldn't have to plan multiple source commits for operational restrictions like this.

    1 proslijeđeni tweet 9 korisnika označava da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  16. proslijedio/la je Tweet
    17. sij

    "Containers change nothing in your security model... Having said that, if you adopt the philosophy & the tools that come with running containers, you get significantly higher security benefits than a traditional security model." -

    8 proslijeđenih tweetova 27 korisnika označava da im se sviđa
    Poništi
  17. proslijedio/la je Tweet
    17. sij
    Odgovor korisniku/ci

    Hey Aidan - APIGW Engineering here. Thanks for bringing this up. We'll take a closer look, but it does appear that we should respect the "Bearer" prefix per RFC6750.

    1 proslijeđeni tweet 11 korisnika označava da im se sviđa
    Poništi
  18. proslijedio/la je Tweet
    17. sij
    Odgovor korisnicima

    This isn’t just a Cognito problem. Even if API Gateway supports Cognito’s non-standard operation, it needs to support the standard version too, and the fact they overlooked that is disappointing

    1 proslijeđeni tweet 4 korisnika označavaju da im se sviđa
    Poništi
  19. proslijedio/la je Tweet
    5. sij

    I was today-years-old when I learned that you can use the iam:AssociatedResourceArn policy key to limit which resources a role can be passed to. 🤯 I wonder which other resource types this works for?

    7 proslijeđenih tweetova 37 korisnika označava da im se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi
  20. proslijedio/la je Tweet
    3. sij

    For our business AWS accounts, I'd like to set up 3+ MFA devices, any 2+ of which are required for a root login. Managing secure access to a single MFA device is difficult and adds risk to our business.

    6 replies 7 proslijeđenih tweetova 31 korisnik označava da mu se sviđa
    Prikaži ovu nit
    Prikaži ovu nit
    Poništi

@geoff_baskwill još nije objavio nijedan Tweet.

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·