There are two configurations on General.
Application-wise monthly budget
Enabling Application-wise monthly budget setting will enforce user to link an Environment to Application and will trigger an Alarm whenever monthly estimated cost within the application is crossing the budget. Applications allow you to configure access and budgets.
To open Naming Conventions settings, click on Disabled > or Enabled >. It depends on which status has already set.
With Service Naming Conventions, you can define the default names for services to be used while creating an environment from a template. A number will be incremented to the service where specified by a # (or ##/###/#### - depending on number of digits you wish to use).
There is a role available under Access Management which exempts a user from it's use. (Access Management: Exceptions: Naming Conventions).
Enabling Naming Convention setting will help you to apply different naming standards for each service and will auto-assign those while creating service from build/manage page.
You can use Application/Tag Variable in naming conventions.
When you use “$$” before the name of a Tag pre-defined, your Naming Conventions will check on tag’s values and use the content before | (vertical bar).
When you use “##” represents an incremental integer applied to each variable (you can use only one incremental for a service type, all other occurrences will be treated as normal text).
With Free Text enabled will possibly set different names.
You can create these variables on Tagging section, for example:
win2012 | Windows 2012
win2016 | Windows 2016
ubu1610 | Ubuntu Server 16.10
rhel7 | Red Hat Enterprise Linux 7
deb8 | Debian 8
pub | Public
priv | Private
prod | Production
stg | Staging
dev | Development
appx | Application X
appy | Application Y
appz | Application Z
websvr | Web Server
db | Database
mid | Middleware
mysql57 | MySQL 5.7
orase1 | Oracle Database Standard Edition One
mssqlent | Microsoft SQL Enterprise Edition
mssqlstd | Microsoft SQL Standard Edition
The content before | (vertical bar) will be used for Naming Convention.
The content after | (vertical bar) will be used for Tagging in drop-down menu.
Additional Variables Supported
Naming Conventions: Added support for RDS and EBS snapshots and Private AMI’s.
In addition to the existing Naming Convention / Tagging variables, we’ve added the following variables for Volumes, EBS and RDS Snapshots.
When completed as part of an automated policy, they will be prefixed with “a_”.
|%username%||Username of current logged in user.|
|%soename%||Display name of AMI added via SOE OS’s module.|
|%soeconfiguration%||Display name of AMI added via SOE OS’s module.|
|%templatename%||Configuration name of AMI added via SOE OS’s (being used on build).|
|%templateversion%||Version of template.|
|%environmentname%||Name of environment.|
|%hostname%||Hostname of attached Server.|
|%hostname%||Hostname of attached Server. (of Volume).|
|%volumename%||Volume name that snapshot was taken from.|
|%dbname%||RDS name that snapshot was taken from.|
|%currentdate%||Date at time of SnapShot.|
Use the check box Enable Naming Conventions to enable or disable it.
Use the text box Configuration to specify a name for the service, Variables and ## are supported.
Free Text- Allows user to enter free text by the end of service name on Build / Manage.
After your settings click on Save to finish.
You will receive a confirmation message about this action.