Global vs regional about aws-deployment-framework HOT 5 CLOSED

Hi @larsrnielsen

regional.yml will bootstrap accounts in regions other than the global region. When setting up ADF you would of defined a global (main) region, this region will be the target for any global.yml files found. You can also define target regions, these regions will be the target for any regional.yml files. Currently ADF does not apply the regional.yml to the global region even if its included as a target region.

I would recommend creating a deployment pipeline in the deployment account to deploy resources (such as CloudTrail, Logging resources) in a scalable and streamlined manner as oppose to bootstrapping these into the accounts.

from aws-deployment-framework.

from aws-deployment-framework.

Hi @larsrnielsen

There is no need to reconfigure the deployment map for each new account, just set it up to target the OU's you would like to have your foundation stacks deployed to, then set it to ExecuteOnPipelineUpdate. For example:

pipelines:
  - name: sample-pipeline  # The name of your pipeline (This will match the name of your repository)
    type: cc-cloudformation  # The pipeline_type you wish to use for this pipeline
    params:
      - SourceAccountId: 111111111111  # The source account that will hold the codebase
      - RestartExecutionOnUpdate: true # This means it will automatically trigger when a new account moves into any of the below OU's (After they have been bootstrapped)
    targets:  # Deployment stages
      - /business_unit/testing
      - /business_unit/production

You can create multiple pipelines for different foundation aspects, you can even set up pipelines to have completion triggers that will trigger other pipelines when they complete successfully. This is the preferred way to go when deploying resources. The base stacks are mostly just for setting up ADF roles that are then assumed by pipelines. Where possible its best to avoid adding more resources to them.

from aws-deployment-framework.

Closing as this was a question, let me know if I can elaborate further.

from aws-deployment-framework.

Currently ADF does not apply the regional.yml to the global region even if its included as a target region.

Hey @bundyfx, thanks for the explanation. Could you elaborate on why regional bootstrapping is not roled out to the deployment-account region?

At least I would propose to document the behavior in the Admin Guide. Currently it states

No need to also include 'eu-central-1' in targets as the deployment-account region is also considered a target region by default.

which led me believe that regional baselines are also deployed to the deployment-account region.

My current workaround/hack is to duplicate all resources from regional.yml to global.yml.

from aws-deployment-framework.