Getting started
Prerequisites
Creating an Organization
Creating Audit and Log Archive AWS AccountsManagement
Creating an AWS Account
Initial Setup
Billing Alerts
Configuring AWS SSO (IAM Identity Center)
Generating As-Built Documentation
Alliance ModeEnvironments
Environments
Configuring AWS Client VPN
Configuring Private Bastion
Deleting an Environment
Domains
Service RolesCompliance
Compliance standards
Compliance status
Configuring a standardReference
Choosing Email Addresses for your AWS Accounts
Checklist end-of-deployment
Configuring SSO for Microsoft Azure
Configuring SSO for G-Suite
Deploying Applications
Notification History
Removing NX1 Access from AWS Accounts
Reduce permission access for NX1
What’s deployed in my accountTroubleshooting
Troubleshooting
Common Issues
Finding the Root Cause of a Failed Job
Creating new environment failed
Fixing Network Access is not connecting to RDS
SSO G-Suite - Deploy Lambda ErrorChoosing Email Addresses for your AWS Accounts
To create the accounts, you will need a unique email address for each account.
If you use Office365 as your email provider, you must create an email alias per account.
Examples:
aws-audit@piedpiper.com
aws-prod@piedpiper.com
If your email provider is Google, it supports adding a plus sign to automatically create aliases.
Example:
Email is aws@piedpiper.com
Supported aliases:
aws+audit@piedpiper.com
aws+prod@piedpiper.com