@@ -349,30 +349,30 @@ IAM permission boundaries. Where applicable, the roles received a new prefix.
349
349
This makes it easier to identify what part of ADF relies on those roles and
350
350
whom should have access to assume the role or modify it.
351
351
352
- | Previous prefix | Previous name | New prefix | New name |
353
- | ------------------| ---------------------------------------------------------------------| ----------------------------| ---------------------------------------------------------------|
354
- | / | ${CrossAccountAccessRoleName}-readonly | /adf/organizations/ | adf-organizations-readonly |
355
- | / | adf-update-cross-account-access-role | /adf/bootstrap/ | adf-update-cross-account-access |
356
- | /adf-automation/ | adf-create-repository-role | /adf/pipeline-management/ | adf-pipeline-management-create-repository |
357
- | /adf-automation/ | adf-pipeline-provisioner-generate-inputs | /adf/pipeline-management/ | adf-pipeline-management-generate-inputs |
358
- | /adf-automation/ | adf-pipeline-create-update-rule | /adf/pipeline-management/ | adf-pipeline-management-create-update-rule |
359
- | / | adf-event-rule-${AWS::AccountId}-${DeploymentAccountId}-EventRole-* | /adf/cross-account-events/ | adf-cc-event-from-${AWS::AccountId}-to-${DeploymentAccountId} |
360
- | ------------------| ---------------------------------------------------------------------| ----------------------------| ---------------------------------------------------------------|
352
+ | Previous prefix | Previous name | New prefix | New name |
353
+ | -------------------- | ----------------------------------------------------------------------- | ------------------------------ | -- ---------------------------------------------------------------|
354
+ | / | ${CrossAccountAccessRoleName}-readonly | /adf/organizations/ | adf-organizations-readonly |
355
+ | / | adf-update-cross-account-access-role | /adf/bootstrap/ | adf-update-cross-account-access |
356
+ | /adf-automation/ | adf-create-repository-role | /adf/pipeline-management/ | adf-pipeline-management-create-repository |
357
+ | /adf-automation/ | adf-pipeline-provisioner-generate-inputs | /adf/pipeline-management/ | adf-pipeline-management-generate-inputs |
358
+ | /adf-automation/ | adf-pipeline-create-update-rule | /adf/pipeline-management/ | adf-pipeline-management-create-update-rule |
359
+ | / | adf-event-rule-${AWS::AccountId}-${DeploymentAccountId}-EventRole-* | /adf/cross-account-events/ | adf-cc-event-from-${AWS::AccountId}-to-${DeploymentAccountId} |
360
+ | ------------------ | --------------------------------------------------------------------- | ---------------------------- | --------------------------------------------------------------- |
361
361
362
362
#### ADF Renaming of Resources
363
363
364
- | Type | Previous name | New name |
365
- | --------------| -----------------------------------------------| --------------------------------------------------------|
366
- | StateMachine | EnableCrossAccountAccess | adf-bootstrap-enable-cross-account |
367
- | StateMachine | ADFPipelineManagementStateMachine | adf-pipeline-management |
368
- | StateMachine | PipelineDeletionStateMachine-* | adf-pipeline-management-delete-outdated |
369
- | Lambda | DeploymentMapProcessorFunction | adf-pipeline-management-deployment-map-processor |
370
- | Lambda | ADFPipelineCreateOrUpdateRuleFunction | adf-pipeline-management-create-update-rule |
371
- | Lambda | ADFPipelineCreateRepositoryFunction | adf-pipeline-management-create-repository |
372
- | Lambda | ADFPipelineGenerateInputsFunction | adf-pipeline-management-generate-pipeline-inputs |
373
- | Lambda | ADFPipelineStoreDefinitionFunction | adf-pipeline-management-store-pipeline-definition |
374
- | Lambda | ADFPipelineIdentifyOutOfDatePipelinesFunction | adf-pipeline-management-identify-out-of-date-pipelines |
375
- | --------------| -----------------------------------------------| --------------------------------------------------------|
364
+ | Type | Previous name | New name |
365
+ | ---------------- | ------------------------------------------------- | -- --------------------------------------------------------|
366
+ | StateMachine | EnableCrossAccountAccess | adf-bootstrap-enable-cross-account |
367
+ | StateMachine | ADFPipelineManagementStateMachine | adf-pipeline-management |
368
+ | StateMachine | PipelineDeletionStateMachine-* | adf-pipeline-management-delete-outdated |
369
+ | Lambda | DeploymentMapProcessorFunction | adf-pipeline-management-deployment-map-processor |
370
+ | Lambda | ADFPipelineCreateOrUpdateRuleFunction | adf-pipeline-management-create-update-rule |
371
+ | Lambda | ADFPipelineCreateRepositoryFunction | adf-pipeline-management-create-repository |
372
+ | Lambda | ADFPipelineGenerateInputsFunction | adf-pipeline-management-generate-pipeline-inputs |
373
+ | Lambda | ADFPipelineStoreDefinitionFunction | adf-pipeline-management-store-pipeline-definition |
374
+ | Lambda | ADFPipelineIdentifyOutOfDatePipelinesFunction | adf-pipeline-management-identify-out-of-date-pipelines |
375
+ | -------------- | ----------------------------------------------- | -------------------------------------------------------- |
376
376
377
377
#### ADF Parameters in AWS Systems Manager Parameter Store
378
378
@@ -1208,7 +1208,7 @@ around IAM we have created two new IAM Role that lives on each AWS Account
1208
1208
within the organization. These role are created in the global.yml
1209
1209
*(base stack)* of each account and are used for the following purposes:
1210
1210
1211
- **adf -automation-role:**
1211
+ __adf -automation-role:__
1212
1212
1213
1213
> When creating pipelines in ADF there are certain things that are required to
1214
1214
> be setup on multiple different accounts. For example, the source account
@@ -1222,7 +1222,7 @@ This new role (`adf-automation-role`) is assumed by CodeBuild in the
1222
1222
` aws-deployment-framework-pipelines` pipeline exclusively and cannot be
1223
1223
assumed by the standard *(other)* deployment pipelines.
1224
1224
1225
- **adf -readonly-automation-role:**
1225
+ __adf -readonly-automation-role:__
1226
1226
1227
1227
> When CodeBuild runs as part of a standard deployment pipeline
1228
1228
> *(anything other than `aws-deployment-framework-pipelines`)* it uses the
0 commit comments