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

[AWS::IAM::SAMLProvider] - [BUG] - resources don't receive the `aws:cloudformation:*` built-in tags / default service-managed auto-tags

Open
#2,550 0 comments 1 reaction 0 assignees View on GitHub
bug
Dominant language
No language data
Stars
1.1k
Forks
62
PR merge metrics
No merged PRs in 30d

Description

### Name of the resource

AWS::IAM::SAMLProvider

### Resource Name

_No response_

### Issue Description

To find the right CloudFormation Stack, where a AWS resource is defined/maintained `aws:cloudformation:*` built-in tags are needed. This is an important function in day-to-day business for customers.

### Expected Behavior

Resources with type `AWS::IAM::SAMLProvider`, which are managed as CloudFormations Stacks, should automatically receive the `aws:cloudformation:*` built-in tags / automatic default CFN AutoTags.

### Observed Behavior

When you have an `AWS::IAM::SAMLProvider` resource in your stack, it does not get the built-in tags assigned:

- `aws:cloudformation:stack-name`
- `aws:cloudformation:logical-id`
- `aws:cloudformation:stack-id`

### Test Cases

```yaml
Resources:
SAMLProvider:
Type: AWS::IAM::SAMLProvider
```

### Other Details

_No response_

Contributor guide

Open the contributing guide

Research direction

Start with the YAML reproduction for AWS::IAM::SAMLProvider and investigate how CloudFormation assigns built-in tags to managed resources. Confirm the behavior for the listed stack-name, logical-id, and stack-id tags; done means this resource receives all three tags when deployed in a stack.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws
Domain
cloud
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.