wip - starting resource-self-service

Author: em0ney

docs/solutions/03-resource-self-service/01-create-golden-paths.md

@@ -78,12 +78,28 @@ We'll explore 2 types of self-service below - RESTful Self-Service and Gitops-ba
 
 RESTful self-service actions directly create resources in your cloud provider or other upstream systems through their APIs. This approach is straightforward and immediate—when a developer requests a resource through Port's self-service interface, the action makes API calls to create the resource directly in the target system (like AWS, Azure, or GCP). This pattern works well for organizations that prefer direct resource creation or when you need immediate provisioning without the overhead of Git-based workflows. The trade-off is that you lose the audit trail and version control benefits that come with GitOps, but you gain simplicity and speed for teams that don't need the full GitOps workflow.
 
+- [Create an S3 Bucket via Webhook](../../guides/all/s3-using-webhook)
+
 ##### GitOps-based Self-Service
 
 GitOps-based self-service actions create resources by leveraging your existing Infrastructure as Code (IaC) files and modules. Here, an existing GitOps pipeline (like ArgoCD, Flux, or Terraform Cloud) picks up the changes and provisions the resources in the target cloud environment. This approach maintains the benefits of version control, audit trails, and the ability to review changes through pull requests, while still providing developers with a streamlined self-service experience. The trade-off is that resource creation takes longer due to the GitOps pipeline cycle, but you gain better governance, compliance, and the ability to enforce organizational standards through code review processes.
 
-- [Create Cloud Resource Using IaC](../../guides/all/create-cloud-resource-using-iac/)
-
+- [Create Cloud Resource Using IaC](../../guides/all/create-cloud-resource-using-iac)
+- [Deploy S3 Bucket CrossPlane](../../guides/all/deploy-s3-bucket-crossplane)
 
 ### Create Secrets
 
+Secret leakage remains a huge issue in the industry. The fact that developers have to manually handle secrets is like a process in a nuclear plant requiring the manual handling of uranium. It's an error prone workflow, that often leads to a security incident and in worse cases, supply chain security issues and data loss.
+
+The best protection against secret leakage is the design of a secure workflow, in which secrets are securely handled and developers are unlikely to make an error.
+
+- [Create GitHub Secret](../../guides/all/create-github-secret/)
+<iframe
+  width="560"
+  height="315"
+  src="https://www.youtube.com/embed/QO45jaeAA2o"
+  title="Secure Secrets Management"
+  frameborder="0"
+  allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture"
+  allowfullscreen
+></iframe>