sample-aws-pricing-calculator-mcp 1.2.0 → 1.2.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
|
@@ -5,7 +5,8 @@
|
|
|
5
5
|
"templateId": "networkAddressTranslationGateway",
|
|
6
6
|
"status": "verified",
|
|
7
7
|
"traps": [
|
|
8
|
-
"
|
|
8
|
+
"NAT Gateway has two mutually exclusive field sets, make sure to confirm with the user to either use 'Regional NAT Gateway' or 'NAT Gateway'. Regional (regionalNatGatewayCount, regionalNatGatewayAzCount, regionalNatGatewayDataProcessed) is the current UI default. Non-regional/legacy (numberOfGateways, dataProcessedPerNATGateway) also works. Using both will double-count costs.",
|
|
9
|
+
"All five fields are marked required by the manifest. When using one set, explicitly set the other set to \"0\" to avoid inflated defaults and linter refusals.",
|
|
9
10
|
"Manifest defaults are 5 gateways × 3 AZs — wildly over-sized for a 'hello world'. minimalConfig overrides to 1×1; agents reading manifest defaults directly will over-estimate ~5×."
|
|
10
11
|
],
|
|
11
12
|
"minimalConfig": {
|
|
@@ -16,6 +17,11 @@
|
|
|
16
17
|
"regionalNatGatewayDataProcessed": {
|
|
17
18
|
"value": "1",
|
|
18
19
|
"unit": "gb|month"
|
|
20
|
+
},
|
|
21
|
+
"numberOfGateways": "0",
|
|
22
|
+
"dataProcessedPerNATGateway": {
|
|
23
|
+
"value": "0",
|
|
24
|
+
"unit": "gb|month"
|
|
19
25
|
}
|
|
20
26
|
},
|
|
21
27
|
"lastVerifiedAt": "2026-05-29",
|