Support IPv6 in beanstalk - NAT gateway avoidance
<!--- Please keep this note for the community ---> ### Community Note * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request. * Please do not leave "+1" or "me too" comments. They generate extra noise for issue followers and do not help prioritize the request. <!--- Thank you for keeping this note for the community ---> **Tell us about your request** What do you want us to build? EBS should support to build an EC2 instance (for app) even if this instance only has an IPv6 stack. **Is this request specific to an Elastic Beanstalk [platform](https://docs.aws.amazon.com/elasticbeanstalk/latest/platforms/platforms-supported.html)?** If so, which one(s)? It al least affects nodejs12.x on ALBv2. I suspect broader scope. **Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?** What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem. For now, EC2 instances created by EBS have IP addresses depending on the VPC they run in. If the VPC they run in issues both IPv4/IPv6 addresses, they will have both. If the VPC only supports IPv6, so will the EC2 instances created. A common patt
Posted by Ottunger on Nov 11, 2021, 10:26 AM
Tags
Related issues
- I hate that this whole cluster of beliefs exists, but software on my own computer enforcing what I can and can't do for ideological reaso...
- As I replied in another comment[1], it's their software, their choice.
- [Feature] Support external model integration via personal API keys and local LLMs (BYOK)
- > So when head of companies don’t care about quality, they’ll push hard no matter what to have speed.
- Feature request: support multiple named accounts per app/connector
- Support standalone Windows installer (`codex-setup.exe`)
Raise real-world problems, find people facing the same issue, and discuss solutions.3,000 issues0 comments
support (SaaS)
I hate that this whole cluster of beliefs exists, but software on my own computer enforcing what I can and can't do for ideological reaso...
NewAs I replied in another comment[1], it's their software, their choice.
[Feature] Support external model integration via personal API keys and local LLMs (BYOK)
> So when head of companies don’t care about quality, they’ll push hard no matter what to have speed.
Feature request: support multiple named accounts per app/connector
Support standalone Windows installer (`codex-setup.exe`)
[feature]: Move OIDC back to self-hosted OSS(Plane Free)
I was running about 1000 machines on VMware in my previous career.
Support IPv6 in beanstalk - NAT gateway avoidance
<!--- Please keep this note for the community ---> ### Community Note * Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request. * Please do not leave "+1" or "me too" comments. They generate extra noise for issue followers and do not help prioritize the request. <!--- Thank you for keeping this note for the community ---> **Tell us about your request** What do you want us to build? EBS should support to build an EC2 instance (for app) even if this instance only has an IPv6 stack. **Is this request specific to an Elastic Beanstalk [platform](https://docs.aws.amazon.com/elasticbeanstalk/latest/platforms/platforms-supported.html)?** If so, which one(s)? It al least affects nodejs12.x on ALBv2. I suspect broader scope. **Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?** What outcome are you trying to achieve, ultimately, and why is it hard/impossible to do right now? What is the impact of not having this problem solved? The more details you can provide, the better we'll be able to understand and solve the problem. For now, EC2 instances created by EBS have IP addresses depending on the VPC they run in. If the VPC they run in issues both IPv4/IPv6 addresses, they will have both. If the VPC only supports IPv6, so will the EC2 instances created. A common patt
Comments (0)
No comments yet. Start the discussion.