AWS CloudFormation Typical CodePipeline-Based Service Project: Difference between revisions
| (9 intermediate revisions by the same user not shown) | |||
| Line 15: | Line 15: | ||
Template is ready. | Template is ready. | ||
Template example: {{External|[https://github.com/ovidiuf/playground/blob/master/amazon/cloudformation/codepipeline-based-template/codepipeline-based-template.yaml | Template example: {{External|[https://github.com/ovidiuf/playground/blob/master/amazon/cloudformation/codepipeline-based-template/codepipeline-based-template.yaml codepipeline-based-template.yaml ]}} | ||
===Specify template=== | ===Specify template=== | ||
Upload a template file. | Upload a template file. | ||
==Specify stack details== | |||
===Stack Name=== | |||
themyscira-cicd | |||
Avoid using "-stack" in the name as some templates may use "AWS::StackName" to compose other names. | |||
The rest of the page is dynamically build based on the "[[AWS_CloudFormation_Concepts#Input_Parameters|Parameters]]" and "[[AWS_CloudFormation_Concepts#Metadata|Metadata]]" sections of the template. | |||
==Configure stack options== | |||
===Tags=== | |||
===Permissions=== | |||
Allows choosing an IAM role that defines how CloudFormation can create, modify or delete resources. If no role is chosen, CloudFormation uses permissions based on the user credentials. | |||
See: {{Internal|AWS_CloudFormation_Concepts#CloudFormation_Service_Role|CloudFormation Service Role}} | |||
==Advanced Options== | |||
===Stack policy=== | |||
Defines the resources that you want to protect from unintentional updates during a stack update. | |||
===Rollback configuration=== | |||
===Notification options=== | |||
===Stack creation options=== | |||
====Rollback on failure==== | |||
====Termination protection==== | |||
=Post-Creation= | |||
The resources that are created as part of the stack creation can be inspected in the "Resources" tab. | |||
Latest revision as of 19:25, 13 March 2019
Internal
Overview
This example walks the reader through the steps required to create the AWS infrastructure for a CodePipeline-based service project.
Procedure
Create Stack
Prerequisite - Preparte template
Template is ready.
Template example:
Specify template
Upload a template file.
Specify stack details
Stack Name
themyscira-cicd
Avoid using "-stack" in the name as some templates may use "AWS::StackName" to compose other names.
The rest of the page is dynamically build based on the "Parameters" and "Metadata" sections of the template.
Configure stack options
Tags
Permissions
Allows choosing an IAM role that defines how CloudFormation can create, modify or delete resources. If no role is chosen, CloudFormation uses permissions based on the user credentials.
See:
Advanced Options
Stack policy
Defines the resources that you want to protect from unintentional updates during a stack update.
Rollback configuration
Notification options
Stack creation options
Rollback on failure
Termination protection
Post-Creation
The resources that are created as part of the stack creation can be inspected in the "Resources" tab.