Practise the standard verbs for issuing AWS S3 presigned URLs safely.
0 / 5 completed
1 / 5
Fill in: 'We ___ a presigned URL server-side so a client can upload directly to S3 without ever holding our AWS credentials.'
We 'generate a URL' — the standard, established S3 collocation for creating a temporary signed link. The other options aren't the recognised term here.
2 / 5
Fill in: 'Setting no expiry on a presigned URL can ___ a link that was meant to last minutes still usable weeks later.'
We say a missing expiry will 'leave' a URL usable indefinitely — the standard, natural collocation here. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ a short expiry window on every presigned URL so a leaked link is only exploitable for a few minutes.'
We 'set a window' — the standard, simple collocation for configuring a time-limited validity period. The other options are less idiomatic here.
4 / 5
Fill in: 'We ___ the upload's content type and size in the signature so a presigned URL can't be reused to upload something else entirely.'
We 'restrict' a parameter — the standard, established collocation for constraining what a signed request can be used for. The other options aren't the recognised term here.
5 / 5
Fill in: 'We ___ every presigned URL issuance in an audit log so a suspicious spike in generated links gets flagged quickly.'
We 'log' an event — the standard, simple collocation for recording an action for later inspection. The other options are less idiomatic here.