Update mappings for some cloudformation, s3, cloudfront, sqs and cloudwatchlogs operations #32
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivations
Over the last half year, we did a number of changes for the IAM dataset, due to diverse user bug reports or more testing in LocalStack.
With this PR, I want to upstream our changes as much as possible.
Changes
StackName
parameter in cloudformation generally also accepts theStackId
: https://docs.aws.amazon.com/AWSCloudFormation/latest/APIReference/API_DescribeStacks.html . Often stack id only for deleted stacks, and stack name or id for active stacks. We have to strip everything but the arn for the resource rendering to yield correct resultsCreateDistributionWithTags
also uses thecloudfront:CreateDistribution
IAM actionDeleteBucketOwnershipControls
operations uses thes3:PutBucketOwnershipControls
action, similar forDeleteBucketIntelligentTieringConfiguration