- Newest
- Most votes
- Most comments
The ability to specify a specific older landing zone version (such as 3.0) when creating a new account depends on the specific tools or processes you are using for your landing zone implementation. It's important to note that AWS Landing Zone is a solution that provides a set of best practices, configurations, and automation for setting up and managing a multi-account AWS environment. The versions of Landing Zone, such as 3.0 and 3.1, represent different releases of the Landing Zone solution.
When creating a new account, the Landing Zone version that will be used for that account is typically determined by the configuration of your landing zone setup. If your landing zone setup is designed to use version 3.1 by default, the new account will automatically use that version.
However, if you specifically require the new account to be provisioned with an older version (e.g., 3.0), you may need to modify your landing zone configuration or provisioning process accordingly. This could involve customizing the automation scripts, templates, or configuration files used for provisioning accounts within your landing zone.
It's important to carefully review the documentation and guidelines provided by AWS for your specific landing zone solution to understand the options available for managing and provisioning accounts with different versions. Additionally, you may consider consulting with AWS support or engaging with AWS Professional Services for assistance in customizing your landing zone implementation to meet your specific requirements.
Relevant content
- asked 6 months ago
- asked 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 3 months ago
- AWS OFFICIALUpdated 2 years ago