This project helps to practice skills with Infrastructure as a code using cloudformation.
-
AWS CloudFormation is a service that helps you model and set up your Amazon Web Services resources so that you can spend less time managing those resources and more time focusing on your applications that run in AWS. You create a template that describes all the AWS resources that you want (like Amazon EC2 instances or Amazon RDS DB instances), and AWS CloudFormation takes care of provisioning and configuring those resources for you. You don't need to individually create and configure AWS resources and figure out what's dependent on what; AWS CloudFormation handles all of that. The following scenarios demonstrate how AWS CloudFormation can help.
• CloudFormation is a declarative language, not an imperative language.
• CloudFormation handles resource dependencies, so that you don’t have to specify which resource to start up before another. There are cases where you can specify that a resource depends on another resource, but ideally, you’ll let CloudFormation take care of dependencies.
With the right template, you can deploy at once all the AWS resources you need for an application. In this section, you'll examine a template that declares the resources for deploying high availability web app
- Diagrams are a very important starting point for planning your cloud infrastructure. DevOps engineers start with a visual representation of the required cloud infrastructure before they turn it into code.
- AWS Account
- Visual Studio
- AWS CLI
- python
- YAML
- JSON
- Shell Script
Configure AWS CLI with user key for programmatic access:
aws configure
AWS Access Key ID [None]:
AWS Secret Access Key [None]:
Default region name [None]:
Default output format [None]:aws --version
aws-cli/1.17.9 Python/3.6.0 Windows/10 botocore/1.14.9- Create Stack
$ aws cloudformation create-stack --stack-name <stackname> \
--template-body file://<stackyamlfile> \
--parameters file://<parameterjsonfile> - Update Stack
$ aws cloudformation update-stack --stack-name <stackname> \
--template-body file://<stackyamlfile> \
--parameters file://<parameterjsonfile>- Log information for UserData scripts is located in this file: cloud-init-output.log under the folder: /var/log.
* create.sh ==> Script to create new cloudformation stack. Requires following arguments in order:
./create.sh <stack name> <YAML template file name> <JSON Parameter file name>
* update.sh ==> Script to update the cloudformation stack. requires following arguments in order:
./update.sh <stack name> <YAML template file name> <JSON Parameter file name>
-
Create Network Stack using Network Stack files
1a. network.parameters.json ==> parameter file for cloudformation stack to create network components.
1b. network.yml ==> cloudformation yaml file to create the network stack ( VPC, subnets, NAT gateway, Internet Gateway)
-
create Server Stack using Server stack files
2a. server-parameters.json ==> parameter file tfor cloudformation stack to create infrastructure.
2b. servers.yml ==> cloudformation yaml file to create infrastructure stack ( Security group, Instances, Load Balancer, Bastion host, Auto Scale, Listener, listener rule, targets)
To Use IAMInstance profile with EC2 Instance for accessing AWS Resource like S3: use below create stack command with --capabilities argument
$ aws cloudformation create-stack --stack-name webappserverstack \ --template-body file://servers.yml \ --parameters file://server-parameters.json --capabilities CAPABILITY_IAM
Command line
aws s3 cp <file name> <link to S3 bucket> This line above copies a file from your local machine to the S3 bucket
• You'll want your data to persist even if your stack of resources is updated or deleted. • Retention policy: keeps a service even if the entire stack of infrastructure is marked for removal. In CloudFormation, the syntax is DeletionPolicy: retain. This is very useful to assign to your data storage (database, file storage), to make sure that your data is saved even when the stack is updated or deleted.