I'm using a VPC with public/private subnets and a NAT instance created by the VPC setup wizard. I'd like to make a few tweaks to the NAT instances via OpsWorks (mostly logging and changes to iptables rules), but when I created a custom layer and attempted to add the existing NAT instance to it, it wasn't on the list of available instances. Is what I'm trying to do even possible? If not, what is the best way to manage a NAT instance inside OpsWorks?
How to add a NAT instance that was created by the VPC setup wizard to an OpsWorks layer
amazon ec2amazon-vpcopsworks
Related Topic
- Linux – How to SSH to ec2 instance in VPC private subnet via NAT server
- Nat – Amazon EC2 VPC: NAT instance download speed performance drop
- Nat – No internet access to EC2 instance in VPC
- Iptables – Instance in private subnet can connect internet but can’t ping/traceroute
- AWS RDS Private Subnet – Does RDS in Private Subnet Need a NAT Instance/Gateway?
Best Answer
When adding an instance to a layer in OpsWork, the Existing tab will show existing instances that are already defined in another layer in your stack. This might be useful if you had a web server layer and an app server layer and wanted the same EC2 instance to act as both the web server and the app server. The Existing tab will not show any EC2 instances that were created outside of OpsWorks or in another Stack.
Here is what we did to set up NAT instances using OpsWorks.