Cloud Management Platform Blog (Archived) — cwilhelm (Flexera Software)
Deprecation of Cloud Management Policies
The following Flexera Cloud Management Policies have been depreciated and are no longer being updated. The policies can still be used in the Flexera NAM environment. They can also be modified as custom versions managed by customers.
For a complete list of the Flexera Policies or to access the policy templates for the deprecated policies please visit our GitHub repository .
List of deprecated Policies
- Compliance
- Disallowed Cloud Images
- Untagged Resources
- Unapproved Instance Types
- Cost
- Downsize Instances
- Running Instance Count Anomaly
- Inefficient Instance Utilization using RightLink
- Inefficient Instance Utilization using RightLink Add Tags
- Schedule Instances
- Superseded Instance Remediation
- Terminate Instances with End Date
- Discover Old Snapshots
- Unattached Volumes
- Operational
- AWS Cloud Credentials Rotation
- No Recent Snapshots
- Stranded Servers
- VMWare Instance Tag Sync
- Security
- Security Group with High Open Ports
- Security Groups with ICMP Enabled
- Security Group Rules without Description
- Security Group Rules with ports open to the world
Could you clarify what it means under Operational -> Stranded Servers?
If I'm currently expecting RightScale to auto-terminate a stranded server, will that happen?
@yesthatallen The Stranded Servers policy will terminate any of the servers that were found stranded. This only applies to servers created within the Flexera Cloud Management module.
Here is the description from the README file
What it does
This policy checks all Servers in Cloud Management and reports on any that have been stranded during the boot process. It provides the option to terminate any stranded servers after approval.