2 months ago
Hello! I am observing odd behaviour with the Railway managed S3 buckets. When using 3rd party browsers (I've tried multiple and observe the same bheaviour), even after deleting a specific bucket, and creating a new one, and then using it's credetials to browse it. The previously deleted buckets are still visible, albeit inaccessible (status code 403). This is unexpected (and not desired) behaviour.
In the screenshot (the 2nd bucket was deleted a long time ago in Railway)
1 Replies
Status changed to Awaiting Railway Response Railway • 2 months ago
2 months ago
When you delete a bucket, it enters a 2-day grace period before permanent deletion from our storage provider. Third-party S3 browsers call ListBuckets at the account level, which can show all buckets associated with your workspace, including ones pending permanent deletion. If the bucket you're seeing was deleted more than 2 days ago and is still appearing, let us know and we can look into whether the cleanup completed on our end.
Status changed to Awaiting User Response Railway • 2 months ago