Help
Back to home
Português
Português
  • Visão geral
    • Nossas Features
    • Catálogo de descontos AWS
    • Money back guarantee
  • Como Começar
    • Etapas
      • Step 1 - Estimate Savings Preview
      • Step 2 - Authorize Dotted
      • Step 3 - Know your Business
      • Team Invitation
      • Additional AWS accounts
      • Post onboarding
    • Múltiplas contas
      • via 'Join Account(s)'
      • Leave an AWS Organization
      • via 'Join With A Pre-Existing Org(s)'
  • Plataforma e Serviços
    • Nossa plataforma
      • Menu de Navegação
      • Relatórios
        • Estimativas
        • Resultados
        • Cobranças
      • Configurações
        • Organizações
        • Contas
        • Usuários
      • Suporte
        • ChatDot AI
        • Suporte
    • Financeiro
    • Notas de Versão
  • Ajuda e Suporte
    • Dúvidas Gerais
    • Canais de Suporte
    • Acessos e Segurança
      • Cross Account Role
      • Role Deployment
      • Other Housekeeping
      • Access Management
  • Entendendo a AWS
    • Compromissos
    • Reservas de Instâncias (RIs)
    • Savings Plans
Fornecido por GitBook
Nesta página

Isto foi útil?

  1. Como Começar

Múltiplas contas

AnteriorPost onboardingPróximovia 'Join Account(s)'

Atualizado há 10 meses

Isto foi útil?

If your company has a multi-account architecture, we recommend calculating the savings estimate on Dotted first using your management account. This will provide us with a fairly accurate estimate of your potential savings.

Your management account is your 'root account' that you created your AWS account with, you can also verify this by visiting this and seeing which account is designated as 'management account'.

Once you've checked your savings with your management account following the steps listed in , assess if you'd need to be breaking your organization or importing it whole.

Otherwise removing an AWS Organization can impact the following ways and we recommend you evaluate each of the impact items for yourself:

Impact
Description

Access control

Breaking an organization can affect access control and permissions, which may require additional configuration and management.

Cross-account functions management

Managing cross-account functions like logging, security, and monitoring can become more complex when you break an organization.

Account management

Managing multiple accounts separately can be more difficult than managing them within an organization.

Organizational structure

Dotted can recreate the OUs for you in our organization

If you have one or more active accounts within your AWS organization (like the example shown above) and don't have SSO setup - we recommend you disassociating your accounts from the organization & join the standalone account via the steps linked .

If you have SSO setup through (see if it is enabled on your end) we recommend you DO NOT disassociate your AWS accounts from your organization.

Please proceed here with caution, and check in with us at or starting an intercom chat.

Dotted sets up a for you to overcome this.

You may lose the that you have set up within the organization, which can impact the way you manage and organize your accounts.

Bottom line - If you do not have SSO setup for your AWS organization or have communication setup between accounts, we recommend that you break up your organization following these .

However, if you do have it setup or cannot break an organization due to a complex setup, we recommend you to follow the steps .

here
steps
here
AWS Identity Center only
support@usedotted.com
'billing group'
organizational structure (OUs)
link
Getting started