- 新しい順
- 投票が多い順
- コメントが多い順
Greetings NobodySpecial
I have seen this post and query, I am from AWS Support.
Firstly I would like to confirm that you are not crazy!
The Elastic Beanstalk Team identified an issue where the AssociatePublicIpAddress value was not being resolved properly in some situations. This resulted in the AssociatePublicIpAddress being set to false as you identified.
There has since been a fix released that resolved this behavior. You should not experience this issue any more.
Please test the behavior on your end again.
*Should the issue not be resolved on your end I would recommend creating a case with AWS Support as there may be other issues you are experiencing.
To troubleshoot this issue, you can check the VPC configuration for your new project and compare it with the VPC configuration for your other projects. Specifically, you should check the subnet settings to ensure that they are properly configured to assign public IP addresses to all instances launched in the subnet. You could try creating a new sample project using the Elastic Beanstalk console instead of the CLI tool to see if you have the same issue.
関連するコンテンツ
- AWS公式更新しました 1年前
- AWS公式更新しました 7ヶ月前
Thanks for reporting back!
Still having an issue here. If you go through the "Create environment" on the AWS site and select "network" for the load balancer type, it wont let you get past that screen. Shows an error at the bottom that says "Cannot read properties of undefined (reading 'DefaultValue')". If you change it to "application" then it lets you proceed.
Going to try this via CLI now and will report back.