piotr-rzepa / cloud-resume-challenge Goto Github PK

Automate deployment of AWS resources from building & deploying SAM Template to Initializing, Planning and Applying Terraform configuration file.

The environment for automatic deployment is GitHub Actions workflow pipeline in .github/workflows/pipeline.yaml

Update following sections:

1. Personal projects - Mention kubernetes-flask personal project
2. Technical skills - Mention skills such as K8s, Terraform, Terragrunt, Rancher, ArgoCD, Datadog
3. Work experience - Add new/Edit existing section to introduce recently gained skills
4. Certificates - Remove CPA for SAA-C03 or SOA-C02) (if passed)

Use AWS CLI to verify, if bucket desired for storing the Terraform state file exists (by default, it should exist).

If the bucket is nowhere to be found, create a bucket with name (przepk-cloud-resume-challenge-terraform-state)
If the bucket already exists, continue with the pipeline.

Possible command to verify the bucket exists: aws s3api head-bucket --bucket <bucket_name>
Possible command to create the bucket: aws s3api create-bucket --bucket <bucket_name> --region <aws_region>

Make use of media queries to allow seeing the website on multiple devices

Terragrunt - https://terragrunt.gruntwork.io/

Use Terragrunt wrapper to modularize, simplify and structurize the Terraform's remote state configuration

Instead of relying on Terraform AWS resources, use modules to simplify infrastructure provisioning and reduce code
Examples:

• AWS API Gateweway module: https://registry.terraform.io/modules/terraform-aws-modules/apigateway-v2/aws/latest (already integrated)
• AWS Lambda module: https://registry.terraform.io/modules/terraform-aws-modules/lambda/aws/latest

For some reason, the plan generated using Terragrunt is not correctly displayed in the comment(s) added by github-actions.
The same issue occurs for validation output, as can be seen below:

Create CloudWatch alarm(s) for monitoring and alerting when various metrics exceed their thresholds.
Metrics to consider:

• Response time (latency) of Api Gateway degrades
• Number of Lambda invocations in given timespan is unsually large
• Lambda function exists with an error

Additionally, a SNS topic can be created to send an account owner email informing about the issues.

Migrate the Infrastructure as Code setup from SAM Template to Terraform.
Points to consider:

• How is the automatic packaging/archiving of Lambda source (Python code, requirements.txt) handled in Terraform?
• What would be good output values from Terraform resources?
  • CloudFront URL
  • CloudFront Distribution ID (for invalidating the cache)
  • API Gateway URL
  • others?
• Summarize differences between CloudFormation/SAM Template and Terraform - Which is easier to use / easier to migrate to?

Integrate following tools into CI/CD chain:

• TFLint for linting Terraform syntax and finding provider-related errors
• Terrascan for static code analysis of IaC code
• Checkov for static code analysis of IaC code
• (Optional) terraform-compliance for imposing security standards and best practices using BDD