aws-cloudformation / aws-cloudformation/cloudformation-coverage-roadmap

Pseudo parameter for account email

Open
#1,806 0 comments 0 reactions 0 assignees View on GitHub
enhancement
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::AccountEmail

### Description

There are some use cases where knowing the account email would be helpful, for example when creating a [cost anomaly subscription](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-properties-ce-anomalysubscription-subscriber.html).

The absence of a pseudo parameter means one has to add a parameter to the template, and although the parameter can have an `AllowedPattern` to ensure the value is correct, it's still prone to human error.

Having `AWS::AccountEmail` return the account's email address would help here. It would operate similar to [`AWS::AccountId`](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/pseudo-parameter-reference.html#cfn-pseudo-param-accountid).

### Other Details

_No response_

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the AWS::AccountId entry in the linked CloudFormation pseudo-parameter reference and the cost anomaly subscription documentation. Confirm the proposed AWS::AccountEmail behavior and its constraints, then determine what CloudFormation coverage or design work is needed; done means the pseudo parameter is supported and documented for templates.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.