Allow pipelines to target nested organisational units about aws-deployment-framework HOT 3 CLOSED

Gotcha, I think there is value in having some clever way of handling OU's with 100+ accounts in them (eg sandbox) - At the moment I think having sandbox type OU's under a specific OU is the best bet.

However I think it would be good to have a way to handle this. One option would be to create a new sequential action (Limit of 50) within that same stage once we reach 50 Parallel accounts (also limit of 50). We just need to make sure we build within the limits of CodePipeline itself. The most important thing is that the deployment_map.yml stays true and reflects the stages of the pipeline itself. Otherwise It could be very confusing if a user were to look at the map, see one stage however in CodePipeline see many stages.

For now I'll flag this as a enhancement and we will work out how to add a sequential deployment action to a stage once we reach 50 accounts (parallel) within a single stage.

from aws-deployment-framework.

Hi @bundyfx

Great, thanks for looking into it. Its not a big issue for us but would be a nice feature.

The problem with getting a large number of accounts in a single stage isn't really limited to this enhancement request, although it can indeed exaggerate the issue. At least in our case we will likely end up with quite a few accounts (10's to perhaps >100) in a single organisational unit.

Maybe a solution for these large deployment phases could be to create a new deployment phase for every x amount of accounts?

from aws-deployment-framework.

Hi @thiezn

This could be possible, and could potentially help users scope large amounts of targets within a single stage. I also agree with the optional control of this feature. One thing with this however, is that it could be an extremely large amount of accounts in a single stage. Which, is some ways, might be used when really a safer, more staged approach to deploying resources would be preferable. Potentially, If there is something that should be in a very large amount of accounts like this, maybe it should be part of the base (bootstrap) template for all OUs.

It could also raise potential problem when it comes to limits of CodePipeline itself. That being said, I will investigate this possibility further.

from aws-deployment-framework.