I have 1 AWS - EC2 instance (windows server 2008 r2) running - I configured the security group to my IP address - I downloaded the RDP for it, and was able to logged in successfully,and now I want to give my friend's computer an access to the EC2 instance I have.
how do you I add another ip address on an EC2 instance so that my team can access the same windows server on AWS?
we want to use the server as a development environment. please advice.
thanks in advance.
Related
I have created a centos7 in my windows machine using oracle virtual box.
I also created and redhat instance in amazon aws.
Now I want to connect from aws ec2 instance to my centos7 instance which is in my windows laptop using SSH.
I have enabled the PasswordAuthentication to Yes in /etc/ssh/sshd_config file in both the machines/instances.
Now in aws ec2 instance I'm trying with below command and it is not showing anything.
ssh user1#122.175.101.188
Please guide me? Am I missed something here?
Make sure that both instances are connected to the internet and have a valid IP address assigned to them.
SSH service is running on your CentOS 7 instance by running the command sudo systemctl status sshd.
,ifconfig on your CentOS 7 instance and looking for the IP address assigned to the network interface you are using.
In your AWS EC2 instance, open a terminal and run the command ssh user1#. Replace with the actual IP address of your CentOS 7 instance.
If this is your first time connecting to the CentOS 7 instance, you may be prompted to confirm the SSH host key fingerprint. Type "yes" to continue.
This typically requires that your local network is configured to allow incoming connections from the Internet, and that your Amazon EC2 instance has the necessary firewall rules and security groups configured to allow outbound connections to your local network. Additionally, you will need to configure any necessary port forwarding or NAT rules on your router or firewall to allow incoming connections to your VirtualBox instance.
When I try to connect to my EC2 instance using web browser (Mozilla Firefox) using the third option in the connect (EC2 Instance Connect (browser-based SSH connection) ), I get the following error in the new pop-up window:
There was a problem setting up the instance connection
Log in failed. If this instance has just started up, try again in a minute or two.
Some things to check:
Make sure the instance was launched from Amazon Linux 2 or Ubuntu 16.04 or later
Check that the instance is in a public subnet (defined as having a Route Table that points to an Internet Gateway)
Open the Security Group for SSH (port 22) either for the whole Internet (0.0.0.0/0) (which is a very poor choice for security) or from the IP address ranges for EC2 Instance Connect (See: AWS IP Address Ranges - AWS General Reference)
EC2 Instance Connect in your browser establishes a web connection to the AWS service. Then, the SSH connection is established from the AWS Service to the Amazon EC2 instance. This is why the security group needs to allow incoming connections from the IP address range associated with the EC2 Instance Connect Service (not your own IP address).
Alternative ways to connect are:
Run an SSH client on your computer, or
Use AWS Systems Manager Session Manager (which connects via an Agent running on the computer, so it's not 'real' SSH)
By following the link below, I have successfully setup Windows Server 2012 R2 as a Customer Gateway.
https://docs.aws.amazon.com/vpc/latest/adminguide/customer-gateway-windows-2012.html
I am able to ping the EC2 instance from my on-premises Windows Server. However, I want to do the vice-versa i.e., to ping the on-premises Windows Server IP from EC2 inside instance (RDP). May I know how to do this please?
I logged into EC2 instance through RDP. Pinged my on-premises Windows Server from there (192.168.X.X) but it returned 'Request timed out'.
Why do I need this?
I am doing all these because I want to migrate & replicate data automatically from my on-premises SQL Server to DB in Cloud. I decided to use AWS Database Migration Service (DMS). In order to set source endpoint (on-premises SQL Server), I need to let AWS communicate to my on-premises network through private IP. DMS should recognize 192.168.X.X\MSSQLServer.
Check outbound filters on your security group (but by default should allow everything).
Check your NACL to ensure it allows proper inbound/outbound traffic since it is stateless.
Check your Windows firewall in your Windows Server to ensure it will allow inbound ICMP.
I have set up an AWS EC2 server, and installed cassandra on it. I am successfully able to connect to cassandra and use it through my local machine using the public IP of my ec2 instance.
Now, I need to be connected to a VPN to continue with my work. But, after connecting to the VPN, I am not able to ssh into the ec2 server or access the installed cassandra.
My security group allows all traffic (IPv4 and IPv6).
I'm new to this, so any help would be appreciated. Thanks!
I installed jboss in my ec2 instance. My elastic ip address 52.16.53.218.
I deployed my retailproduct application. Server is started. Deployed successfully, but I can't access my application.
I tried below ways:
http://localhost:8080/retailcare
http://127.0.0.1:8080/retailcare
http://52.16.53.218:8080/retailcare
I can't access. Any help appreciated.
Accessing localhost stays totally within the Amazon EC2 instance, so it would not be impacted by Security Group.
If you are able to SSH/RDP to the actual server and accessing http://localhost:8080/retailcare does not work, then it is a problem with your application or JBoss configuration.