2 Answers
- Newest
- Most votes
- Most comments
2
As a best practice, we recommend you deploy your image builder and fleet instances in private subnets. This means each fleet instance will access the internet via a corresponding NAT gateway. Each NAT gateway has an elastic IP address that doesn't change.
AppStream 2.0 is non-persistent. After the session is ended, the underlying instance is terminated. I don't recommend editing network interfaces, as that is not a scalable solution.
answered 2 years ago
1
can you see the nic in ec2 network interfaces page, if so it's worth reserving an elastic ip and trying to bind it outside of appStream if the image builder natively doesn't support static IP
answered 2 years ago
Relevant content
- asked 6 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
In this case I needed a quick way to have a static IP on my Image Builder, so the accepted answer worked. But I agree, your answer is the "best practice"