简体   繁体   English

如果我将AWS独立帐户迁移到组织怎么办?

[英]What if I migrate an AWS standalone account to Organizations?

At work, we have an AWS standalone account which have been created some time ago by the IT Department and inside we have some users created. 在工作中,我们有一个独立的AWS账户,该账户是IT部门早些时候创建的,在内部我们创建了一些用户。 Now we want to move to AWS Organizations because the consolidated billing and the possibility of apply ACL across multiple users. 现在,我们要转到AWS Organizations,因为合并账单以及可以在多个用户之间应用ACL的可能性。

My question is: What happen with the already running services that have been created via the standalone account (eg, API Gateways, Lambda functions, S3 buckets and EC2 instances) when we switch to Organizations format? 我的问题是:当切换到“组织”格式时,通过独立帐户创建的已经运行的服务(例如API网关,Lambda函数,S3存储桶和EC2实例)会发生什么情况?

The answer to this question change if we create a new account and then invite our already old account to the new organization? 如果我们创建一个新帐户,然后邀请我们已经很旧的帐户加入新组织,此问题的答案就会改变吗?

AWS Organizations is just an account management tool- it doesn't affect the resources within an account. AWS组织只是一个帐户管理工具-它没有一个帐户影响的资源。 So, to answer your question: your resources will stay as they are after you switch to Organizations. 因此,回答您的问题:切换到组织后,您的资源将保持不变。

My question is: What happen with the already running services that have been created via the standalone account (eg, API Gateways, Lambda functions, S3 buckets and EC2 instances) when we switch to Organizations format? 我的问题是:当切换到“组织”格式时,通过独立帐户创建的已经运行的服务(例如API网关,Lambda函数,S3存储桶和EC2实例)会发生什么情况?

There won't be any impact for the existing services under your account unless you enable Service Control Policies and attach a restrictive policy to the AWS account, where existing users won't be able to perform restricted actions (By default, Service Control Policies are Disabled in Organizations). 除非您启用服务控制策略并将限制性策略附加到AWS账户(现有用户无法执行受限操作)(默认情况下,服务控制策略为在组织中已禁用)。 Only noticeable thing is, the billing will be consolidated to the root account. 唯一值得注意的是,帐单将合并到根帐户。 You can even detach the account from the organization, later if needed. 您甚至可以在以后将帐户从组织中分离出来,如果需要的话。

The answer to this question change if we create a new account and then invite our already old account to the new organization? 如果我们创建一个新帐户,然后邀请我们已经很旧的帐户加入新组织,此问题的答案就会改变吗?

There is a difference when creating a new account under the organization vs inviting an already existing account to become a part of an organization. 在组织下创建新帐户与邀请已有的帐户成为组织的一部分是有区别的。 The main difference is, when you create a new account under the organization, the account cannot be detached from the organization later on. 主要区别在于,当您在组织下创建新帐户时,以后无法将其与组织分离。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 如果我在 AWS 组织中创建 AWS 账户,我可以从拥有该组织的根账户中删除它吗? - If I create an AWS account in AWS organizations, can I delete it from my root account which owns the organization? 在其账户中创建来自 AWS 组织的用户 - Create users from AWS organizations in an account from it 在多个 AWS Organizations 账户上部署资源 - Deploying resources on multiple AWS Organizations account 终止我的 aws 组织中的成员帐户?(不是根帐户) - terminate a member account in my aws organizations?(not the root account) 使用适用于Java的AWS开发工具包在AWS Organizations中创建帐户 - Creating Account in the AWS Organizations using AWS SDK for Java 如何通过 AWS Organizations 创建的根账户进行新访问? - How to access newly, via AWS Organizations created root account? 使用同一账户的不同组织中的 AWS 访问环境 - AWS Access environments in different Organizations using the same account 将 AWS 服务从一个 AWS 账户迁移到另一个 AWS 账户 - To Migrate AWS Services from one AWS Account to another AWS Account 如何将现有 AWS IAM 用户迁移到 AWS SSO 跨账户? - How do I migrate existing AWS IAM users to AWS SSO cross-account? 将机器和数据从一个AWS账户迁移到另一个AWS账户的最简单方法是什么 - What is the easiest way to migrate machine and data from one AWS account to another
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM