Update Infrastructure access page (#196)

docs/services/access.md

@@ -18,10 +18,32 @@ CIROH has partnered with <strong>AWS, 2i2c and Google Cloud </strong> to provide
 CIROH also operates an on-premises infrastructure that includes high-performance computing (HPC) resources and specialized software. To request access to the on-premises infrastructure, please submit a GitHub template request detailing your project requirements and specifications. Our team will review your request and assist you in obtaining the necessary access.
 
 <a class="button button--active button--primary" href="https://github.com/CIROH-UA/NGIAB-CloudInfra/issues/new?assignees=&labels=on-prem&projects=&template=onprem-request.md&title="> On-premises Infrastructure Request Form</a>
-_____
-
+<br />
+<br />
 :::note
 - This form must be submitted by Principal Investigator (PI) of the project.
 - Your request will be handled by <i>DevOps staff at CIROH</i> and if permitted will be given access to the <strong>research cloud</strong> or <strong>on-premise</strong> infrastructure.
 
 :::
+
+### How to get access to Pantarhei?
+
+**Step 1**: Submit the On-Premise Infrastructure Request Form below to get access to Pantarhei:
+
+We encourage PI of the project to start here: (select On-Premises Infrastructure Request Form and fill out details)
+
+<a class="button button--active button--primary" href="https://docs.ciroh.org/docs/services/access/"> Infrastructure Request Form</a>
+
+---
+
+**Step 2**: Submit the On-premise Access Request form for individual user accounts on Pantarhei:
+
+<a class="button button--active button--primary" href="https://forms.office.com/Pages/ResponsePage.aspx?id=jnIAKtDwtECk6M5DPz-8p4IIpHdEnmhNgjOa9FjrwGtUMzdTOUpKVU5UWFNCU0ZQUlowS0cxV0xFRy4u"> On-Premise Access Request Form</a>
+
+---
+
+:::note
+For UA users, please submit On-Premises Access Request Form. For outside UA users, please start with VPN Access Request Form followed by On-Premises Access Request Form
+:::
+
+

docs/services/cloudservices/aws/documentation/aws-s3-sync/index.md

@@ -78,5 +78,4 @@ aws s3 sync s3://my-source-bucket s3://my-destination-bucket \
 - The --profile (or --dest-profile in some AWS CLI versions) is used for writing to the destination bucket.
 - Ensure both profiles have the necessary permissions on their respective buckets.
 - Be cautious with the --delete flag as it removes files in the destination that don't exist in the source.
-- Always test with --dryrun first to ensure the operation will do what you expect.
-- Basically, you have to create two access key profile, and attach those appropriate
+- Always test with --dryrun first to ensure the operation will do what you expect.