aws-sts-gap

To analyze AWS STS IAM policy gaps between OpenShift versions, you can run a script that compares policies at the action and service levels. It flags unexpected permission changes in managed-cluster-config and generates detailed HTML and JSON reports.

AWS STS IAM policy gaps are missing, removed, or changed permissions between OpenShift versions. Identifying them before an upgrade ensures your cluster has the necessary IAM permissions correctly configured to avoid deployment failures.

Yes, comparing AWS STS policies requires Python3, the oc CLI, jq, and PyYAML. These dependencies are necessary to parse policy data and generate the final HTML and JSON gap analysis reports.

You can check for unexpected permission changes in managed-cluster-config by running an automated gap analysis. The process evaluates policy actions and services across OpenShift versions, highlighting any unexpected permission modifications in its report.

The best way to generate an IAM policy difference report is to use an automated analysis script that compares STS policies across versions. This approach produces comprehensive HTML and JSON outputs detailing new, removed, or changed permissions.

Yes, you can generate an HTML report of AWS STS permission changes for OpenShift. The analysis script outputs both HTML and JSON formats, providing a comprehensive view of action-level and service-level policy differences between versions.