- 新しい順
- 投票が多い順
- コメントが多い順
I don't know if this is possible, but what about making the subnet you use a private subnet and registering the NAT gateway in the route table?
In doing so, the public IP address may become the fixed IP address of the NAT gateway.
When an AWS MediaConnect Flow is created a new Public IP address is created. When that flow is deleted, that address is removed. If you are using VPC connections to/from a MediaConnect Flow, when a new flow is created you will need to reattach to the existing VPC subnet. The Public to Private connection through the VPC could be then be used to translate a Public IP to the new MediaConnect input or output.
Can you please share any relevant doc/AWS article for this. It would be helpful.
Will Elastic IP be needed here ? or this can be done without it has well ?
My IP will be whitelisted at Vendor's Server
関連するコンテンツ
- 質問済み 4ヶ月前
- AWS公式更新しました 1年前
- AWS公式更新しました 2年前
Can you please share the relevant doc or any link,on how we can do this.
But by doing this,if I create another Mediaconnect I would need one more Elastic IP which will talk to internet ?