aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap
[AWS::SmsVoice::ProtectConfiguration] - [Coverage] - Add support for Associations (Account Default)
- Dominant language
- No language data
- Stars
- 1.1k
- Forks
- 62
- PR merge metrics
- No merged PRs in 30d
Description
### Name of the resource
Other
### Resource name
AWS::SmsVoice::ProtectConfiguration
### Description
I am using an SMS protect configuration in AWS end user messaging in order to protect my application against SMS pumping attacks (see [this aws article](https://aws.amazon.com/blogs/messaging-and-targeting/defending-against-sms-pumping-new-aws-features-to-help-combat-artificially-inflated-traffic/)). In order for the protect configuration to get applied to general AWS services like Cognito (SMS for registration or "forgot password" feature), one needs to make the protection configuration the AWS Account default.
In AWS console, this is is done by editing the protection configurations associations:
Unfortunately, I am not able to edit / add these associations via CloudFormation. As a consequence, it is not possible to set these via terraform neither.
Please provide resp. attributes in Cloudformation for the resource AWS::SmsVoice::ProtectConfiguration.
Thanks, Nils
### Other Details
_No response_
Contributor guide
Research direction
Start with the coverage implementation for AWS::SmsVoice::ProtectConfiguration and the AWS documentation for protection-configuration associations. Determine the CloudFormation properties needed to manage account-default associations, then verify create and update behavior for the resource and its use by services such as Cognito.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100