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

Can Terraform AWS ELB provider support configuring the SSL Cipher Suite? #3176

Closed
ketzacoatl opened this issue Sep 6, 2015 · 7 comments
Closed

Comments

@ketzacoatl
Copy link
Contributor

I am not sure AWS provides API endpoints or attributes for this (I spent some time looking through their docs to confirm), but I also see no mention of the cipher suite in the Terraform codebase.

I am assuming this is not possible, but I would like to be sure: Is it possible for the ELB provider to support configuring the SSL Cipher Suite used by an ELB?

@gtmtech
Copy link

gtmtech commented Mar 2, 2016

+1 - definitely needed, and definitely a terraform omission.

Especially because the default ELB ciphersuite is no longer recommended to be used, and so if you want to run a compliant/secure ELB, you should be doing a custom one anyway.

Sadly this is something that terraform lacks, but cloudformation has

Do you know if anyone is scheduled to look at this @catsby ?

@anthonycorletti
Copy link

👍

@catsby
Copy link
Contributor

catsby commented Mar 9, 2016

Hey @gtmtech – no, can't say anyone is looking into this. I'm not sure how it's done, is this done through Load Balancer Policy types?

I don't believe I'll be getting to this soon, but would love to hear more on how it's done via the API

@catsby catsby added the waiting-response An issue/pull request is waiting for a response from the community label Mar 9, 2016
@catsby
Copy link
Contributor

catsby commented Mar 23, 2016

Looks like this is implemented in #5637! We'll review and get that in if possible.
Thanks!

@stack72
Copy link
Contributor

stack72 commented Aug 11, 2016

Closed via the rebased PR in #8084

@catsby catsby closed this as completed Nov 3, 2016
@cappellem
Copy link

+1 :)

@ghost
Copy link

ghost commented Apr 14, 2020

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.

@ghost ghost locked and limited conversation to collaborators Apr 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

7 participants