Hello Team,
When we run the below command, we are not able to see the MetadataOptions property configured for the instance:
aws cloudcontrol get-resource --type-name AWS::EC2::Instance --identifier <my-instance-id> --profile <my-profile>
Additionally, we checked the AWS::EC2::Instance registry, the MetadataOptions is not listed as a write-only property.
The WriteOnlyProperties in the schema are:
"/properties/BlockDeviceMappings/*/NoDevice",
"/properties/BlockDeviceMappings/*/VirtualName",
"/properties/LicenseSpecification",
"/properties/AdditionalInfo",
"/properties/Ipv6AddressCount",
"/properties/Ipv6Addresses",
"/properties/PropagateTagsToVolumeOnCreation",
"/properties/LaunchTemplate"
MetadataOptions is not a security property. It only defines the protocol for fetching credentials, not any related credentials, so treating it as a security property is incorrect. Hence, every field in the schema (except those marked as writeOnly) should be returned by the above command.
Hence, please consider this as a bug so that the MetadataOptions can be shown when running the above command.
Hello Team,
When we run the below command, we are not able to see the MetadataOptions property configured for the instance:
aws cloudcontrol get-resource --type-name AWS::EC2::Instance --identifier <my-instance-id> --profile <my-profile>Additionally, we checked the AWS::EC2::Instance registry, the MetadataOptions is not listed as a write-only property.
The WriteOnlyProperties in the schema are:
MetadataOptions is not a security property. It only defines the protocol for fetching credentials, not any related credentials, so treating it as a security property is incorrect. Hence, every field in the schema (except those marked as writeOnly) should be returned by the above command.
Hence, please consider this as a bug so that the MetadataOptions can be shown when running the above command.