- Newest
- Most votes
- Most comments
Verify that the EC2 instance you are connected to has a public IP address (I assume it should have if you are RDPing into Windows), and that the security group associated with it has an outbound security rule allowing access to destination 0.0.0.0/0 over TCP ports 80 and 443.
I can't use RDP.** On this type of account,** I can't generate a key using "create key pair" (or import *.pem file from Windows) because an authorization error pops up "You are not authorized to perform this operation. User is not authorized to perform ec2:CreateKeyPair on resource".
I connect to my instance (Windows Server 2019) via "Connect using Fleet Manager"and User credentials - Username and password.
I have only "Web server security group" and I can't add another - "Failed to change security groups for network interface {{networkInterfaceId}}. You are not authorized to perform this operation."
I would look at where your EC2 is on your VPC.
If your EC2 is on a private subnet then make sure there is a route on your private subnet to a NAT Gateway. I assume you may not have a NAT gateway setup or routes for the NAT gateway.
If it’s on a public subnet ensure the EC2 has a public IP address.
You also will need an internet gateway attached to your VPC.
Also ensure any ACLs allow out and inbound traffic.
Relevant content
- asked 4 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago