CloudFront Signed URL Generator
Generate signed URLs for AWS CloudFront private content
Basic Settings
Example: https://d111111abcdef8.cloudfront.net/private/video.mp4
Expiration Time
Policy Type
Key Pair Information
Example: APKAXXXXXXXXXXXXXXXX
Enter RSA private key in PEM format or read from file
How to use
About this tool
Generates signed URLs for accessing private content on AWS CloudFront. Supports both Canned Policy and Custom Policy, with advanced options including IP address restrictions, start time, and multiple resource patterns.
How to use
1. Basic Settings: Enter CloudFront URL, expiration time (relative/absolute/UNIX timestamp), and policy type (Canned/Custom) 2. Key Pair Information: Enter Key Pair ID and RSA private key in PEM format, or load from file 3. Advanced Options (Custom Policy only): Set IP address restrictions, start time, and multiple resource patterns 4. Click "Generate" to create the signed URL 5. Copy the generated URL, generate QR code, or test the URL
Options
Policy Type: Canned Policy (simple, expiration only) or Custom Policy (IP restrictions, start time, multiple resources). Expiration: Relative time (minutes/hours/days/weeks), absolute time (datetime and timezone), or UNIX timestamp (seconds). Advanced Options (Custom Policy): IP address/CIDR (e.g., 192.168.1.0/24), start time (datetime and timezone), resource pattern (wildcard support, e.g., https://d111111abcdef8.cloudfront.net/private/*).
Use cases
• Temporary access to premium content (videos, PDFs, images, etc.) • Generating download links for restricted files • Time-limited access control • Secure delivery with IP address restrictions • Bulk access permission for multiple file patterns
How it works
CloudFront signed URLs are generated using RSA-SHA1 signing. For Canned Policy, a simple URL parameter with expiration only is generated. For Custom Policy, a JSON policy (including IP restrictions, start time, resource patterns) is Base64 URL safe encoded and signed with RSA-SHA1. All processing is done in the browser; private keys are never sent to any server.
Privacy and data
All processing is done in the browser; private keys and generated URLs are never sent to any server. Private keys are only handled in memory and are not stored in local storage.
