Skip to content

CloudFormation and Cloud Control API actions merged together, no CFN service showing #7

Description

@eppeters

Probably due to their sharing an IAM prefix (cloudformation), the actions for Cloud Control API and CloudFormation are both merged under the service name "Cloud Control API" in aws.permissions.cloud.

This could be an issue with the underlying dataset: https://github.com/iann0036/iam-dataset, but I'm not sure.

Note that Cloud Control API actions (e.g. CreateResource) and CloudFormation actions (e.g. CancelUpdateStack) show up on the below page and that no CloudFormation service is listed:

image

Impact: hard to find CloudFormation actions without using the search functionality and can be confusing.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions