-
Notifications
You must be signed in to change notification settings - Fork 4k
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
fix(certificatemanager): Route53 endpoint cannot be set and does not work for aws-cn #6480
Conversation
Title does not follow the guidelines of Conventional Commits. Please adjust title before merge. |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Hey @shivlaks Any update? |
taking a look! |
...ws-cdk/aws-certificatemanager/lambda-packages/dns_validated_certificate_handler/lib/index.js
Show resolved
Hide resolved
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
@@ -80,7 +80,7 @@ let report = function(event, context, responseStatus, physicalResourceId, respon | |||
const requestCertificate = async function(requestId, domainName, subjectAlternativeNames, hostedZoneId, region) { | |||
const crypto = require('crypto'); | |||
const acm = new aws.ACM({ region }); | |||
const route53 = new aws.Route53(); | |||
const route53 = region.startsWith("cn-") ? new aws.Route53({endpoint: "https://route53.amazonaws.com.cn"}) : new aws.Route53(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- what're the exact region(s)? is there a good reason for going with
startsWith
? (i.e. would all future CN regions map to the same endpoint? if not, we should be specific here) - how has this been tested? - I don't see Route53 as a supported service in the region table.
- can you share any resources used in determining this endpoint?
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
getting closer - can you clarify why the ecs-patterns
integ test expectations needed to change?
...ges/@aws-cdk/aws-ecs-patterns/test/fargate/integ.load-balanced-fargate-service.expected.json
Show resolved
Hide resolved
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
To fix #6431
We have also considered hardcode endpoint for China regions, but which may have change after Route53 officially launched in China.
Now to make this work for internal accounts(as for which Route53 in China are available), we provide a word around for users to provide endpoint from app stack.
After Route53 officially launched in China and it will also provide a decent endpoint as other regions, customers need not provide any endpoint for the parameter, just use it as for other regions.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license