A website's objects are stored in an S3 bucket with Versioning enabled and served through CloudFront. Recently some files were updated but retained the same object keys, yet users still see the old content. What is the correct way for an administrator to ensure the updated objects are served immediately?

Creating a CloudFront invalidation for the paths of the changed objects forces CloudFront to remove the cached content and fetch the latest version from the S3 origin. This ensures users immediately see the updated content. Generating a CloudFront signed URL is for controlling access to private content, not for forcing cache updates. Configuring an S3 origin access identity (OAI) allows CloudFront to access private S3 content but doesn't resolve caching issues. Disabling S3 Versioning is not recommended as it removes the ability to recover previous object versions and does not directly address CloudFront's caching behavior.