Skip to content
This repository has been archived by the owner on Jul 19, 2019. It is now read-only.

ELBs Should Work Whether or Not ACM Is Available #13

Open
ferricoxide opened this issue Dec 26, 2018 · 0 comments
Open

ELBs Should Work Whether or Not ACM Is Available #13

ferricoxide opened this issue Dec 26, 2018 · 0 comments
Labels
bug Something isn't working

Comments

@ferricoxide
Copy link
Member

ferricoxide commented Dec 26, 2018

Problem Description:

Amazon Certificate Manager (ACM) is not available for use in all regions/partitions. In these regions/partitions, it will be necessary to use Identity and Access Management (IAM) to host SSL certificates used for ELB-based SSL-termination. To maximize portability, ELB templates should allow use of either ACM- or IAM-hosted SSL certificates.

Expected Behavior:

ELBs support SSL-termination whether ACM is available for use in a given region/partition.

Actual Behavior:

ELBs do not currently support SSL-termination when ACM is unavailable for use in a given region/partition.

Affected Components

The following templates need remediation:

  • make_jira-dc_ELBv1-pub.tmplt.json
  • make_jira-dc_ELBv2-pub.tmplt.json
  • make_jira-dc_parent-EFS-ELBv1.tmplt.json
  • make_jira-dc_parent-EFS-ELBv2-autoscale.tmplt.json
  • make_jira-dc_parent-EFS-ELBv2-instance.tmplt.json

Fix recommendation:

Add a Condition{} and Parameters{} components and associated logic within the Resources{} sections to support selection of ACM- or IAM-hosted SSL certificates when launching an ELB template.

@ferricoxide ferricoxide added the bug Something isn't working label Dec 26, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant