Skip to content
This repository has been archived by the owner on Mar 21, 2022. It is now read-only.

Setup ACM. #3

Merged
merged 1 commit into from
Feb 11, 2018
Merged

Setup ACM. #3

merged 1 commit into from
Feb 11, 2018

Conversation

mazgi
Copy link
Owner

@mazgi mazgi commented Feb 11, 2018

fixes #2

@mazgi mazgi self-assigned this Feb 11, 2018
@mazgi mazgi merged commit a6f23f1 into master Feb 11, 2018
@mazgi mazgi deleted the setup-acm branch February 11, 2018 18:56
@mazgi
Copy link
Owner Author

mazgi commented Feb 11, 2018

see: hashicorp/terraform-provider-aws#2813

It was a problem when use SAN.

$ bin/terraform apply
aws_acm_certificate.sakemeshi-love: Refreshing state... (ID: arn:aws:acm:us-east-1:413505172286:cert...e/cc470fc8-a011-4f6c-b9a3-47eecb55d0df)
aws_cloudfront_origin_access_identity.sakemeshi-love-website-prod-origin_access_identity: Refreshing state... (ID: E3OXK8V70FD009)
aws_s3_bucket.sakemeshi-love-website-prod-s3: Refreshing state... (ID: sakemeshi-love-website-prod-s3)
aws_route53_zone.sakemeshi-love: Refreshing state... (ID: Z1JQE9O62ELH0F)
aws_iam_user.sakemeshi-love-website-prod-writer: Refreshing state... (ID: sakemeshi-love-website-prod-writer)
aws_route53_record.certificate-validation-sakemeshi-love: Refreshing state... (ID: Z1JQE9O62ELH0F__cb26a628cb419467524e6361f5360a23.sakemeshi.love._CNAME)
aws_cloudfront_distribution.sakemeshi-love-website-prod-distribution: Refreshing state... (ID: E144P48JQ6OQV1)
aws_route53_record.sakemeshi-love: Refreshing state... (ID: Z1JQE9O62ELH0F_sakemeshi.love_A)

An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  + aws_acm_certificate_validation.sakemeshi-love
      id:                                 <computed>
      certificate_arn:                    "arn:aws:acm:us-east-1:413505172286:certificate/cc470fc8-a011-4f6c-b9a3-47eecb55d0df"
      validation_record_fqdns.#:          "1"
      validation_record_fqdns.3517848190: "_cb26a628cb419467524e6361f5360a23.sakemeshi.love"


Plan: 1 to add, 0 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

aws_acm_certificate_validation.sakemeshi-love: Creating...
  certificate_arn:                    "" => "arn:aws:acm:us-east-1:413505172286:certificate/cc470fc8-a011-4f6c-b9a3-47eecb55d0df"
  validation_record_fqdns.#:          "" => "1"
  validation_record_fqdns.3517848190: "" => "_cb26a628cb419467524e6361f5360a23.sakemeshi.love"

Error: Error applying plan:

1 error(s) occurred:

* aws_acm_certificate_validation.sakemeshi-love: 1 error(s) occurred:

* aws_acm_certificate_validation.sakemeshi-love: Certificate needs [_cb26a628cb419467524e6361f5360a23.sakemeshi.love _cb26a628cb419467524e6361f5360a23.sakemeshi.love] to be set but only [_cb26a628cb419467524e6361f5360a23.sakemeshi.love] was passed to validation_record_fqdns

Terraform does not automatically rollback in the face of errors.
Instead, your Terraform state file has been partially updated with
any resources that successfully completed. Please address the error
above and apply again to incrementally change your infrastructure.

@mazgi
Copy link
Owner Author

mazgi commented Feb 11, 2018

The aws_acm_certificate_validation require 2 FQDNs but it got one FQDN, because R53 recordscertificate-validation-sakemeshi-love and certificate-validation-_-sakemeshi-love are return same value.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Enable HTTPS with ACM
1 participant