Update guide – Add instructions for creating the Sandbox folder before cloud account onboarding

[skellish-turbot]

Guide to be updated
Getting Started with AWS | Connect an AWS Account to Guardrails
URL: https://turbot.com/v5/docs/guides/getting-started/aws/connect-an-aws-account

---

Reason for update
The guide instructs users to select the "Sandbox" folder as the import location for their AWS account, but there are no prior instructions on creating this folder. This can cause confusion for new users, as the "Sandbox" folder does not exist by default. The same issue is present in the Azure and GCP onboarding guides, indicating a need for a foundational step that covers environment preparation.

---

Proposed changes

• Add a new preliminary section or page (e.g., "Prepare the Guardrails Environment") before the cloud onboarding steps (AWS, Azure, GCP).
• In this new section, provide instructions for creating the "Sandbox" folder under the Turbot root, including:
  • The purpose of the Sandbox folder (e.g., for testing, isolation, or best practices).
  • Step-by-step instructions and screenshots for creating the folder.
  • Any relevant naming conventions or organizational recommendations.
• Update the "Connect an AWS Account," "Connect an Azure Subscription," and "Connect a GCP Project" guides to reference this new preparatory step, ensuring users are not confused when asked to select the "Sandbox" folder.
• Optionally, clarify in the guides that if the Sandbox folder does not exist, it should be created before proceeding.

---

[RahulSrivastav14]

While the original suggestion recommended creating a dedicated “Prepare the Guardrails Environment” section with step-by-step folder creation instructions, we’ve opted for a more streamlined solution by adding a contextual note in each onboarding guide (AWS, Azure, GCP). This note:
• Acknowledges the possible absence of the “Sandbox” folder.
• Clarifies its intended use in production contexts.
• Provides a direct link to the Create Folder Guide for users who need detailed instructions.

This approach avoids duplication of existing documentation, reduces maintenance overhead, and still ensures that users are not blocked or confused when instructed to select the “Sandbox” folder. It balances guidance with conciseness and keeps the onboarding flow focused.