You can enable static website hosting for buckets and configure mirroring-based back-to-origin rules. After you host a static website on a bucket, you can access the bucket to visit the website. You are automatically redirected to the specified index page or error page. After mirroring-based back-to-origin rules are configured and take effect, you can use mirroring-based back-to-origin to seamlessly migrate data to Object Storage Service (OSS).
Notes
The sample code in this topic uses the region ID
cn-hangzhou
of the China (Hangzhou) region. By default, the public endpoint is used to access resources in a bucket. If you want to access resources in the bucket by using other Alibaba Cloud services in the same region in which the bucket is located, use an internal endpoint. For more information about the regions and endpoints supported by Object Storage Service (OSS), see OSS regions and endpoints.In this topic, access credentials are obtained from environment variables. For more information about how to configure access credentials, see Configure access credentials.
The
oss:PutBucketWebsite
permission is required for static website hosting or mirroring-based back-to-origin configurations. Theoss:GetBucketWebsite
permission is required to query static website hosting or mirroring-based back-to-origin configurations. Theoss:DeleteBucketWebsite
permission is required to delete static website hosting or mirroring-based back-to-origin configurations. For more information, see Attach a custom policy to a RAM user.
Static website hosting
Static websites are websites in which all web pages consist only of static content, including scripts such as JavaScript code that can be run on the client. You can use the static website hosting feature to host your static website in an OSS bucket and use the domain name of the bucket to access the website.
Configure static website hosting
Query static website hosting configurations
Delete static website hosting configurations
Mirroring-based back-to-origin
Mirroring-based back-to-origin allows you to seamlessly migrate data to OSS. For example, you can migrate services from a self-managed origin or from another cloud service to OSS without causing a service interruption. You can use mirroring-based back-to-origin rules during migration to obtain data that is not migrated to OSS. This ensures business continuity.
Configure mirroring-based back-to-origin
Query mirroring-based back-to-origin configurations
Delete mirroring-based back-to-origin configurations
References
For the complete sample code that is used to configure static website hosting and mirroring-based back-to-origin, visit put_bucket_website.go, get_bucket_website.go, and delete_bucket_website.go.
For more information about the API operation that you can call to configure static website hosting or mirroring-based back-to-origin, see PutBucketWebsite.
For more information about the API operation that you can call to query static website hosting configurations or mirroring-based back-to-origin rules, see GetBucketWebsite.
For more information about the API operation that you can call to delete static website hosting configurations or mirroring-based back-to-origin rules, see DeleteBucketWebsite.