In case somebody else ran into this issue, I was able to resolve the issue by loading the Licensing API key from the support portal into my AWS firewall then fetch the license using the auth-code:
request license api-key set key YOUR_LICENSING_API_KEY request license fetch auth-code YOUR_CAPACITY_LICENSE_AUTH_CODE
NOTE: The licensing API key can be found under Assets > Licensing API in the support portal
After the second command, you will be disconnected from VM. Upon reconnection you should see that you are licensed. Loading the Licensing API key may or may not be necessary, but the firewall should of course have internet access (incluing DNS) from it's MGT interface.