AWS::SNS::Topic is missing in the list of AWS Config resource types
See original GitHub issueHello!
AWS Config supports SNS Topics, but AWS::SNS::Topic
is currently missing in the AWS Config service JSON as a supported resource type:
https://github.com/boto/botocore/blob/develop/botocore/data/config/2014-11-12/service-2.json#L5972
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Supported Resource Types - AWS Config
AWS Config supports the following AWS resources types and resource relationships. Some regions support a subset of these resource types.
Read more >Release Notes - Fugue Documentation
Fugue now supports the AWS.Account.AlternateContact resource type, which will enable rules for checking whether an AWS account has the appropriate security, ...
Read more >Firehose - Turbot
This completes the AWS configuration and Turbot Workspace configuration. ... The resource notification type aggregates resource_created , resource_updated ...
Read more >Using AWS CloudWatch | Crosswalk - Pulumi
Configuring CloudWatch Logging. You can use Amazon CloudWatch Logs to monitor, store, and access your log files from Amazon Elastic Compute Cloud (Amazon...
Read more >Features Introduced in May 2021 - Palo Alto Networks
config from cloud.resource where cloud.type = 'aws' AND api.name ... AWS SNS topic not configured with secure data transport policy—.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
It got added in today’s release here https://github.com/boto/botocore/blob/develop/botocore/data/config/2014-11-12/service-2.json#L6076
Please use the latest botocore version for this. I am closing this issue as it has been fixed.
Excellent!