If you control your own web server (like in dedicated hosting) and edit the configuration files yourself, then you have at least the options that you see used in
These are mostly technical options related to which versions of TLS may be used and which ciphers the client may negotiate with the server, so cryptographic parameters and defaults that are used in the course of the TLS connection.
You could also use the technologies that I mentioned like
If a user types "example.com" into a web browser, the web browser's behavior will be to go to "http://example.com/", not "https://example.com/". Similarly, if the user types "example.com/stuff", the browser will go to "http://example.com/stuff", not "https://example.com/stuff". And if the user follows an old HTTP link, the browser will try to load the HTTP resource pointed to by that link. So, the web server does need to be configured to send a redirect in each case.
With HSTS, individual browsers can be told that they always should automatically go to HTTPS for every resource on a particular site. But that still can't cover 100% of browsers.