Skip to main content
_imagir0_
Explorer II
September 27, 2024
Question

FMG 7.2.7 - AWS External Connector SDN Dynamic Address Object Import Bug

  • September 27, 2024
  • 1 reply
  • 1412 views

Hello,

 

I've deployed FMG 7.2.7  (evaluation) in AWS (BYOL) and configured AWS SDN connector using IAM roles.

 

I've tried to create a dynamic firewall object. Step 1 - enter a name, Step 2 - Filter - click on + , type SecurityGroudIP and then I click on a sg group and Apply. Filter is not applied!

 

I've tried with both Edge and Mozilla. Anyone having the same issue? 

 

FortiManager #aws

 

1 reply

sahmed_FTNT
Staff & Editor
Staff & Editor
September 29, 2024

Hello, you can run debugs using the below link  to collect more details:

 

https://community.fortinet.com/t5/FortiGate/Troubleshooting-Tip-AWS-SDN-connector-is-failing-to-update/ta-p/331503

 

_imagir0_
_imagir0_Author
Explorer II
September 30, 2024

Hello,

 

Thanks for your reply.   AWS connector works well, and it gets populated. The issue is with the GUI which is not selecting objects from the pop up window. 

diag debug application awsd -1  fortimanager-poc # diag debug application awsd -1 command parse error before 'awsd'

this command doesn't work on FMG 7.2.7, so I've used this guide  AWS and Azure Fabric connector issue - Fortinet Community 

 

: "Fabric Connectors: Amazon Web Services", "percent": 90, "vdom": null}, { "detail": "2024-09-30 05:25:49:Import objects from Amazon Web Services successful", "name": "Fabric Connectors: Amazon Web Services", "percent": 100, "vdom": null}], "state": 4, "err": 0, "percent": 100, "name": "Fabric Connectors: Amazon Web Services", "vdom": "", "ip": "", "oid": 0, "detail": "Import objects from Amazon Web Services successful", "start_tm": 1727673946, "end_tm": 1727673949}], "status": { "code": 0, "message": "OK"}, "url": "\/task\/task\/105\/line"}]}2024-09-30 05:25:50 2024-09-30 05:27:09 FSSO(null:null) => refresh interval:18000, current session number:0

 

 

_imagir0_
_imagir0_Author
Explorer II
October 8, 2024

I heard that this is related to a FMG known bug.

Is there anyone here who can check Fortimanger bug id 1073455? Is there any ETA?

 

Thanks!