assign ec2 instance a public ip

• Awards Season
• Big Stories
• Pop Culture
• Video Games
• Celebrities

The Benefits of Tracking an IP Address Location

In today’s digital age, tracking an IP address location has become an important tool for businesses and individuals alike. An IP address is a unique numerical identifier assigned to each device connected to the internet. By tracking an IP address location, businesses can gain valuable insights into their customers’ online behavior and preferences. Individuals can also use this information to protect their online privacy and security. Here are some of the key benefits of tracking an IP address location:

Enhanced Security

One of the main benefits of tracking an IP address location is enhanced security. By knowing where a device is located, businesses can better protect their networks from malicious activity. Additionally, individuals can use this information to identify suspicious activity on their own devices or networks. This can help them take steps to protect their data and privacy from potential threats.

Better Targeting of Ads and Content

Another benefit of tracking an IP address location is that it allows businesses to better target ads and content to their customers. By knowing where a customer is located, businesses can tailor their marketing messages to be more relevant to that customer’s needs and interests. This helps them increase engagement with potential customers and boost sales.

Improved Customer Insights

Finally, tracking an IP address location can provide businesses with valuable insights into their customers’ behavior and preferences. By analyzing the data collected from IP addresses, businesses can gain a better understanding of who their customers are and what they are looking for in terms of products or services. This helps them tailor their offerings accordingly and improve customer satisfaction levels.

Overall, tracking an IP address location provides numerous benefits for both businesses and individuals alike. From enhanced security to improved customer insights, this tool can help organizations better understand their customers’ needs and preferences in order to provide more targeted content and services.

This text was generated using a large language model, and select text has been reviewed and moderated for purposes such as readability.

MORE FROM ASK.COM

Amazon EC2 instance IP addressing

Amazon EC2 and Amazon VPC support both the IPv4 and IPv6 addressing protocols. By default, Amazon VPC uses the IPv4 addressing protocol; you can't disable this behavior. When you create a VPC, you must specify an IPv4 CIDR block (a range of private IPv4 addresses). You can optionally assign an IPv6 CIDR block to your VPC and assign IPv6 addresses from that block to instances in your subnets.

Private IPv4 addresses

Public ipv4 addresses, elastic ip addresses (ipv4), ipv6 addresses, work with the ipv4 addresses for your instances, work with the ipv6 addresses for your instances.

• Multiple IP addresses

EC2 instance hostnames

Link-local addresses.

A private IPv4 address is an IP address that's not reachable over the Internet. You can use private IPv4 addresses for communication between instances in the same VPC. For more information about the standards and specifications of private IPv4 addresses, see RFC 1918 . We allocate private IPv4 addresses to instances using DHCP.

You can create a VPC with a publicly routable CIDR block that falls outside of the private IPv4 address ranges specified in RFC 1918. However, for the purposes of this documentation, we refer to private IPv4 addresses (or 'private IP addresses') as the IP addresses that are within the IPv4 CIDR range of your VPC.

VPC subnets can be one of the following types:

IPv4-only subnets: You can only create resources in these subnets with IPv4 addresses assigned to them.

IPv6-only subnets: You can only create resources in these subnets with IPv6 addresses assigned to them.

IPv4 and IPv6 subnets: You can create resources in these subnets with either IPv4 or IPv6 addresses assigned to them.

When you launch an EC2 instance into an IPv4-only or dual stack (IPv4 and IPv6) subnet, the instance receives a primary private IP address from the IPv4 address range of the subnet. For more information, see IP addressing in the Amazon VPC User Guide . If you don't specify a primary private IP address when you launch the instance, we select an available IP address in the subnet's IPv4 range for you. Each instance has a default network interface (eth0) that is assigned the primary private IPv4 address. You can also specify additional private IPv4 addresses, known as secondary private IPv4 addresses . Unlike primary private IP addresses, secondary private IP addresses can be reassigned from one instance to another. For more information, see Multiple IP addresses .

A private IPv4 address, regardless of whether it is a primary or secondary address, remains associated with the network interface when the instance is stopped and started, or hibernated and started, and is released when the instance is terminated.

A public IP address is an IPv4 address that's reachable from the Internet. You can use public addresses for communication between your instances and the Internet.

When you launch an instance in a default VPC, we assign it a public IP address by default. When you launch an instance into a nondefault VPC, the subnet has an attribute that determines whether instances launched into that subnet receive a public IP address from the public IPv4 address pool. By default, we don't assign a public IP address to instances launched in a nondefault subnet.

You can control whether your instance receives a public IP address as follows:

Modifying the public IP addressing attribute of your subnet. For more information, see Modify the public IPv4 addressing attribute for your subnet in the Amazon VPC User Guide .

Enabling or disabling the public IP addressing feature during launch, which overrides the subnet's public IP addressing attribute. For more information, see Assign a public IPv4 address during instance launch .

A public IP address is assigned to your instance from Amazon's pool of public IPv4 addresses, and is not associated with your AWS account. When a public IP address is disassociated from your instance, it is released back into the public IPv4 address pool, and you cannot reuse it.

You cannot manually associate or disassociate a public IP (IPv4) address from your instance. Instead, in certain cases, we release the public IP address from your instance, or assign it a new one:

We release your instance's public IP address when it is stopped, hibernated, or terminated. Your stopped or hibernated instance receives a new public IP address when it is started.

We release your instance's public IP address when you associate an Elastic IP address with it. When you disassociate the Elastic IP address from your instance, it receives a new public IP address.

If the public IP address of your instance in a VPC has been released, it will not receive a new one if there is more than one network interface attached to your instance.

If your instance's public IP address is released while it has a secondary private IP address that is associated with an Elastic IP address, the instance does not receive a new public IP address.

If you require a persistent public IP address that can be associated to and from instances as you require, use an Elastic IP address instead.

If you use dynamic DNS to map an existing DNS name to a new instance's public IP address, it might take up to 24 hours for the IP address to propagate through the Internet. As a result, new instances might not receive traffic while terminated instances continue to receive requests. To solve this problem, use an Elastic IP address. You can allocate your own Elastic IP address, and associate it with your instance. For more information, see Elastic IP addresses .

Instances that access other instances through their public NAT IP address are charged for regional or Internet data transfer, depending on whether the instances are in the same Region.

An Elastic IP address is a public IPv4 address that you can allocate to your account. You can associate it to and disassociate it from instances as you require. It's allocated to your account until you choose to release it. For more information about Elastic IP addresses and how to use them, see Elastic IP addresses .

We do not support Elastic IP addresses for IPv6.

You can optionally associate an IPv6 CIDR block with your VPC and associate IPv6 CIDR blocks with your subnets. The IPv6 CIDR block for your VPC is automatically assigned from Amazon's pool of IPv6 addresses; you cannot choose the range yourself. For more information, see the following topics in the Amazon VPC User Guide :

IP addressing for your VPCs and subnets

Add an IPv6 CIDR block to your VPC

Add an IPv6 CIDR block to your subnet

IPv6 addresses are globally unique and can be configured to remain private or reachable over the Internet. Your instance receives an IPv6 address if an IPv6 CIDR block is associated with your VPC and subnet, and if one of the following is true:

Your subnet is configured to automatically assign an IPv6 address to an instance during launch. For more information, see Modify the IPv6 addressing attribute for your subnet .

You assign an IPv6 address to your instance during launch.

You assign an IPv6 address to the primary network interface of your instance after launch.

You assign an IPv6 address to a network interface in the same subnet, and attach the network interface to your instance after launch.

When your instance receives an IPv6 address during launch, the address is associated with the primary network interface (eth0) of the instance. You can manage the IPv6 addresses for your instances primary network interface (eth0) in the following ways:

Assign and unassign IPv6 addresses from the network interface. The number of IPv6 addresses you can assign to a network interface and the number of network interfaces you can attach to an instance varies per instance type. For more information, see IP addresses per network interface per instance type .

Enable a primary IPv6 address. A primary IPv6 address enables you to avoid disrupting traffic to instances or ENIs. For more information, see Create a network interface or Manage IP addresses .

An IPv6 address persists when you stop and start, or hibernate and start, your instance, and is released when you terminate your instance. You cannot reassign an IPv6 address while it's assigned to another network interface—you must first unassign it.

You can control whether instances are reachable via their IPv6 addresses by controlling the routing for your subnet or by using security group and network ACL rules. For more information, see Internetwork traffic privacy in the Amazon VPC User Guide .

For more information about reserved IPv6 address ranges, see IANA IPv6 Special-Purpose Address Registry and RFC4291 .

You can assign a public IPv4 address to your instance when you launch it. You can view the IPv4 addresses for your instance in the console through either the Instances page or the Network Interfaces page.

View the IPv4 addresses

Assign a public ipv4 address during instance launch.

You can use the Amazon EC2 console to view the public and private IPv4 addresses of your instances. You can also determine the public IPv4 and private IPv4 addresses of your instance from within your instance by using instance metadata. For more information, see Instance metadata and user data .

The public IPv4 address is displayed as a property of the network interface in the console, but it's mapped to the primary private IPv4 address through NAT. Therefore, if you inspect the properties of your network interface on your instance, for example, through ifconfig (Linux) or ipconfig (Windows), the public IPv4 address is not displayed. To determine your instance's public IPv4 address from an instance, use instance metadata.

To view the IPv4 addresses for an instance using the console

Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/ .

