Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

S3 HTTPS #4738

Closed
fpillotovh opened this issue Jun 5, 2023 · 3 comments
Closed

S3 HTTPS #4738

fpillotovh opened this issue Jun 5, 2023 · 3 comments
Assignees

Comments

@fpillotovh
Copy link
Contributor

fpillotovh commented Jun 5, 2023

As a past techwriter, I would like to create this issue concerning the guide: https://help.ovhcloud.com/csm/fr-public-cloud-storage-s3-static-website-https?id=kb_article_view&sysparm_article=KB0058097 ...
I was opposed to it after OVH's VTT because it didn't offer ssl ... but this is even worse :

  • the dig command is totally wrong as the answer indicates
  • the site given as an example no longer exists??
@lason-ovh
Copy link
Contributor

As a past techwriter, I would like to create this issue concerning the guide: https://help.ovhcloud.com/csm/fr-public-cloud-storage-s3-static-website-https?id=kb_article_view&sysparm_article=KB0058097 ... I was opposed to it after OVH's VTT because it didn't offer ssl ... but this is even worse :

* the dig command is totally wrong as the answer indicates

* the site given as an example no longer exists?? mega lol for a major european hoster

Hi, thanks for the feedback.

Do you care to explain why "this is even worse"?

As for the dig command, maybe replacing it with a simple host command would be enough.

Finally, yes indeed the site given as example is no longer exists, we will edit the documentation to remove the part mentioning it.

@fpillotovh
Copy link
Contributor Author

Do you care to explain why "this is even worse"?

no documentation is better than lousy documentation ... then it all depends on the image you want to convey about the company that hires you.

The dig command could simply have been corrected by adding the {bucket}in it, the host command works even though it's not recommended in terms of best practices.

@lason-ovh
Copy link
Contributor

The dig command could simply have been corrected by adding the {bucket}in it, the host command works even though it's not recommended in terms of best practices.

Thanks for your remark, yes indeed host is not recommended but we will keep the documentation as simple as possible as the main purpose here is to do a very simple dns lookup, so the example will be replaced with a host cmd.
However, we will mention in the doc that a dig or a host cmd can be used to do that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants