Hello lostboy10,
I found this solution. Can you tell us if it helps, please?
To change the instance type of your FortiGate-VM on AWS, especially when dealing with multiple ENIs (Elastic Network Interfaces), there are a few considerations to keep in mind:
Instance Type Compatibility
-
ENI Support: Ensure that the new instance type supports the number of ENIs you require. The r7i.large instance type should support multiple ENIs, but you should verify this against AWS documentation or the instance type specifications.
-
vCPU and Memory: Since you have reduced your license to 2 vCPUs, ensure that the new instance type matches this requirement. The r7i.large instance type typically comes with 2 vCPUs, which should align with your license.
-
FortiGate VM Compatibility: Check the FortiGate-VM compatibility with the chosen instance type. While FortiGate-VMs are generally flexible, it's always good to confirm that the instance type is supported for your specific FortiGate-VM version.
Steps to Change Instance Type
-
Power Off the Instance: As per the technical tip, power off the FortiGate instance from the AWS console and wait for the VM status to change to 'Stopped'.
-
Change Instance Type:
- Navigate to the AWS console.
- From the Action Menu, select Instance settings and then Change instance type.
- Select the desired new size for the VM (e.g.,
r7i.large) and apply the changes.
-
Start the Instance: Once the instance type is changed, start the VM instance and ensure it's up and running.
-
License Check: After changing the instance type, verify that the FortiGate VM license is still valid and functioning correctly. You may need to upload a new license file if there are any issues.
Additional Resources
- AWS Instance Type Documentation: For detailed specifications on ENI support and other features, refer to the AWS EC2 Instance Types documentation.
- FortiGate-VM AWS Datasheet: Review the FortiGate-VM AWS Datasheet for compatibility and performance details.
Final Considerations
- Network Configuration: Ensure that your network configuration, including security groups and routing, remains intact after the instance type change.
- Testing: After making the change, conduct thorough testing to ensure that all functionalities are working as expected.
If you have any specific concerns about compatibility or performance, consulting with Fortinet support or AWS support can provide additional assurance.