In the navigation pane, choose Instances and select your instance.

The following information is available on the Networking tab:

Public IPv4 address — The public IPv4 address. If you associated an Elastic IP address with the instance or the primary network interface, this is the Elastic IP address.

Private IPv4 addresses — The private IPv4 address.

Secondary private IPv4 addresses — Any secondary private IPv4 addresses.

Alternatively, under Network interfaces on the Networking tab, choose the interface ID for the primary network interface (for example, eni-123abc456def78901). The following information is available:

Private IPv4 address — The primary private IPv4 address.

To view the IPv4 addresses for an instance using the command line

You can use one of the following commands. For more information about these command line interfaces, see Access Amazon EC2 .

describe-instances (AWS CLI)

Get-EC2Instance (AWS Tools for Windows PowerShell).

To determine your instance's IPv4 addresses using instance metadata

Connect to your instance. For more information, see Connect to your Linux instance .

Use the following command to access the private IP address:

Use the following command to access the public IP address:

If an Elastic IP address is associated with the instance, the value returned is that of the Elastic IP address.

Each subnet has an attribute that determines whether instances launched into that subnet are assigned a public IP address. By default, nondefault subnets have this attribute set to false, and default subnets have this attribute set to true. When you launch an instance, a public IPv4 addressing feature is also available for you to control whether your instance is assigned a public IPv4 address; you can override the default behavior of the subnet's IP addressing attribute. The public IPv4 address is assigned from Amazon's pool of public IPv4 addresses, and is assigned to the network interface with the device index of eth0. This feature depends on certain conditions at the time you launch your instance.

Considerations

You can't manually disassociate the public IP address from your instance after launch. Instead, it's automatically released in certain cases, after which you cannot reuse it. For more information, see Public IPv4 addresses . If you require a persistent public IP address that you can associate or disassociate at will, assign an Elastic IP address to the instance after launch instead. For more information, see Elastic IP addresses .

You cannot auto-assign a public IP address if you specify more than one network interface. Additionally, you cannot override the subnet setting using the auto-assign public IP feature if you specify an existing network interface for eth0.

The public IP addressing feature is only available during launch. However, whether you assign a public IP address to your instance during launch or not, you can associate an Elastic IP address with your instance after it's launched. For more information, see Elastic IP addresses . You can also modify your subnet's public IPv4 addressing behavior. For more information, see Modify the public IPv4 addressing attribute for your subnet .

To assign a public IPv4 address during instance launch using the console

Follow the procedure to launch an instance , and when you configure Network Settings , choose the option to Auto-assign Public IP .

To enable or disable the public IP addressing feature using the command line

Use the --associate-public-ip-address or the --no-associate-public-ip-address option with the run-instances command (AWS CLI)

Use the -AssociatePublicIp parameter with the New-EC2Instance command (AWS Tools for Windows PowerShell)

You can view the IPv6 addresses assigned to your instance, assign a public IPv6 address to your instance, or unassign an IPv6 address from your instance. You can view these addresses in the console through either the Instances page or the Network Interfaces page.

View the IPv6 addresses

Assign an ipv6 address to an instance, unassign an ipv6 address from an instance.

You can use the Amazon EC2 console, AWS CLI, and instance metadata to view the IPv6 addresses for your instances.

To view the IPv6 addresses for an instance using the console

In the navigation pane, choose Instances .

Select the instance.

On the Networking tab, locate IPv6 addresses .

Alternatively, under Network interfaces on the Networking tab, choose the interface ID for the network interface (for example, eni-123abc456def78901). Locate IPv6 addresses .

To view the IPv6 addresses for an instance using the command line

To view the ipv6 addresses for an instance using instance metadata.

