...
Note: An upgrade could fail if the name of an existing extensible attribute matches the name of any of the cloud extensible attribute for a different object type. You must define values for all required cloud extensible attributes in a cloud API request.
...
| Anchor | ||||
|---|---|---|---|---|
|
You can define metadata in the form of tags for AWS and Azure which are captured through a vDiscovery process and you can save the tags as extensible attributes in NIOS. You can use predefined attributes or create your own tags that consists of an user-defined key and an optional value. The tag values defined in AWS and Azure are translated into corresponding extensible attribute values in NIOS.
...
Table 7.11 Tag Translation
| AWS Object | Azure Object | NIOS Object |
|---|---|---|
| EC-2 Instance | Virtual Machine | VM |
| Interface | Virtual Interface | Managed private IP address: Any DNS record, fixed address, or reservation associated with that IP address. |
| Interface (tags are the same for private IP address and public IP address of the same interface) | Public IP address (Public IP address has specific tags in Azure) | Managed public IP address: Any DNS record, fixed address, or reservation associated with the IP address. |
| VPC | Virtual Network | VPC |
| Subnet | Subnet (no tags for subnet in Azure) | Network |
...
Note: NIOS generates alert messages about tags that are translated and tags that are skipped due to missed extensible attributes or incorrect extensible attributes types will be displayed in the syslog and infoblox.log file.
...