AWS Serverless Claim Check Pattern
Claim Check Pattern
A Claim Check Pattern allows you to provide more than a service limit allows.
It does so by utilizing presigned URLs from Amazon S3.
A presigned URL is an URL that has access to some object.
A presigned URL will use the AWS Credentials of the user who created it.
The client uses the URL to update the object.
A presigned URL can be used by anyone who has access to the internet browser.
Because of that, you have to treat the presigned URL as sensitive information.
You should only share it with people who need access to it.
AWS Serverless Claim Check Pattern Video
W3schools.com collaborates with Amazon Web Services to deliver digital training content to our students.
How Claim Check Pattern Works
The client supplies the presigned URL.
The client sets read or write access, along with the URL expiration time.
A Lambda function creates a role or utilizes IAM credentials to access Amazon S3.
Amazon S3 responds with a URL that other parties can use to access the object.
Presigned URL
The client uses the presigned URL to update items in the S3 bucket.
A presigned URL is provided through the workflow as part of the payload.
A payload is a JSON structure that contains data.
It makes the S3 object available to the components that need it.
URL's expiration time depends on the credentials expiration time.
The URL is valid for the duration of the credential's expiration time.
Related reads:
Amazon S3 Developer Guide: Share an Object with Others
