[watermelon0]

This might be problematic in some use cases.

For example, if a software company works on different products, they would ideally have separate AWS accounts/environments for each product.

If they have established pipelines/infrastructure/procedures/etc., and they use CodeCommit as part of such infrastructure, they won't be able to create a new project, without reworking everything.

[nerdjon]

I was honestly wondering about that myself. If in an organization I CodeCommit in use on one account but I need to move over (and for whatever reason moving off of CodeCommit isnt an option at the moment) could this flag be at the organization level or on the account level. Or at the very least an account rep could override since that since I am actually already using it.