Browsers are
difficult
Please wait, loading your map...
naming conventions and tags
implementation
for naming resource
initial thoughts
avoid using some lengthy numbers e.g. various org have some long random numbers to identify cost centre
try to represent identifier in less chars.
avoid using dots hypen
aws s3 dot is not allowed
here we are using hyphen (-) to seperate info
{resource-identifier}-{region-id}-{env}-{cost-centre}-{vpc-seq-id}-{app-service}-{resource-seq-id}
example
identifiers
resource-identifier
identify resource -
eks,vpc,ecs,ec2,rds,es,apgw
region-id
short indicator for
region in aws, Azure has
similar concept known
as location
env
cost-centre
vpc-seq-id
app-service
resource-seq-id
https://github.com/polganesh/terraform-aws-vpc
for tags
common problems
many times we are providing tags externally
developers might miss certain
important tags, they might miss
spell tags
benefits of this
approach
developers can provide
common_tags, tags for
api but at the end they
can not override
standard tags.
less chance of missing
tags
for improving security
common problems
many terraform modules provide facility to provide subnet
ids to place our worker nodes in ECS,EKS. with this approach
we can not restrict users from creating worker nodes in
public subnet
utilizing naming
conventions
ref -
challenges
although it is better to have seperate cloud account but many times in real life we
are running multiple projects in same cloud account (aws,azure,gcp)
we might be running multiple environment of same projects in same cloud account
no indication (purpose) of resources just by
looking at name
project name
environment
who owns cost of this
resource
which vpc it belongs
humans dont like to remember numbers
we are all human. many of us staying in non engiish speaking countries
and might make small mistakes for tags
tags are case sensitive. env, Env are two different tag keys
the maximum length of various cloud resources is limited e.g. AWS s3 bucket name can not
be more than 63 chars, the target group in AWS can not be more than 32 chars. it also
indicates that we can not have lengthy fancy names. we need to represent information in
precise way possible
reference
https://aws.amazon.com/answers/account-management/aws-tagging-strategies/
×
Created using
MindMup.com