A Static Site Where Encrypting the Bucket Would Break It

An OBS bucket serving a static website, published by an OBS-format bucket policy rather than a public-read ACL, so the file list stays private. Encryption is off on purpose: every byte is published deliberately, and an anonymous reader holds no permission on your key, so a key of your own hides nothing and stops the site working.

This is the operations reference: version drift, dependants and neighbours. For what the module provisions, its inputs and outputs, and how to buy it, see the catalogue entry.

terraformHuawei CloudServerless & Containersv1.0.0static-validated

Provider drift

This artifact declares no Terraform provider requirements, so there is nothing to drift. Provider freshness applies to Terraform and OpenTofu modules.

What depends on this

No reference architecture names this module, so changing it affects only configurations that reference it directly.

Nearest alternatives

Same cloud, same category. These are what you would weigh against it without changing provider.

A FunctionGraph Function with Its Own Agency, LTS Logs, and Secrets Encrypted with Your Key An App Platform Whose Components Are Actually Deployed

The same job on other clouds

Static Site Hosting on other providers. Useful when the cloud is still open, or when you are pricing a second one. How far a comparison like that can be trusted is covered in comparing clouds.

A Pages Project Whose Previews Are Not Public by AccidentCloudflare A Static Site That Tells You the File List Is Public TooTencent Cloud A Static Site Whose Bucket Is Readable and Whose File List Is NotAlibaba Cloud A Static Site Whose Policy Version Is Not the One Every S3 Example UsesScaleway An Amplify App Whose Previews Are Behind Basic Auth and Whose Branches Do Not MultiplyAWS Azure Static Web AppAzure

Installing it

module "huawei_static_site" {
  source  = "www.iac-bazaar.com/iac-bazaar/huawei-static-site/huaweicloud"
  version = "1.0.0"
}

A registry token is required for the download itself. Installing through the registry protocol has the two credential steps.