1 réponse
- Le plus récent
- Le plus de votes
- La plupart des commentaires
0
The error usually appears if you have no available elastic IPs in the region. Please take a look at your available elastic IPs by following steps here Describe your Elastic IP addresses. If there is no elastic IP, make sure to allocate one. Once you have at least one available elastic IP, try it again.
répondu il y a un an
Contenus pertinents
- demandé il y a un an
- demandé il y a un an
- Réponse acceptéedemandé il y a un an
- demandé il y a 14 jours
- AWS OFFICIELA mis à jour il y a 2 ans
- AWS OFFICIELA mis à jour il y a 5 ans
The answer ended up being that the page never updated. For some reason, I decided to navigate out of the create page and go back in to create the server again and that worked.
So clicking (create server -> clicking create VPC (which opens a new tab) -> clicking the refresh button next to create VPC) creates a weird issue where the subnets can't be specified. Not sure why.
I have the same issue here. Trying to set up a SFTP server using Transfer Family but when I select VPC hosted I get an Information message "No Address Allocation ID's are currently available". I have 2 elastic IP's in the region as well. Any ideas?