Open
Description
Checkboxes for prior research
- I've gone through Developer Guide and API referenceI've checked AWS Forums and StackOverflow.I've searched for previous similar issues and didn't find any solution.
Describe the bug
The NetworkInterfaceType enum includes "natGateway"
when the actual value is "nat_gateway"
:
- NetworkInterfaceType enum in aws-sdk-js-v3 includes
"natGateway"
. - Amazon's API reference for NetworkInterface's
interfaceType
property specifies"nat_gateway"
.
The NetworkInterfaceType enum should include "nat_gateway"
instead of "natGateway"
.
Regression Issue
- Select this option if this issue appears to be a regression.
SDK version number
Which JavaScript Runtime is this issue in?
Node.js
Details of the browser/Node.js/ReactNative version
N/A
Reproduction Steps
See above.
Observed Behavior
See above.
Expected Behavior
See above.
Possible Solution
Change the enum.
Additional Information/Context
This bug is present in the JavaScript AWS SDK v2, and possibly others: aws/aws-sdk-js#4702
Metadata
Metadata
Assignees
Labels
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
"natGateway"
instead of"nat_gateway"
aws/aws-sdk-js#4702zshzbh commentedon May 20, 2025
@markandrus
Thanks for the feedback!
In the repo , it is
natGateway: "natGateway",
;In internal codebase it is also
<enumValue value="natGateway"/>
,;On doc it is
nat_gateway
Let me check with the service team to see what should be the correct value.
Meanwhile, did you put
natGateway
and it is not working? Isnat_gateway
working on your end?Thanks!
Maggie
markandrus commentedon May 30, 2025
Hi @zshzbh 👋 thanks for taking a look!
Yes, when we get API results back, the value we see is
"nat_gateway"
. That's the value we need to match on, not"natGateway"
. So the SDK's enum definition appears incorrect (and I guess this may affect other languages' SDKs, too; I already saw it affects the previous JavaScript SDK).Thanks!
Mark
zshzbh commentedon Jun 27, 2025
Hey @markandrus ,
Thanks for the followup, in the repo , it is natGateway: "natGateway", and that value comes from service team. The change in service model will fix this issue. The service team is actively working on that.
Please keep an eye on the release note for the fix. Thanks! : )