Dave Rahardja on Nostr: nprofile1q…ynrtg It’s not particular to Substack; it’s a feature of AWS. ...
nprofile1qy2hwumn8ghj7un9d3shjtnddaehgu3wwp6kyqpqpv5ug6gxy7fet6rltce6hkxksw599v3rnwut0wdc8c5v09k6qraqdynrtg (nprofile…nrtg) It’s not particular to Substack; it’s a feature of AWS.
Basically, the AWS S3 servers allow you to lock down your bucket contents such that only approved identities (known only to the developers) can access its contents. To grant temporary access to people, a computer that has access to an identity’s secret key can sign a request and send it to a customer in the form of that super-long URL you see. Accessing that URL requests the file from S3, which then validates the signature, and grants you access to the file only if the signature can be verified to belong to an approved identity.
Other cloud storage servers like Google and MS Azure offer similar functionality.
Basically, the AWS S3 servers allow you to lock down your bucket contents such that only approved identities (known only to the developers) can access its contents. To grant temporary access to people, a computer that has access to an identity’s secret key can sign a request and send it to a customer in the form of that super-long URL you see. Accessing that URL requests the file from S3, which then validates the signature, and grants you access to the file only if the signature can be verified to belong to an approved identity.
Other cloud storage servers like Google and MS Azure offer similar functionality.