INSERTCART AWS WEB · HOSTING GUIDE
Publish website updates and roll back a CloudFront release
Upload complete releases, wait for CloudFront cache propagation, and restore an earlier website release.
Upload the complete website
In Manage websites, choose your website and expand Publish an update. Upload its complete ZIP or folder, including index.html and every referenced asset. An update is a new release, rather than a patch applied to the previous folder. Files missing from the new upload will be missing from that release.
Understand how a release becomes live
The new backend validates the archive before uploading it to a separate release prefix. Once every file has been uploaded, it changes the CloudFront origin path to that release and requests a cache invalidation. The dashboard waits for both operations before marking the job ready. Visitors can see the previous release while AWS propagates the change.
Browser caches and edge caches are separate. Files uploaded by this tool ask browsers to revalidate stable asset URLs and allow CloudFront to cache them at the edge. If you add a service worker or a separate caching layer to your website, account for that layer when testing an update.
Restore an earlier release
Expand Release history & rollback and choose Restore next to a completed release. CloudFront switches to that release’s existing files and invalidates its cache. The service does not replace files one at a time or recreate your bucket. Restoring a release still needs AWS propagation time.
S3 versioning also retains prior object versions. The dashboard uses complete release prefixes for rollback; S3 object versions remain an additional recovery mechanism in AWS. Retained releases and object versions use storage. Review and clean up unused content according to your needs.
Resume after a browser closes or credentials expire
Refresh the selected website to see its active background job. Closing a browser does not cancel the AWS workflow. If an advanced session expires, connect a new session for the same AWS account and use the dashboard’s connection control to attach it to your website. An IAM role connection can request new temporary sessions when required, provided the role still exists.
When you use the original API
The original template API does not register sites in the new dashboard. Its websites can still be updated directly through their AWS console. Do not use the new release manager for a site that was created outside the new service unless a supported import workflow is added later.
For manual publishing, upload your files to the original bucket and use a CloudFront invalidation when appropriate. Keep the origin structure consistent with how that website was created. See AWS’s content update documentation.
Ready to publish?
Bring your static website files and connect your own AWS account.
Open the launch workspace ↗Browse hosting guides · Connection security · Understand costs