-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
EC2 CustomerGateway Bug #855
Comments
Hello @stack72, I'll reach out to the service team and let them know. Thank you for reaching out to us with this find. |
Thanks for contacting us @stack72 We've forward this information on to the EC2 service team. In addition the console website has a "Feedback" button in the bottom left hand corner of the page. Submitting your feedback here will send your feedback to the EC2 and console teams. Since this issue seems to be a limitation of the console website and not the SDK I'm going to go ahead and close this issue. |
So is his something will be acted on, something I need to raise elsewhere or just ignore? This feels a pretty serious bug as infrastructure can be easily modified without any intention to. Closing it without any idea of what happens next seems to be an odd choice |
Hello @stack72, sorry for the delayed response and thank you for being patient. It looks like the service team had just gotten back to us. According to them, the docs states:
Further, the console uses some validation of input to guide customers in choosing correct values. Lastly, the service team states that this the behavior is safe to use and is idempotent. If you have any additional questions @stack72, please let us know! |
When i have an existing EC2 Customer Gateway as follows:
The AWS Console doesn't let me create another with the same parameters:
But the SDK does allow me to do this:
As you can see, the CustomerGatewayID is the same as the one already in the screenshot above
Paul
The text was updated successfully, but these errors were encountered: