When hosting a static website on your bucket (Psychz's sObject), there's a requirement that the bucket name must match the domain name. For the CNAME (Canonical Name) to function correctly, the bucket name must correspond precisely with the domain name. This ensures that the domain is mapped to the bucket seamlessly.
Example
Bucket Name: examplecom
You must set up a CNAME record in your DNS settings to make the bucket accessible via the domain name.
Create the Bucket
- Go to your bucket management interface and create a new bucket.
- Name the bucket exactly as your domain name, e.g., `examplecom.`
Set Up CNAME Record in DNS Settings
Access your domain's DNS settings through your domain registrar or DNS management provider.
Create a New CNAME Record
- Type: CNAME
- Name: `example.com`
- Target: `examplecom.sobject.uswest1.psychz.net`
- TTL (Time to Live): (Optional, but commonly set to 3600 seconds, which is 1 hour)
Good:
- Bucket: my-assets or myassets
- CNAME target: my-assets.sobject.uswest1.psychz.net
Bad:
- Bucket: my.assets
- CNAME target: my.assets.sobject.uswest1.psychz.net
Here's an example of how your DNS record might look
|
Type |
Name |
Target |
TTL |
|---|---|---|---|
|
CNAME |
example.com |
examplecom.sobject.uswest1.psychz.net |
3600 |
Verify Permissions
Ensure that the bucket permissions are set correctly to allow public access if you want the content to be accessible via the web. This can be done by right-clicking on the bucket or file, selecting 'Permissions,' and then adjusting the settings to 'Public'.
Summary
To summarize, for the CNAME to work correctly
- The bucket name should be DNS-compatible. If using a wildcard endpoint, avoid dots in the bucket name.
- Configure the CNAME record so that the domain points to the corresponding bucket URL in the format: `<bucket_name>.sobject.uswest1.psychz.net`.
This configuration allows seamless access to the bucket content via the domain name, providing a smooth and professional experience for users accessing your content.