DNS Records MUST adhere to the following pattern
instanceSHALL be used in the case that there are multiple instances of an aws_service, e.g. seperate databases.
aws_serviceMUST refer to the specific AWS service that is being used, the correct name of a AWS service MUST be as specified as in the Boto3 Library.
azOPTIONALLY can refer to a specific Availability Zone. This may indicate a design problem in the service.
regionOPTIONALLY can refer to a specific region.
serviceMUST refer to the specific service.
environmentMUST refer to the environment the service is deployed into (
namespaceMUST be a valid TLD.
Example DNS Records:
Object Names in AWS¶
- The name of an Object in AWS must convey the same information at the DNS record, however availability zone and region SHOULD NOT be included as this information is conveyed by interaction with the object.
- The Object name is ordered naturally so that it is read from left to right (inverse of the DNS name).
- By convention the namespace is assumed to be the standard TLD. Exceptions MAY be made for third party services.
- Objects MUST be UpperCamelCase and acronyms MUST be Capitalised.
Example Object Names:
EnvironmentExampleServiceRDSExampleDB EnvironmentSecondServiceElastiCache ThirdPartyLiveMonitoringEC2