3 ms·

Very pleased by this addition! :-) Note that it creates special .on.aws URLs so if you want to use your own domain to future proof the endpoint (against linkrot

Very pleased by this addition! :-) Note that it creates special .on.aws URLs so if you want to use your own domain to future proof the endpoint (against linkrot if you ever leave AWS, say) you'll want to set up a redirect/proxy for yourself (whereas API Gateway does custom domains). Also an interesting note from the docs about how said URL is generated: "Because this process is deterministic, it may be possible for anyone to retrieve your account ID from the <url-id>." I don't know how much of a problem this could be, but it's worth being aware of.

taf2 5y ago
should be able to add these as origin's behind cloudfront since it support multiple origins... /lambda/* could be routed to your functions /* everything else your main app
alexhf 5y ago
In my opinion, AWS account IDs are not sensitive information.
- otterley 5y ago
  Nor does AWS believe so: https://www.lastweekinaws.com/blog/are-aws-account-ids-sensitive-information/ https://www.lastweekinaws.com/blog/are-aws-account-ids-sensi...
- chc 5y ago
  Yeah, account IDs aren't actually publicly listed, but should be treated as such. No part of your security should rest on an AWS account ID staying secret.
  - sorry_outta_gas 5y ago
    they are useful for social engineering and phishing
    - bikingbismuth 5y ago
      To be fair, what isn’t?
      - endofreach 5y ago
        You better don‘t have a name, my friend!
        pantulis 5y ago
        Well he is bikingbismuth. He's doing things right here ;)
spyspy 5y ago
I believe this is why GCP added random hashes to their Cloud Run URLs whereas AppeEngine gave you a deterministic one e.g. https://{serviceID}-dot-{projectID}.appspot.com https://{serviceID}-dot-{projectID}.appspot.com