-
Notifications
You must be signed in to change notification settings - Fork 226
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
47 changed files
with
1,109 additions
and
384 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -59,7 +59,6 @@ pipelines: | |
type: cc-cloudformation | ||
params: | ||
- SourceAccountId: 111111111111 | ||
- NotificationEndpoint: [email protected] # You will receive a confirmation email | ||
- RestartExecutionOnUpdate: True | ||
targets: | ||
- path: /banking/testing | ||
|
@@ -69,7 +68,7 @@ pipelines: | |
regions: us-west-2 | ||
``` | ||
The *SourceAccountId* will be the Account Id of the account we created in the `banking/source` OU and *NotificationEndpoint* will be an email address of the pipeline owner/team. In this pipeline we have specified we want to deploy to two different regions as part of the stages. If you wish to deploy to the *"default"* region *(the one your deployment account is setup globally in)* you can omit the region and path keys as you will see below with our ECR Repository deployment. | ||
The *SourceAccountId* will be the Account Id of the account we created in the `banking/source` OU. In this pipeline we have specified we want to deploy to two different regions as part of the stages. If you wish to deploy to the *"default"* region *(the one your deployment account is setup globally in)* you can omit the region and path keys as you will see below with our ECR Repository deployment. | ||
|
||
Once we have updated our deployment map we can push these changes to the `aws-deployment-framework-pipelines` repository in the Deployment Account. | ||
|
||
|
@@ -127,7 +126,6 @@ We can extend our `deployment_map.yml` file to include the new pipeline, *(remeb | |
type: cc-cloudformation | ||
params: | ||
- SourceAccountId: 111111111111 | ||
- NotificationEndpoint: [email protected] | ||
targets: | ||
- /deployment | ||
``` | ||
|
@@ -159,7 +157,6 @@ Let's add in our ECS Cluster pipeline to our Deployment Map. | |
type: cc-cloudformation | ||
params: | ||
- SourceAccountId: 111111111111 | ||
- NotificationEndpoint: [email protected] | ||
targets: | ||
- path: /banking/testing | ||
regions: eu-west-1 | ||
|
@@ -182,7 +179,6 @@ Let's add the pipeline we need into the map once more. | |
type: cc-cloudformation | ||
params: | ||
- SourceAccountId: 111111111111 | ||
- NotificationEndpoint: [email protected] | ||
- Image: aws/codebuild/docker:18.09.0 | ||
targets: | ||
- path: /banking/testing | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -44,7 +44,7 @@ pipelines: | |
regions: [ eu-west-1, eu-central-1 ] | ||
params: | ||
- SourceAccountId: 8888877777777 | ||
- NotificationEndpoint: [email protected] | ||
- NotificationEndpoint: channel1 | ||
targets: | ||
- ou-12341 | ||
- 22222222222 | ||
|
@@ -54,6 +54,8 @@ In the above example we are creating two pipelines. The first one will deploy fr | |
|
||
The second example is a simple example that deploys to an OU using its OU identifier number `ou-12341`. You can chose between a absolute path *(as in the first example)* in your AWS Organization or by specifying the OU ID. The second stage of this pipeline is simply an AWS Account ID. If you have a small amount of accounts or want to one of deploy to a specific account you can use an AWS Account Id if required. | ||
|
||
In this second example, we have defined a channel named `channel1` as the *NotificationEndpoint*. By doing this we will have events from this pipeline reported into the Slack channel named *channel`*. In order for this functionality to work as expected please see [Integrating Slack](./admin-guide/integrating-slack) | ||
|
||
If you decide you no longer require a specific pipeline you can remove it from the deployment_map.yml file and commit those changes back to the *aws-deployment-framework-pipelines* repository *(on the deployment account)* in order for it to be cleaned up. The resources that were created as outputs from this pipeline will **not** be removed by this process. | ||
|
||
## adfconfig | ||
|
@@ -95,7 +97,7 @@ The Regions specification plays an important role in how your Deployment Framewo | |
|
||
Config has three components in `main-notification-endpoint`, `moves` and `protected`. | ||
|
||
- **main-notification-endpoint** is the main notification endpoint for the bootstrapping pipeline and deployment account pipeline creation pipeline. This value should be a valid email address that will receive updates to the CodeCommit repository and CodePipeline associated with bootstrapping and creation/updating of all pipelines throughout your organization. | ||
- **main-notification-endpoint** is the main notification endpoint for the bootstrapping pipeline and deployment account pipeline creation pipeline. This value should be a valid email address or [slack](./admin-guide/#integrating-slack) channel that will receive updates about the status *(Success/Failure)* of CodePipeline that is associated with bootstrapping and creation/updating of all pipelines throughout your organization. | ||
- **moves** is configuration related to moving accounts within your AWS Organization. Currently the only configuration options for `moves` is named *to-root* and allows either `safe` or `remove_base`. If you specify *safe* you are telling the framework that when an AWS Account is moved from whichever OU it currently is in, back into the root of the Organization it will not make any direct changes to the account. It will however update any AWS CodePipeline pipelines that the account belonged to so that it is no longer a valid target. If you specify `remove_base` for this option and move an account to the root of your organization it will attempt to the base CloudFormation stacks *(regional and global)* from the account and then update any associated pipeline. | ||
- **protected** is a configuration that allows you to specify a list of OUs that are not configured by the AWS Deployment Framework bootstrapping process. You can move accounts to the protected OUs which will skip the standard bootstrapping process. This is useful for migrating existing accounts into being managed by The ADF. | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.