By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

Private instance is not connecting via bastion instance after adding into target group

0

Hi Team,

I have created two instances, one private and one public. They are actually working with proper VPC configuration.

Once i started to host my-app from a private instance via an application load balancer, So I added a private instance to the target group, and then when I connect a private instance via bastion, it's not connecting.

  • Lawrence Aiello
    a year ago

    Can you add more detail? What is the error message?

Topics
Networking & Content DeliveryCompute
Tags
Amazon VPCAmazon EC2Application Load Balancer
Language
English
Ravoi
asked a year ago203 views
1 Answer
0

Hi - I would start by checking basic security groups etc. from bastion to private instance and I believe they are in same VPC. Also ensure correct keys are used. You can also share the error message you are getting to see more.

profile pictureAWS
EXPERT
AWS-User-Nitin
answered a year ago
  • Ravoi
    a year ago

    Hi Nitin - --> The security group is properly configured and also ssh port enabled -->The VPC remains same for both instance in same region -->SSH key is correct -->How do I get error message ? and I just getting time-out issue

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content