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

[Enhancement]: Set Private Key as Sensitive for aws_sesv2_email_identity on Plans #33333

Closed
danhlee329 opened this issue Sep 6, 2023 · 5 comments
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/sesv2 Issues and PRs that pertain to the sesv2 service.

Comments

@danhlee329
Copy link

Description

When looking at the plan for aws_sesv2_email_identity, I see the private key as plain text, this should ideally be shown as (sensitive):

# aws_sesv2_email_identity.byodkim_domain will be created
resource "aws_sesv2_email_identity" "byodkim_domain" {
    arn                         = (known after apply)
    email_identity              = "testdomain.domain"
    id                          = (known after apply)
    identity_type               = (known after apply)
    tags_all                    = (known after apply)
    verified_for_sending_status = (known after apply)

    dkim_signing_attributes {
        current_signing_key_length    = (known after apply)
        domain_signing_private_key    = "MIIEvwIBADA...." # shown as plain text, shortened for display
        domain_signing_selector       = "testselector._domainkey.testdomain"
        last_key_generation_timestamp = (known after apply)
        next_signing_key_length       = (known after apply)
        signing_attributes_origin     = (known after apply)
        status                        = (known after apply)
        tokens                        = (known after apply)
    }
}

Affected Resource(s) and/or Data Source(s)

Resource aws_sesv2_email_identity in provider hashicorp/aws (version 5.15.0)

Potential Terraform Configuration

No response

References

No response

Would you like to implement a fix?

None

@danhlee329 danhlee329 added the enhancement Requests to existing resources that expand the functionality or scope. label Sep 6, 2023
@github-actions
Copy link

github-actions bot commented Sep 6, 2023

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please see our prioritization guide for information on how we prioritize.
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@github-actions github-actions bot added the service/sesv2 Issues and PRs that pertain to the sesv2 service. label Sep 6, 2023
@terraform-aws-provider terraform-aws-provider bot added the needs-triage Waiting for first response or review from a maintainer. label Sep 6, 2023
@danhlee329
Copy link
Author

This is better suited as a security vulnerability, I've sent an email to security@hashicorp.com per https://github.com/hashicorp/terraform-provider-aws/security/policy referencing this issue.

@jar-b jar-b removed the needs-triage Waiting for first response or review from a maintainer. label Sep 15, 2023
@danhlee329
Copy link
Author

Thanks for the PR, I'll close the issue after testing out changes via the latest release with the adjustment.

@danhlee329
Copy link
Author

Was able to pull Provider version 5.18.1 and confirming that the value is now shown as (sensitive value), closing issue, thank you!

@github-actions
Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 27, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement Requests to existing resources that expand the functionality or scope. service/sesv2 Issues and PRs that pertain to the sesv2 service.
Projects
None yet
Development

No branches or pull requests

2 participants