Skip to content

fix(infra): add ProjectId tags to fcknat CFN template - #3

Open
ellen-goc wants to merge 1 commit into
mainfrom
fix/388-cfn-projectid-tags
Open

fix(infra): add ProjectId tags to fcknat CFN template#3
ellen-goc wants to merge 1 commit into
mainfrom
fix/388-cfn-projectid-tags

Conversation

@ellen-goc

Copy link
Copy Markdown

Summary

  • Adds ProjectId: kippo, Project: kippo, and Environment tags to all resources in conf/aws/fcknat.cfn.yaml
  • ASG tags use PropagateAtLaunch: true so EC2 NAT instances inherit tags
  • Adds Environment parameter (default dev) for environment-scoped tagging

Why

EC2 NAT instances and related resources created by this template were appearing as (untagged) in AWS Cost Explorer. This blocked attribution to the kippo project in the weekly cost report.

Resources now tagged

  • FckNatInterfaceA / FckNatInterfaceB (NetworkInterface)
  • FckNatAsgA / FckNatAsgB (AutoScalingGroup + propagate to EC2 instances)
  • NatSecurityGroup (SecurityGroup)
  • NatRole (IAM Role)

Test plan

  • Deploy stack to dev: aws cloudformation deploy --template-file conf/aws/fcknat.cfn.yaml --stack-name kippo-dev-fcknat ...
  • Verify EC2 instance has ProjectId=kippo tag in AWS console

Adds ProjectId, Project, and Environment tags to all resources:
NetworkInterfaces, AutoScalingGroups (with PropagateAtLaunch), SecurityGroup,
and IAM Role. ASG tags propagate to EC2 NAT instances at launch.

Also adds Environment parameter (default: dev) to allow environment-scoped
tagging when deploying to staging/prod.

Fixes monkut#388

@ellen-goc ellen-goc left a comment

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Review — kippo#3 (ProjectId tags on fcknat CFN)

Verdict: Approve (comment — self-authored, cannot self-approve).

  • Adds ProjectId/Project/Environment tags to both FckNatInterface ENIs and the ASG (PropagateAtLaunch: true so NAT EC2 instances inherit them). This is exactly the cost-allocation-tag coverage the org is standardizing on.
  • New Environment parameter (default dev, constrained AllowedValues) is env-scoped and safe.
  • No hardcoded account IDs, ARNs, or secrets; template-only change. Structurally valid CFN.

CI: no checks configured on this repo; mergeStateStatus=CLEAN. Ready for human merge.

@ellen-goc ellen-goc added the ellen:awaiting-merge Ellen has approved — awaiting human merge label Jul 22, 2026
@ellen-goc

Copy link
Copy Markdown
Author

✅ CI green — Slack notification sent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ellen:awaiting-merge Ellen has approved — awaiting human merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant