Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Parameter NoEcho used with resource primary identifiers #3066

Open
2 tasks done
kddejong opened this issue Feb 21, 2024 · 0 comments
Open
2 tasks done

Parameter NoEcho used with resource primary identifiers #3066

kddejong opened this issue Feb 21, 2024 · 0 comments
Labels
v1 v1.X

Comments

@kddejong
Copy link
Contributor

Is this feature request related to a new rule or cfn-lint capabilities?

rules

Describe the feature you'd like to request

We strongly recommend against including NoEcho parameters, or any sensitive data, in resource properties that are part of a resource's primary identifier.

When a NoEcho parameter is included in a property that forms a primary resource identifier, CloudFormation may use the actual plaintext value in the primary resource identifier. This resource ID may appear in any derived outputs or destinations.

To determine which resource properties comprise a resource type's primary identifier, refer to the resource reference documentation for that resource. In the Return values section, the Ref function return value represents the resource properties that comprise the resource type's primary identifier.

Describe the solution you'd like

warn if a NoEcho parameter is used in the primary identifier of a resource

Additional context

No response

Is this something that you'd be interested in working on?

  • 👋 I may be able to implement this feature request

Would this feature include a breaking change?

  • ⚠️ This feature might incur a breaking change
@kddejong kddejong added the v1 v1.X label Feb 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v1 v1.X
Projects
None yet
Development

No branches or pull requests

1 participant