vendix-s3-storage

To stop storing expiring AWS S3 presigned URLs, extract the underlying S3 key from the signed URL before persistence. This ensures only the static key is saved, preventing expired links and 403 errors.

Storing S3 keys instead of full presigned URLs improves data consistency by avoiding data churn from expired links. The database retains a stable key, and fresh presigned URLs are generated only on read for frontend consumption.

The best way to generate fresh presigned URLs for frontend display is to retrieve the stored S3 key from the database and pass it through an S3Service to sign a new, short-lived URL on read.

To sanitize image_url fields before persisting, parse the incoming signed S3 URL using helper logic to extract the core S3 key. Save this extracted key directly in your data access layer.

Yes, you need a backend storage service to sanitize S3 URLs on write and sign them on read. This service integrates into your data access layers to handle URL parsing and secure link generation.

Stored S3 image URLs return 403 errors over time because presigned URLs expire. Persisting the full signed URL means the link becomes invalid, whereas storing the S3 key avoids this issue.