Browsers are difficult Please wait, loading your map...
naming conventions and tagsimplementationfor naming resourceinitial thoughtsavoid using some lengthy numbers e.g. various org have some long random numbers to identify cost centretry to represent identifier in less chars.avoid using dots hypenaws s3 dot is not allowedhere we are using hyphen (-) to seperate info{resource-identifier}-{region-id}-{env}-{cost-centre}-{vpc-seq-id}-{app-service}-{resource-seq-id}exampleidentifiersresource-identifieridentify resource -eks,vpc,ecs,ec2,rds,es,apgwregion-idshort indicator forregion in aws, Azure hassimilar concept knownas locationenvcost-centrevpc-seq-idapp-serviceresource-seq-idhttps://github.com/polganesh/terraform-aws-vpcfor tagscommon problemsmany times we are providing tags externallydevelopers might miss certainimportant tags, they might missspell tagsbenefits of thisapproachdevelopers can providecommon_tags, tags forapi but at the end theycan not overridestandard tags.less chance of missingtagsfor improving securitycommon problemsmany terraform modules provide facility to provide subnetids to place our worker nodes in ECS,EKS. with this approachwe can not restrict users from creating worker nodes inpublic subnetutilizing namingconventionsref -challengesalthough it is better to have seperate cloud account but many times in real life weare running multiple projects in same cloud account (aws,azure,gcp)we might be running multiple environment of same projects in same cloud accountno indication (purpose) of resources just bylooking at nameproject nameenvironmentwho owns cost of thisresourcewhich vpc it belongshumans dont like to remember numberswe are all human. many of us staying in non engiish speaking countriesand might make small mistakes for tagstags are case sensitive. env, Env are two different tag keysthe maximum length of various cloud resources is limited e.g. AWS s3 bucket name can notbe more than 63 chars, the target group in AWS can not be more than 32 chars. it alsoindicates that we can not have lengthy fancy names. we need to represent information inprecise way possiblereferencehttps://aws.amazon.com/answers/account-management/aws-tagging-strategies/

Created using MindMup.com