Refer to the exhibit.
An administrator configured a FortiGate device to connect to the AWS API to retrieve resource values from the AWS console to create dynamic objects for the FortiGate policies. The administrator is unable to retrieve AWS dynamic objects on FortiGate.
Which two reasons can explain why? (Choose two.)
Invalid Credentials:
The debug output shows an 'AuthFailure' error, indicating that AWS was not able to validate the provided access credentials. This usually points to incorrect or invalid AWS access or secret keys configured in the AWS Lab SDN connector (Option C).
Clock Skew:
Another common reason for authentication failures in AWS API calls is a clock skew between the FortiGate device and AWS. AWS requires that the system time of the client making the API call is synchronized with its own time, within a small margin. If there is a significant time difference, AWS will reject the credentials (Option B).
Other Options Analysis:
Option A is incorrect because the AWS API supports XML version 1.0.
Option D is incorrect as the error message does not indicate an issue with connecting on port 401.
Option E is incorrect because the error is related to authentication, not the absence of instances.
AWS API Authentication: AWS API Security
FortiGate AWS Integration Guide: FortiGate AWS Integration
Timothy
2 months agoMelodie
2 months agoAlise
2 months agoWeldon
2 months agoLezlie
2 months agoWeldon
2 months agoKanisha
3 months agoAnissa
2 months agoBuddy
2 months agoShannan
2 months agoSabina
2 months agoWilletta
2 months agoJoanna
2 months agoSherell
3 months agoMarkus
3 months agoEmilio
3 months agoVeronika
3 months agoLuis
3 months agoTashia
3 months agoLatricia
3 months agoPercy
3 months agoSharmaine
3 months agoJovita
3 months agoKenny
3 months agoFlo
3 months ago