More updates to SSH for Access for Infrastructure

Author: asamborski

src/content/docs/cloudflare-one/connections/connect-networks/use-cases/ssh/ssh-infrastructure-access.mdx

@@ -63,6 +63,10 @@ To generate a Cloudflare SSH CA and get its public key:
 ### Modify your SSHD config
 <Render file="ssh/modify-sshd" />
 
+:::note
+For certain distributions, such as Amazon Linux 1 (based on RHEL), the certificate file permissions must be set to 600 in order for the configuration to work. "
+:::
+
 ### Restart your SSH server
 <Render file="ssh/restart-server" />
 

src/content/partials/cloudflare-one/access/add-target.mdx

@@ -16,7 +16,7 @@ To create a new target:
 3. In **Target hostname**, enter a user-friendly name for the target resource. We recommend using the server hostname, for example `production-server`. The hostname does not need to be unique and can be reused for multiple targets. Hostnames are used to define the subset of targets included in an infrastructure application and are not used in DNS address resolution.
 	<Details header="Format restrictions">
 			- Case insensitive
-			- Contain no more than 255 characters
+			- Contain no more than 253 characters
 			- Contain only alphanumeric characters, `-`, or `.` (no spaces allowed)
 			- Start and end with an alphanumeric character
 	</Details>

src/content/partials/cloudflare-one/ssh/ssh-proxy-ca.mdx

@@ -32,4 +32,4 @@ import { Render } from "~/components"
    --header "Authorization: Bearer <API_TOKEN>"
    ```
 
-4. Copy the `public_key` value returned in the response.
+4. Copy the `public_key` value returned in the response.