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

NAT cost optimization #2

Open
arno49 opened this issue Feb 14, 2019 · 3 comments
Open

NAT cost optimization #2

arno49 opened this issue Feb 14, 2019 · 3 comments
Assignees

Comments

@arno49
Copy link
Member

arno49 commented Feb 14, 2019

I'd like to have opportunity to reduce core costs with replacing NAT gateway service with ec2 instance (shape should be chosen from variables, default t3.nano).

@arman-personal
Copy link
Contributor

Hi all! I've created PR for this issue, plz review it.
I'm new to Terraform and IaC AWS and don't expect to solve this issue from the first time

ToROxI pushed a commit that referenced this issue Feb 28, 2019
ToROxI added a commit that referenced this issue Feb 28, 2019
* Issue "NAT cost optimization #2" (#3)

some improvements:
* add ability to disable NAT
* restore ability to setup only one NAT in case if it ec2-based
* add auto-detecting latest Amazon NAT AMI
* add test example
* remove redundant parameters
* Update README.md
@ToROxI ToROxI assigned ToROxI and arman-personal and unassigned ToROxI Feb 28, 2019
@arno49 arno49 closed this as completed Feb 28, 2019
@arno49 arno49 reopened this Apr 22, 2019
@arno49
Copy link
Member Author

arno49 commented Apr 22, 2019

Not works, as expected.

@javid87
Copy link

javid87 commented Apr 29, 2019

please recheck. connection problem solved.
Now we can connect to Nat instance with key. added new line for internet connection "source_dest_check = false ". tested on own AWS cloud platform all work fine

https://github.com/javid87/ld_tf_projects.git

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

No branches or pull requests

4 participants