Skip to content

fix(ses): incorrect DKIM records for EmailIdentity#21318

Merged
mergify[bot] merged 2 commits intoaws:mainfrom
jogold:ses-dkim-cname
Aug 5, 2022
Merged

fix(ses): incorrect DKIM records for EmailIdentity#21318
mergify[bot] merged 2 commits intoaws:mainfrom
jogold:ses-dkim-cname

Conversation

@jogold
Copy link
Copy Markdown
Contributor

@jogold jogold commented Jul 25, 2022

Because route53.determineFullyQualifiedDomainName() doesn't correctly
handles tokens we get the zone name twice here.

Another way to solve this would be to fix
determineFullyQualifiedDomainName(). There is already a discussion
there #20435 for the hosted zone name
part, not the record name.

Closes #21306


All Submissions:

Adding new Unconventional Dependencies:

  • This PR adds new unconventional dependencies following the process described here

New Features

  • Have you added the new feature to an integration test?
    • Did you use yarn integ to deploy the infrastructure and generate the snapshot (i.e. yarn integ without --dry-run)?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

Because `route53.determineFullyQualifiedDomainName()` doesn't correctly
handles tokens we get the zone name twice here.

Another way to solve this would be to fix
`determineFullyQualifiedDomainName()`. There is already a discussion
there aws#20435 for the hosted zone name
part, not the record name.

Closes aws#21306
@gitpod-io
Copy link
Copy Markdown

gitpod-io bot commented Jul 25, 2022

@aws-cdk-automation aws-cdk-automation requested a review from a team July 25, 2022 15:24
@github-actions github-actions bot added bug This issue is a bug. p2 labels Jul 25, 2022
@jogold
Copy link
Copy Markdown
Contributor Author

jogold commented Jul 25, 2022

@corymhall FYI

Do you think it is better to solve this in route53?

See #20435 (comment)

@TheRealAmazonKendra
Copy link
Copy Markdown
Contributor

I think that we should fix this in route53 instead of here, since that's the actual source of this bug. I closed the other PR because I didn't think the approach was right but I want to keep the conversation going in the issue of what the right path forward really is.

@corymhall
Copy link
Copy Markdown
Contributor

Do you think it is better to solve this in route53?

I commented on the issue. I agree with @TheRealAmazonKendra, we should address this in route53.

@TheRealAmazonKendra
Copy link
Copy Markdown
Contributor

I'm going to go ahead and close this since we won't be moving forward with this particular approach.

@jogold
Copy link
Copy Markdown
Contributor Author

jogold commented Aug 4, 2022

@TheRealAmazonKendra if this is fixed under a feature flag in route53 how can it be fixed for everyone in ses?

@corymhall
Copy link
Copy Markdown
Contributor

That's a good point...I guess we need this PR as well, otherwise it will remain broken for anyone that doesn't opt-in to the feature flag.

@corymhall corymhall reopened this Aug 4, 2022
@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Aug 4, 2022

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

@TheRealAmazonKendra
Copy link
Copy Markdown
Contributor

@Mergifyio update

@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Aug 5, 2022

update

☑️ Nothing to do

Details
  • -closed [:pushpin: update requirement]
  • #commits-behind>0 [:pushpin: update requirement]

@aws-cdk-automation
Copy link
Copy Markdown
Collaborator

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
  • Commit ID: 34471d8
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Aug 5, 2022

Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork).

@TheRealAmazonKendra
Copy link
Copy Markdown
Contributor

@Mergifyio update

@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Aug 5, 2022

update

☑️ Nothing to do

Details
  • -closed [:pushpin: update requirement]
  • #commits-behind>0 [:pushpin: update requirement]

@TheRealAmazonKendra
Copy link
Copy Markdown
Contributor

@Mergifyio requeue

@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented Aug 5, 2022

requeue

✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically

@mergify mergify bot merged commit 54bad4c into aws:main Aug 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug This issue is a bug. p2

Projects

None yet

Development

Successfully merging this pull request may close these issues.

aws-ses: DKIM records are created with incorrect name from EmailIdentity

4 participants