#9266 AWS: Create VPC peering connection between two VPCs / Testing Farm
Closed: Fixed 3 years ago by mvadkert. Opened 3 years ago by mvadkert.

Hi,

we need to connect our EKS cluster to EC2 instances, I need to connect two VPCs so they can reach each other:

vpc-0896aedab4753e76f (eks cluster)
vpc-a4f084cd (our EC2 instances)

Seems it can be done here:
https://us-east-2.console.aws.amazon.com/vpc/home?region=us-east-2#CreatePeeringConnection:

I am not able to do it myself, I get this error:

You are not authorized to perform this operation. Encoded authorization failure message: i1oD88iF5XzCB1pAIS_bA5ztjcllP0FLjUDyJnTvkVcfVH3Ylm0rON4zvUil4oLGd_HrAEI3vonGc1H2puS7RXbuYDV1EDXTe7Tfsc5aMiHq9vd81z6IxegJH2BGP49KscW9Q3HYaCdeN7JlgBGC2D8GQ6fLyKiOd5vnZRiZyTWFWoc1tt5AeJcDsoOtZOlRw_ckMYa3Pa08RP6iA_8gudUCM3_y6PSI1Q2Io3RX6APJI-JKysKv3tX6cseFULTTlRA7JN82OaySB_LPd0zQ-hSnH_X-oFwRhvKugCJZ3aPe8Ghi37fbkRFRrQVSuqRArtlBgWJYTqhriaLrRxwz946sWQoDJmSmyFM7ESt-UqbJI34JKVsujezLb06c7xhV9BwCRNaUahY3LJlwTW80px-NIPNvT0lsZyRZThvu7zIe-M0Z7j47inmwCI4m_ifCY0ArEHjrsqAU-9iW0UpL-zu3MdOnj7PDafH4_rBFlmswpsWbBwuphwO6u4a-4PtniiTjJQKgdOgmcYVVQex9WpbkV7i0iOWww1HD7Y3buX1BWecWUBhGartxTpiD3Rk4Euc3JCbzypRwZb50lH4RGZ7ci8KhXwQfmsoUOHLStq6Y8rS8W7usX_pIXuA

This is blocking feature to running functional tests for Fedora CI.


Metadata Update from @zlopez:
- Issue tagged with: aws

3 years ago

Metadata Update from @mohanboddu:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: medium-gain, medium-trouble, ops

3 years ago

I don't see vpc-0896aedab4753e76f... it's showing me only: vpc-0618f77c2f99c9956

Is the 0618 one right?

@kevin sorry the other vpc is in us-east-2, one is in us-east-1, the other one in us-east-2

@kevin, so to be precise

us-east-1: vpc-0896aedab4753e76f
us-east-2: vpc-a4f084cd

ok, done. Can you take a look and see if that looks right?

Thanks, looking but I am not seeing what I would like to see, will need to do more testing to see what is wrong ...

Shall we keep this open? Or have you reopen if there's further to do?

Let's close it for now, we workarounded the problem, so the severity is lower now. Thanks for helping!

Metadata Update from @mvadkert:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata
Boards 1
ops Status: Done