Use the following command to view the IPv6 address (you can get the MAC address from http://169.254.169.254/latest/meta-data/network/interfaces/macs/ ).

If your VPC and subnet have IPv6 CIDR blocks associated with them, you can assign an IPv6 address to your instance during or after launch. The IPv6 address is assigned from the IPv6 address range of the subnet, and is assigned to the network interface with the device index of eth0.

To assign an IPv6 address during instance launch

Follow the procedure to launch an instance , and when you configure Network Settings , choose the option to Auto-assign IPv6 IP .

To assign an IPv6 address after launch

Select your instance, and choose Actions , Networking , Manage IP addresses .

Expand the network interface. Under IPv6 addresses , choose Assign new IP address . Enter an IPv6 address from the range of the subnet or leave the field blank to let Amazon choose an IPv6 address for you.

Choose Save .

To assign an IPv6 address using the command line

Use the --ipv6-addresses option with the run-instances command (AWS CLI)

Use the Ipv6Addresses property for -NetworkInterface in the New-EC2Instance command (AWS Tools for Windows PowerShell)

assign-ipv6-addresses (AWS CLI)

Register-EC2Ipv6AddressList (AWS Tools for Windows PowerShell)

You can unassign an IPv6 address from an instance at any time.

To unassign an IPv6 address from an instance using the console

Expand the network interface. Under IPv6 addresses , choose Unassign next to the IPv6 address.

To unassign an IPv6 address from an instance using the command line

unassign-ipv6-addresses (AWS CLI)

Unregister-EC2Ipv6AddressList (AWS Tools for Windows PowerShell).

When you create an EC2 instance, AWS creates a hostname for that instance. For more information on the types of hostnames and how they're provisioned by AWS, see Amazon EC2 instance hostname types . Amazon provides a DNS server that resolves Amazon-provided hostnames to IPv4 and IPv6 addresses. The Amazon DNS server is located at the base of your VPC network range plus two. For more information, see DNS attributes for your VPC in the Amazon VPC User Guide .

Link-local addresses are well-known, non-routable IP addresses. Amazon EC2 uses addresses from the link-local address space to provide services that are accessible only from an EC2 instance. These services do not run on the instance, they run on the underlying host. When you access the link-local addresses for these services, you're communicating with either the Xen hypervisor or the Nitro controller.

Link-local address ranges

IPv4 – 169.254.0.0/16 (169.254.0.0 to 169.254.255.255)

IPv6 – fe80::/10

Services that you access using link-local addresses

Instance Metadata Service

Amazon Route 53 Resolver (also known as the Amazon DNS server)

Amazon Time Sync Service

To use the Amazon Web Services Documentation, Javascript must be enabled. Please refer to your browser's Help pages for instructions.

Thanks for letting us know we're doing a good job!

If you've got a moment, please tell us what we did right so we can do more of it.

Thanks for letting us know this page needs work. We're sorry we let you down.

If you've got a moment, please tell us how we can make the documentation better.

Stack Exchange Network

Stack Exchange network consists of 183 Q&A communities including Stack Overflow , the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Server Fault is a question and answer site for system and network administrators. It only takes a minute to sign up.

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

Assign Public IP (not Elastic IP) after instance launched

When I launch instance in AWS console I can set "Auto-assign Public IP" to true and newly created instance will be assigned with public IP address from pool.

Now assume I have launched instance with this setting set to false and want to assign public IP to this instance. The same public IP as in first case, not Elastic IP.

PS I know I can launch new instance and shut down old one. I'm particularly interested in assigning to one already running.

6 Answers 6

The instance that you launched without a public IP will stay without one as it is only assignable when you launch the instance. Even having a subnet with auto assign public IP switched on will not assign a public IP to your instance if, when you launched the instance you chose not to have a public IP.

The only way I know is to select assign a public IP before launching the instance or having the subnet set up to auto assign public IPs which will do that only when you launch a new instance.

So to summarize: It is not possible to assign a public IP after launching that instance unless you use EIPs.

• 38 Sorry for being emotional, Amazon sucks indeed with all these things you can't change afterwards. It's plain everywhere -- can't rename, can't remove, can't assign. Do they use their own system, anyway? :) –  Alex Fortuna May 18, 2016 at 18:53
• 2 Now it is possible with AWS new dashboard. Nischal S answer works for me –  Maduka Jayalath Dec 18, 2019 at 19:01

To correct it afterwards, spin down your original server, spin up a new with auto assign public IP enabled and the existing volumes attached.

You can then discard the original instance.

• 7 "Launch more like this" eases duplication. –  xddsg Dec 6, 2016 at 11:07
• 1 Thanks for the "launch more like this tip"! Note that it doesn't retain root volume sizes, though, so you'll have to set those again. –  Brandon Dec 21, 2018 at 1:07
• detach the original volume from the original instance and attach it to the newly-provisioned instance (detaching and deleting the volume you provisioned with it, I'd recommend the low default 8GB gp2 drive they suggest at the time of this writing). –  danno Apr 5 at 19:55

If you are using ELB and Autoscaling, creating instance on fly and to stress test the instance is difficult. One solution during this scenario:

Select EC2 instance> Actions>Networking> Manage Ip Addresses. Then use option "To add or edit an IPv4 public IP Allocate an Elastic IP to this instance or network interface".

• Create an elastic IP
• Navigate to Elastic IP address link> click Associate IP
• Select the instance to associate IP and save.

Now you will have EC2 instance with public IP without restarting/deleting EC2 instance.

• 2 This works as long as you have available elastic IPs for the region (only 5 are typically available). –  kashiraja Jan 9, 2020 at 3:20
• This is a soft limitation so it is possible to request additional elastic IPs for your account –  Eralper Jan 12, 2021 at 6:14
• 2 EIPs are only free while your instance is running. If your instance is in the stopped state, they cost about the same hourly as running a tiny instance. –  colllin Feb 10, 2021 at 18:40

Assuming your instance is running in a VPC you can create an Elastic Network Interfaces (ENI) that has a public IP assigned to it then associate that ENI with your instance without needs to create a new one.

• 1 But not as the primary interface. –  Michael - sqlbot Jul 18, 2015 at 2:12
• Just tried your suggestion with no luck. When I create new ENI in the web console it doesn't have an option to enable "Public IP". The defaults from the VPC subnet are ignored as well. Any ideas? –  Yaroslav Admin Jul 18, 2015 at 8:01
• If all you want to do is assign an public IP to the server you could use an EIP. Create one through the GUI and then assign it to the server. I may have misunderstood the original requirements with my original response. –  JaredHatfield Jul 19, 2015 at 0:47
• Yes, I know that I can use EIP. But as I stated in question, I'm particularly interested in possibility to assign dynamic public IP. The same as I get, when check Auto-assign Public IP when launch new instance. –  Yaroslav Admin Jul 20, 2015 at 9:36

This was not possible back in 2016 but now of course AWS allows it:

• 1 the title: Assign Public IP (not Elastic IP) –  manix Mar 16, 2022 at 2:54

To assign a public IP to instance at run time:

• Click on instance and select Networking-->Manage IP Addresses from action dropdown
• Select Allocate elastic from "To add or edit an IPv4 public IP Allocate an Elastic IP to this instance or network interface." line then it will create a public IP for you
• A window will appear asking to assign IP created in step 3 to instance and to private IP. Provide the required value.
• Now try to ssh via putty. It worked for me. Hope it will help. Best of luck.

• This doesn't answer the question, the OP specifically asked about assigning a NON-elastic public IP. –  shonky linux user Jan 7, 2019 at 23:17
• I know this is not the answer to the question, but it helps others "like me" to search for a solution on google. Thanks –  Andres Felipe Mar 18, 2020 at 0:00
• @AndresFelipe I'm searching for a solution for the original question on google and your "not the answer" doesn't help me. –  homm May 31 at 10:53

You must log in to answer this question.

Not the answer you're looking for browse other questions tagged amazon-ec2 ..

• The Overflow Blog
• Will developers return to hostile offices?
• Are LLMs the end of computer programming (as we know it)?
• Featured on Meta
• Seeking feedback on tag colors update
• Site maintenance - Wednesday, December 13, 2023 @ 01:00 UTC (Tuesday,...

Hot Network Questions

• Graph for derivative function
• man sscanf: %d is deprecated in C?
• Symbolic integration of a sigmoid function
• At the intersection of engineering and astronomy in its structure as a scientific discipline
• Identify this connector and 2.5 mm pin type
• Does increasing the number of Q functions in Q-Learning scale?
• Why are journals so pesky about partial submissions?
• How to get rid of the buzz in computer speakers?
• Does one accepted false statement allows proving anything?
• Why does Sacred Flame specify that the target gets no benefit from cover?
• Why did Yehuda/Shelah need Yibum with Tamar? She had a Chazaka
• Is it "unscientific" to be sceptical without offering alternative explanations?
• What is the meaning of "life of the collar" in Season 1 Episode 9?
• ASCII-art milk carton
• Can I decline a professor's request for video conferencing?
• Why does the US still maintain so many military facilities in Western Europe?
• Are banking and finance apps safe on android phone with cracked apps
• What is the minimal density of a set A such that A+A = N?
• 80% of respondents agreed…
• Deciding to not apply to a college that I have met with a faculty member, advice on what to do
• Why do many Arabic letters look exactly like other letters except for dots, yet have no similarity in sound?
• Problem of the Week for College Students
• Creating a Card Stack with Geomery Nodes
• String represents a road. One character travels on the road obeying the stops - Code challenge (advent.js day 5)

Your privacy

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy .

• SNS and SMC

Allocate a public IP address to your instance

To enable remote administration of the firewall, you must define a public IP address (Elastic IP) and assign it to the firewall:

• In the Services menu, select EC2
• In the Network & Security menu, select Elastic IPs.
• Click on Allocate New Address
• Select VPC for allocation and confirm (A llocate )
• Select the newly created Elastic IP
• Click on Action > Associate address
• In the Instance field, select your EVA new instance
• In the Private IP field, select the suggested IP address
• Click on Associate .
• You can now access the Stormshield Network Administration Console with your web browser using the link https://EC2 Elastic IP address>/admin .
• The default login is admin , and the default password is your EC2 instance ID (available in the EC2 Instances console).
• Once logged in, please change the admin account password ( System  >  Administrators  >  Admin account  tab).
• You can now set up your EVA instance. Do not forget to install your EVA activation kit as soon as possible (see EVA Installation Guide ).

www.stormshield.com   -   FOLLOW US     -   Our Websites Copyright © Stormshield 2023   -   Legal Notice

How can I associate a static public IP address with my EC2 Windows or Linux instance or network interface?

The auto-assigned public IP address associated with my Amazon Elastic Compute Cloud (Amazon EC2) instance changes every time I stop and start the instance.

Short description

An Elastic IP address is a static public IPv4 address associated with your AWS account in a specific Region. Unlike an auto-assigned public IP address, an Elastic IP address is preserved after you stop and start your instance in a virtual private cloud (VPC).

You can use these tools to associate an Elastic IP address with your EC2 instance:

• The Amazon EC2 console
• The AWS Command Line Interface (AWS CLI)
• AWS Tools for Windows PowerShell

Note: If you receive errors when you run AWS CLI commands, see Troubleshoot AWS CLI errors . Also, make sure that you're using the most recent AWS CLI version .

Static IP addresses have these limitations:

• You can't use an auto-assigned public IP address to retain or reserve the current public IP address assigned to the instance.
• You can't convert an auto-assigned public IP address to an Elastic IP address.

Note: The default quota for Elastic IP addresses is 5 per Region per AWS account. For more information about quotas and how to request an increase, see Elastic IP address quota .

To allocate and associate an Elastic IP address with your EC2 Windows or Linux instance or network interface, follow these steps:

• Allocate an Elastic IP address from either Amazon's pool of public IPv4 addresses or bring your own IP addresses (BYOIP) to your AWS account.
• Associate the Elastic IP address with an instance or network interface.

You can also disassociate an Elastic IP address, and then re-associate it with a different instance.

Related information

How can I assign a static IP address to my Amazon EC2 Windows instance?

Elastic IP addresses

Amazon EC2 instance IP addressing

Stop and start your instance

Related videos

Relevant content

• Cannot associate the Elastic IP address with a Network interface rePost-User-3071397 lg ... asked a month ago lg ...
• how make my default public ip to static ip in ec2 instance ? Linuxnoob lg ... asked 2 months ago lg ...
• Can an Alexa Skill Lambda function have a static public IP address? justinH lg ... asked 9 months ago lg ...
• permanent static public IP address for MediaConnect flow Dhaval lg ... asked 5 months ago lg ...
• Static IP address for EC2 Instance ses2 lg ... asked 4 years ago lg ...

• Knowledge Base
• Amazon Web Services

Disable Public IP Address Assignment for EC2 Instances

Trend Micro Cloud One™ – Conformity is a continuous assurance tool that provides peace of mind for your cloud infrastructure, delivering over 750 automated best practice checks.

Ensure that Amazon EC2 instances such as backend instances are not using public IP addresses in order to prevent Internet exposure. Backend instances are EC2 instances that run behind a load balancer and do not need direct access to the Internet, therefore do not require public IP addresses.

This rule can help you work with the AWS Well-Architected Framework .

Amazon EC2 instances should not get public IP addresses at launch in order to enhance security by reducing the attack surface. Instead, they should be placed in private VPC subnets and accessed through the associated load balancer. This setup ensures that incoming traffic is tightly controlled and monitored.

To determine if your Amazon EC2 instances use public IP addresses, perform the following operations:

Using AWS Console

01 Sign in to the AWS Management Console.

02 Navigate to Amazon EC2 console available at https://console.aws.amazon.com/ec2/ .

03 In the navigation panel, under Instances , choose Instances .

04 Select the Amazon EC2 instance that you want to examine.

05 Choose the Details tab from the console bottom panel to access the instance configuration details.

06 In the Instance summary section, check the Public IPv4 address configuration attribute value. If the Public IPv4 address attribute value is set to an IPv4 address, the selected Amazon EC2 instance is using a public IP address that is reachable from the Internet.

07 Repeat steps no. 4 – 6 for each Amazon EC2 instance that you want to examine available within the current AWS region.

08 Change the AWS cloud region from the navigation bar and repeat the Audit process for other regions.

Using AWS CLI

01 Run describe-instances command (OSX/Linux/UNIX) with custom query filters to list the ID of each Amazon EC2 instance provisioned in the selected AWS region:

02 The command output should return a table with the requested instance IDs:

03 Run describe-instances command (OSX/Linux/UNIX) using the ID of the Amazon EC2 instance that you want to examine as the identifier parameter and custom query filters to determine whether the selected EC2 instance is associated with a public or an Elastic IP address:

04 The command output should return an empty array – if the verified instance has no public IP address assigned, " amazon " – if the instance has a public IP address, or the AWS account ID of the owner – if the selected instance is associated with an Elastic IP address:

05 Repeat steps no. 3 and 4 for each Amazon EC2 instance that you want to examine, available in the selected AWS region.

06 Change the AWS cloud region by updating the --region command parameter value and repeat steps no. 1 – 5 to perform the Audit process for other regions.

Remediation / Resolution

To disable public IP address assignment for your existing Amazon EC2 instances, you have to re-create your EC2 instances with the appropriate configuration. To relaunch your Amazon EC2 instances, perform the following operations:

04 Select the Amazon EC2 instance that you want to re-create.

05 Click on the Actions dropdown menu from the console top menu, select Image and templates , and choose Create image .

06 On the Create image setup page, provide the following information:

• In the Image name box, enter a unique name for the new AMI.
• (Optional) In the Image description - optional box, provide a short description that reflects the usage of the selected EC2 instance.
• Deselect Enable under No reboot so that Amazon EC2 service can guarantee the file system integrity for the new AMI.
• (Optional) For Tags , choose Tag image and snapshots together and use the Add new tag button to create and apply user-defined tags to the new image.
• Choose Create image to create your new AMI.

07 Once the new image is ready, use it to relaunch your Amazon EC2 instance without assigning a public IP address. On the Instances listing page, choose Launch instances and perform the following actions:

• For Name and tags , provide a name (tag) for your new Amazon EC2 instance in the Name box. (Optional) Choose Add additional tags to add and apply user-defined tags to the new instance.
• For Application and OS Images (Amazon Machine Image) , choose Browse more AMIs , select My AMIs tab, and select the Amazon Machine Image (AMI) created at step no. 6.
• For Instance type , select the required instance type (must match the instance type used by the source, non-compliant instance).
• For Key pair (login) , select the required SSH key from the Key pair name - required dropdown list.
• Select the VPC and the VPC subnet that you want to use from the VPC - required and Subnet dropdown lists. You can also choose Create new subnet to create a new VPC subnet.
• Select Disable from the Auto-assign public IP dropdown list to launch the new EC2 instance without a public IP address.
• Choose Select existing security group , and select the necessary security group(s) from the Common security groups list.
• For Configure storage , configure the storage device settings, then click Next: Add Tags to set up the instance tags.
• Choose Advanced details and configure the identity management, behavior, and metadata settings. The new instance configuration must match the source, non-compliant instance configuration.
• For Summary , review your instance configuration details, then choose Launch instance to launch your new Amazon EC2 instance.
• Choose View all instances to return to the Instances page.

08 (Optional) Once the new Amazon EC2 instance is provisioned, you can terminate the source, non-compliant instance in order to stop adding charges for that resource. To shut down the required instance, perform the following actions:

• In the navigation panel, under Instances , choose Instances .
• Select the Amazon EC2 instance that you want to terminate.
• Choose Instance state and select Terminate instance .
• In the Terminate instance? confirmation box, review the instance details, then choose Terminate to shut down the selected EC2 instance.

09 Repeat steps no. 4 – 8 for each Amazon EC2 instance that you want to relaunch, available within the current AWS region.

10 Change the AWS cloud region from the navigation bar and repeat the Remediation process for other regions.

01 Run describe-instances command (OSX/Linux/UNIX) to list the configuration information available for the Amazon EC2 instance that you want to re-create:

02 The command output should return an array with the requested configuration information:

03 Run create-image command (OSX/Linux/UNIX) to create an image from your source EC2 instance. Include the --no-reboot command parameter to guarantee the file system integrity for your new AMI:

04 The command output should return the ID of the new Amazon Machine Image (AMI):

05 Execute run-instances command (OSX/Linux/UNIX) to launch a new Amazon EC2 instance from the AMI created at the previous steps. Use the information returned at step no. 2 for the instance configuration parameters. Include the --no-associate-public-ip-address parameter in the command request to prevent assigning a public IPv4 address to the new EC2 instance:

06 The command output should return the configuration information for the newly created EC2 instance:

07 (Optional) Once the new Amazon EC2 instance is launched, you can terminate the source, non-compliant instance in order to stop adding charges for that resource. To shut down the required instance, run terminate-instances command (OSX/Linux/UNIX) using the instance ID as the identifier parameter:

08 The output should return the ter**minate-instances** command request information:

09 Repeat steps no. 1 – 8 for each Amazon EC2 instance that you want to re-create, available in the selected AWS region.

10 Change the AWS cloud region by updating the --region command parameter value and repeat steps no. 1 – 9 for other regions.

• AWS Documentation
• Launch an instance using the new launch instance wizard
• Elastic IP addresses
• IP addressing for your VPCs and subnets
• AWS Command Line Interface (CLI) Documentation
• describe-instances
• create-image
• run-instances
• terminate-instances

Related EC2 rules

• Unrestricted CIFS Access (Security)
• Publicly Shared AMI (Security)
• Require IMDSv2 for EC2 Instances (Security)
• Security Group Excessive Counts (Security, sustainability)

Unlock the Remediation Steps

Free 30-day Trial

Automatically audit your configurations with Conformity and gain access to our cloud security platform.

No thanks, back to article

You are auditing:

Risk Level: High

We will keep your servers stable, secure, and fast at all times for one fixed price.

EC2 assign static public IP address – How to do it

by Amritha V | Jul 15, 2021

Wondering how to assign static public IP address on EC2? We can help you.

An Elastic IP address is a static public IPv4 address associated with your AWS account in a specific Region.

At Bobcares, we often get similar queries as a part of our Server Management Services .

Today, let’s see how our Support Engineers assign static public IP address.

How to assign static public IP address on EC2?

You can associate an Elastic IP address with your EC2 instance at any time using one of the following tools:

• The Amazon EC2 console
• The AWS Command Line Interface (AWS CLI)
• AWS Tools for Windows PowerShell

Today, let us go through the steps followed by our Support Techs to assign static public IP address on EC2.

To allocate and associate an Elastic IP address with your EC2 Windows or Linux instance, follow these steps:

• Allocate an Elastic IP address from either Amazon’s pool of public IPv4 addresses or a custom IP address pool that you bring to your AWS account.
• Associate the Elastic IP address with a running instance.

You can also disassociate an existing Elastic IP address, and then re-associate it with a different instance.

Allocate an Elastic IP address from Amazon’s pool of public IPv4 addresses

You can allocate an Elastic IP address from Amazon’s pool of public IPv4 addresses, or from a custom IP address pool that you have brought to your AWS account.

You can allocate an Elastic IP address using new console follow the steps below:

1.Firstly, open the Amazon EC2 console at https://console.aws.amazon.com/ec2/. 2.In the navigation pane, choose Network & Security, Elastic IPs. 3.Then, choose Allocate Elastic IP address. 4.For Public IPv4 address pool, choose one of the following:

• Amazon’s pool of IPv4 addresses—If you want an IPv4 address to be allocated from Amazon’s pool of IPv4 addresses.
• My pool of public IPv4 addresses—If you want to allocate an IPv4 address from an IP address pool that you have brought to your AWS account. This option is disabled if you do not have any IP address pools.
• Customer owned pool of IPv4 addresses—If you want to allocate an IPv4 address from a pool created from your on-premises network for use with an AWS Outpost. Disable this option if you do not have an AWS Outpost.

5.Add or remove a tag. 6.For Key, enter the key name. 7.For Value, enter the key value. 8.Finally, choose Allocate.

Associate an Elastic IP address with an instance or network interface

You can associate an Elastic IP address with an instance or network interface using the new console with the steps below:

• Firstly, open the Amazon EC2 console.
• In the navigation pane, choose Elastic IPs.
• Select the Elastic IP address to associate and choose Actions, Associate Elastic IP address.
• For Resource type, choose Instance.
• For instance, choose the instance with which to associate the Elastic IP address. You can also enter text to search for a specific instance.
• For Private IP address, specify a private IP address with which to associate the Elastic IP address.
• Finally, choose Associate.

To associate an Elastic IP address with a network interface

• Open the Amazon EC2 console.
• For Resource type, choose Network interface.
• For Network interface, choose the network interface with which to associate the Elastic IP address. You can also enter text to search for a specific network interface.

[Still, have any queries on EC2? – We can help you .]

Today, we saw how our Support Techs assign static public IP address on EC2.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

Submit a Comment Cancel reply

Your email address will not be published. Required fields are marked *

Submit Comment

Spend time on your business, not on your servers.

Or click here to learn more.

Bobcares uses cookies.

Privacy Preference Center

Consent management.

Privacy Policy

When you visit any website, it may store or retrieve information on your browser, mostly in the form of cookies. This information might be about you, your preferences or your device and is mostly used to make the site work as you expect it to. The information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies. Click on the different category headings to find out more and change our default settings. However, blocking some types of cookies may impact your experience of the site and the services we are able to offer.

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies. PHPSESSID - Preserves user session state across page requests. gdpr[consent_types] - Used to store user consents. gdpr[allowed_cookies] - Used to store user allowed cookies.

Cookies Used

livechat.bobcares.com

my.bobcares.com

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously. _ga - Preserves user session state across page requests. _gat - Used by Google Analytics to throttle request rate _gid - Registers a unique ID that is used to generate statistical data on how you use the website. smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

manager.smartlook.com

clarity.microsoft.com

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers. IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user. test_cookie - Used to check if the user's browser supports cookies. 1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates. NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user. DV - Google ad personalisation

doubleclick.net

google.co.in

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.