Advanced Search
Search Results
98 total results found
Sandbox Studio Installation Guide
This is the installation guide for Sandbox Studio
User Guide
Manager Guide
Administrator Guide
Solution overview
The overview describes the Features and Benefits, Use cases and concept and definitions.
Architecture overview
I think we need an "Architecture" section....not to explain how we built it - but to explain e.g. Organisations, Onboarding OU, Exit OU Hub Account etc
Plan your deployment
This section describes the Regions, cost, security, and other considerations prior to deploying the solution.
Deploy the Solution
Post-deployment configuration tasks
After you successfully deployed the stacks, complete the following tasks to configure the: IAM Identity Center and the Web Application
Using the web UI
This section provides detailed instructions on how to log into the web UI, and links to the end User Guides for the Administrator, Manager, or a User.
Troubleshooting & Support
If you need support, there is a full knowledge base and ticketing site here: https://support.sandboxstudiosoftware.com/ Below are some common problems identified during installation.
Uninstall the solution
To uninstall the solution, follow these steps: End leases and eject accounts Uninstall stacks Delete the custom application from the IDC
Revisions
Terms and Conditions
Application Licencing
Account Templates
Guide to create and update lease templates
Monitoring the solution
@Philippe is this needed with SBS?
Role-Based Permissions (is this needed??)
Choosing the right Budget and Duration configuration
When creating the account templates, you will be prompted to set a budget , duration as well as thresholds that can trigger an action when a limit is reached, let's look at this in more detail.
Settings
Installation script
Automatically deploy Sandbox Studio using our script
Features and Benefits
Instant Account Access Stay on Budget Simplified Account Cleanup Built-in Security Quickly provide secure, temporary AWS accounts with pre-configured policies, ready for use in just seconds. Automatically set spending limits and receive...
Use cases
Development and innovation experiments Developers who want to build a proof of concept on new AWS services, or run innovation experiments and prove the business value, before moving to a CI/CD pipeline. Train and test GenAI models Machine learning engineers...
Concepts and definitions
Sandbox environment A controlled, isolated environment where teams can experiment with AWS services without impacting production systems. It provides a safe space for learning, testing, and innovation. Organizational Unit (OU) A grouping of AWS accounts tha...
Prerequisites
Adjust based on new install mechanisim Before launching the stacks, you must meet the following prerequisites: Identify the AWS account where you want to deploy the solution: Use the AWS Management Console to identify and name this as the Hub account. We r...
AWS CloudFormation templates
This page needs careful work This solution uses AWS CloudFormation to automate the deployment of Sandbox Studio on AWS in the AWS Cloud. It includes the following CloudFormation template, which you can download before deployment. AccountPool stack View Temp...
Prepare to Launch the Stack
Needs editing You must gather deployment parameter details before deploying the stacks. For details, refer to Prerequisites. Time to deploy: Approximately 60 minutes You will need to deploy these four stacks for the Sandbox Studio solution in the following ...
Step 1: Deploy the AccountPool stack
This page needs techie work In this step, you will deploy the resources required to set up Organizational Units (OUs), Service Control Policies (SCPs), roles, and Regions. Important: Ensure that you log into the Org Management account for deploying the Accou...
Step 2: Deploy the IDC stack
This needs a proper look at by the techies. In this step, you will deploy the resources required to set up IDC, including mappings, roles, policies, and other configuration. Important: Ensure that you log in using the account where you have configured the IA...
Step 3: Deploy the Data stack
Needs a proper look at by techies In this step, you will deploy the data resources required for the Sandbox Studio application. Important: Ensure that you are logged in using the Hub account for deploying the Data stack. Sign in to the AWS Management Cons...
Step 4: Deploy the Compute stack
This needs a proper check by techies In this step, you will deploy the compute resources required for the Sandbox Studio application. Important: Ensure that you are logged in using the Hub account for deploying the Compute stack. Sign in to the AWS Manage...
Step 5: ?????
Solution Architecture
@Team - decide what architecture diagram to share Sandbox Studio on AWS architecture The high-level process flow for the solution components deployed with the AWS CloudFormation templates is as follows: Users access the solution (SAML2.0 application) ...
AWS Well-Architected design considerations
This solution uses the best practices from the AWS Well-Architected Framework which helps customers design and operate reliable, secure, efficient, and cost-effective workloads in the cloud. This section describes how the design principles and best practices ...
Running Costs
There are two cost components for running Sandbox Studio: Administrative Cost: This is a small overhead for running the Sandbox Studio application within your AWS account. It varies based on your deployment configuration. For example, a small customer wit...
Security
The following resources are engaged in setting up and running the Sandbox Studio solution. Resource Access IAM roles IAM roles allow customers to assign granular access policies and permissions to services and users on the AWS Cloud. Multiple roles are requ...
Quotas
Quotas for AWS services in this solution Service quotas, also referred to as limits, are the maximum number of service resources or operations for your AWS account. Make sure you have sufficient quota for each of the services implemented in this solution. Fo...
Choosing the deployment accounts
Accounts To deploy this solution, you will need access to these accounts. NEED TO ADD OTHER STACK INFO Organizations Management account The AccountPool stack, deployed into the AWS Organizations management account, is used to manage the lifecycle on sandbo...
Create a SAML 2.0 application
In this step, you federate your Identity Provider (IdP) to IAM Identity Center through SAML 2.0, and use IAM Identity Center to manage user access to the solution. Note: Log in to the account where the IAM Identity Center is enabled (usually the Org Managemen...
Map application attributes
In this step, you map application attributes to the user attribute in IAM Identity Center, using the email address for authentication. From the list of applications, choose the SAML application we set up in the previous step. Under Actions, select Edit att...
Assign groups to your application
The IDC stack creates these three user groups in IAM Identity Center (where NAMESPACE is the namespace parameter passed to the stack). <NAMESPACE>_IsbUsersGroup <NAMESPACE>_IsbManagersGroup <NAMESPACE>_IsbAdminsGroup To assign g...