Source:[https://www.trek10.com/blog/guiding-priciples-for-building-saas-on-aws](trek10 | 3 guiding principles for building new saas products on aws)
- Build as if you might sell it.
- Forces to build with best practices and isolation
- Use account isolation - different accounts for different projects AWS OrganizationFormation is recommended tool for this.[https://github.com.OlafConijn.AwsOrganizationFormation](github - olafconijn.awsorganizationformation: better than landingzones) =Move your development environment towards the cloud, do not try to move the cloud down to your dev environment.= AWS Cloud9 could be used for this. =Simply put, there is no sufficient simulation or substitute for actual cloud resources.=
- Build as if you may open-source at any time
- Can't use security by obscurity.
- No secrets in code or cert files in repo
- Regularly audit the project dependencies
- Have an automated and comprehensive pipeline for deploying code
- The "embarrassment" angle can encourage you to be more on it with testing and componentising.
- Documentation will tend to be better.
- Build with a cloud-native mindset
- =any time I stray from a platform-native offering it's reasonably high likelihood I will regret it=
- Infrastructure as code.