Tweetovi

Blokirali ste korisnika/cu @__steele

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

  1. prije 14 sati

    Personally I'm very much looking forward to HTTP APIs getting parity with REST APIs' friendly support for custom domains in AWS SAM as per the latest release

    Prikaži ovu nit
    Poništi
  2. prije 14 sati

    For those on the edge of their seats, this is what I had wrong. "GatewayDomain" here is an AWS::ApiGatewayV2::DomainName resource. Apparently these domains are different alias targets than the primary domain for the gateway.

    Prikaži ovu nit
    Poništi
  3. prije 14 sati

    Has anyone succeeded in getting a custom domain working with the new AWS HTTP APIs functionality? I keep getting bad SSL certs (i.e. they're not serving my cert) when I try through both CloudFormation and the web console.

    Prikaži ovu nit
    Poništi
  4. 1. velj

    This blog article by made using EC2 instances really easy:

    Prikaži ovu nit
    Poništi
  5. 1. velj

    If I used EC2 instances instead, I could skip the NLBs altogether as Global Accelerator can target ALBs, NLBs, EIPs and EC2. That'd save me 60% on my pet project.

    Prikaži ovu nit
    Poništi
  6. 1. velj

    AWS Global Accelerator and Fargate are both independently very cool and affordable services. But together, the price increases rapidly. Here's the maths on running a hobby project across five regions (because why not?) GA: $20/mo Fargate: $50/mo NLBs: $100/mo

    Prikaži ovu nit
    Poništi
  7. 31. sij

    Would it be useful if you could attach a debugger and step through code on a deployed AWS Lambda function?

    Poništi
  8. 30. sij
    Poništi
  9. 29. sij

    Today is not my day. EC2 ASG in the wizard isn't having much more luck than the spot fleet approach.

    Prikaži ovu nit
    Poništi
  10. 29. sij

    So I decided to go with Fargate for the time being while I work on getting an ASG provided, but there's no Fargate spot capacity provider associated with this brand new ECS cluster (in a brand new account) - and I think I need to drop down to the CLI

    Prikaži ovu nit
    Poništi
  11. 29. sij

    Based on the error, I assume it was a race condition between IAM role creation and the spot fleet creation. I wonder why they didn't just include the IAM roles in the CloudFormation stack?

    Prikaži ovu nit
    Poništi
  12. 29. sij

    I was expecting to go into CloudFormation to debug what happened, but they deleted the stack - trying to destroy the evidence!

    Prikaži ovu nit
    Poništi
  13. 29. sij

    So I tried the ECS cluster creation wizard for the first time, didn't have much luck.

    Prikaži ovu nit
    Poništi
  14. 28. sij

    Step Functions: is there a better way to have a choice state "does this string have this prefix" or do I need to combine StringGreaterThanEquals and StringLessThanEquals?

    Poništi
  15. 28. sij

    To be honest, this is the kind of science I expected from a Research Scientist at . The cloud insights is just a bonus.

    Poništi
  16. 28. sij

    TIL that the council of Bens also knows a lot about JWTs

    Poništi
  17. 28. sij

    Turns out I should understand the subject before saying what is and isn't supported! Thanks to all thread participants for being so patient with me 😅

    Poništi
  18. 28. sij

    As a non-frontend dev, I really appreciate what the ALB does. I just stick everything behind an authentication rule and I'm done: all I need to do is read the user ID header that the ALB injects. The HTTP API approach requires me to write Javascript 😱

    Prikaži ovu nit
    Poništi
  19. 28. sij

    So AWS ALBs and HTTP APIs both support OIDC - yay, easy migration! But it turns out that ALBs support the "authorisation code flow" and HTTP APIs support the "implicit flow". This can require moderate changes to the app. Is it worth it? What are the pros / cons?

    Prikaži ovu nit
    Poništi
  20. 28. sij

    Has anyone used the new OIDC federation support with AWS EKS? Is it possible to use parts of the JWT (e.g. the pod name) as a variable in my trust policy? Docs indicate I can use “app_id” and “user_id” for Facebook and Amazon login — very light on details for generic OIDC

    Poništi

Č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:

    ·