This repository contains a collaboration of general and specific Amazon Web Services CloudFormation Template Examples. The basic design is a layered approach so there is less repeat content between all the templates. That way you can build a custom environment by picking the solution templates you wish to use. In other words you won't see a VPC created over and over throughout the templates. You simply use the VPC template then move to the next piece you would like to create.
Also, The general design leans towards not having to refactor the template to fit your account/environment. By using the configured parameters from the console or CLI you should be able to use the template without the need to edit it. The templates generally output all the information you may need for another template. So, be sure to examine the Outputs tab after creating the stack.
The AWS CLI examples can be dropped in a shell script and/or added to your CI/CD solution to spin up solutions in a fully automated fashion. Of course logic around updating stacks, deleting and checking for success/failure should be addressed.
With a simple shell script and a customized parameter json file you can spin up stacks quickly and consistently. Furthermore it's just as easy to tear a CloudFormation stack versus if all the objects where created manually.
One template to rule them all... These are master templates that call nested templates. These are good to build out a full environment without having to run each template individually. Coupled with a custom parameters JSON file can give you a one command solution to a complex setup and eliminate the need to duplicate code.
For instance you could have a VPC, NAT, RDS and Autoscaling Webapp behind an ELB and Update DNS all in one command using various foundational templates that I've creates to be used together.
|
Select the foundational pieces for building out an infrastructure from the ground up.
|
|
||||
|
Creates an entire VPC from scratch for Lab or Permanent.
|
|
||||||
|
Creates a NAT Gateway on an existing VPC with Public (IGW) and Private subnets. Private route table is updated to route traffic to the NAT gateway a Public subnet that has an Internet Gateway Attached.
|
|
||||||
|
Creates a Site-to-Site BGP VPN Connection in and existing VPC with public and/or private networks. There is an option to not exclude allowing VPN access to the public networks. Simply select false for the 'Include Public Subnets', leave default value in Public Network ACL and Route Table. The values will just be ignored. This only sets up the AWS side of the VPN. After the CloudFormation creates the objects you'll then need to configure your remote VPN Device. Here's an article that gives the configuration steps for configuring a Sophos UTM v9 VPN endpoint. This assumes that the Private Network ACL allows all outbound. Lastly, the Private Network ACL inbound is updated to allow the remote network block specified.
|
|
||||||
|
Creates a single Bastion host on a Public subnet in an existing VPC. Select from either a RHEL, Ubuntu or Windows OS.
|
|
||||
|
Create EC2 Single Proxy Instance
|
|
||
|
Creates an Elastic File System with 3 Mounts
|
|
||
|
Create S3 Backup Bucket
|
|
||
|
Creates a MySQL RDS Database Instance.
|
|
||
|
Creates an RDS Instance From Snapshot. Can be great for Blue/Green or pull Prd DB to Nonprod for testing.
|
|
||
|
Create an Autoscaling group in 3 private subnets from a baked AMI, an Elastic Load Balancer in 3 public subnets and S3 ELB Logging Bucket. Option to use SSL/TLS on ELB. Option to update Route 53 Hosted DNS alias to point to the ELB. Setup to add RDS Access Security Group. Does not create an RDS Instance. Use an RDS Instance Cloudformation Template first.
|
|
||||
|
Automates the integration between AWS Lambda and CodePipeline
|
|
||||
|
Creates a Bitbucket Server in a private or public subnet in an existing VPC.
|
|
||||
|
Creates a Chef Complianc Web server in a Public Subnet with Internet Gatewayy attached on an existing VPC. It then attaches an EIP and finally adds the instance to an existing instance-to-instance security group.
|
|
||||
|
Automates the integration between AWS CodeBuild, CodeCommit, CodeDeploy, and CodePipeline
|
|
||||||
|
Automates the integration between AWS CodeCommit and CodePipeline
|
|
||||
|
Adds a Manual Approval to a CodePipeline
|
|
||||||
|
Containerized CI Solutions in AWS: Jenkins in ECS
|
|
||||
|
Automates the integration between EC2 Container Service (ECS), EC2 Container Registry (ECR), CodeCommit, and CodePipeline
|
|
||||
|
Automates the integration between AWS Elastic Beanstalk and CodePipeline
|
|
||||
|
Create S3 Backup Bucket
|
|
||
|
Creates a deployment pipeline in AWS CodePipeline using a pre-built Lambda function. It can be used to model a pipeline without initial implementation
|
|
||||
|
Automates the integration between AWS OpsWorks, CodeCommit and CodePipeline
|
|
||||
|
Creates an S3 bucket to host a single-page application and a continuous delivery pipeline with CodeBuild and CodePipeline.
|
|
||
|
Creates three test instances in an existing VPC. Each instance is a different operating system. They are; Red Hat Enterprise Linux 7, Ubuntu 14 and Windows 2012 R2.
|
|
||||
|
Create S3 Backup Bucket
|
|
||