How can I get a fixed public IP address for my instance?

The public IP address of your instance changes every time you stop or start it. To prevent this and get a fixed IP, you can associate an EIP to the instance that you make persistent using the tags.osc.fcu.eip.auto-attach tag. That way, every time you stop or start the instance, the same EIP is associated with it. 

To associate the EIP with the instance, you can use the External IPs page on Cockpit, or the AWS CLI. For more information, see External IP Addresses (EIPs).

You can then add the tag to the instance in the user data, or using a regular tag (with osc.fcu.eip.auto-attach as Key and your EIP as Value). For more information, see Configuring an Instance with User Data and OUTSCALE Tags or Tagging Your Resources.


How can I link an EIP to an instance persistently?

By default, the EIP is dissociated from the instance every time you stop or start it.

For a persistent association, you can add the osc.fcu.eip.auto-attach tag to the instance, using a regular tag (with osc.fcu.eip.auto-attach as Key and your EIP as Value) or the user data. For more information, see Configuring an Instance with User Data and OUTSCALE Tags.


What ranges of public IP addresses can my instances have?


RegionPublic IP Ranges
eu-west-2
  • 5.104.96.0/21 (5.104.96.0-5.104.103.255)
  • 80.247.0.0/21 (80.247.0.0-80.247.7.255)
  • 109.232.232.0/21 (109.232.232.0-109.232.239.255)
  • 148.253.64.0/19 (148.253.64.0-148.253.95.255)
  • 148.253.100.0/22 (148.253.100.0-148.253.103.255)
  • 148.253.104.0/21 (148.253.104.0-148.253.111.255)
  • 148.253.112.0/20 (148.253.112.0-148.253.127.255)
  • 171.33.64.0/23 (171.33.64.0-171.33.65.255)
  • 171.33.68.0/22 (171.33.68.0-171.33.71.255)
  • 171.33.72.0/21 (171.33.72.0-171.33.79.255)
  • 171.33.80.0/20 (171.33.80.0-171.33.95.255)
  • 171.33.96.0/19 (171.33.96.0-171.33.127.255)
  • 217.75.160.0/20 (217.75.160.0-217.75.175.255)
us-east-2
  • 157.250.32.0/20 (157.250.32.0-157.250.47.255)
  • 157.250.48.0/21 (157.250.48.0-157.250.55.255)
  • 157.250.56.0/22 (157.250.56.0-157.250.59.255)
us-west-1
  • 157.250.24.0/22 (157.250.24.0-157.250.27.255)
  • 157.250.28.0/23 (157.250.28.0-157.250.29.255)
cloudgouv-eu-west-1
  • 148.253.96.0/23 (148.253.96.0-148.253.97.255)

  • 185.21.194.0/25 (185.21.194.0-185.21.194.127)

ap-northeast-1
  • 24.230.24.0/22 (24.230.24.0-24.230.27.255)

  • 24.230.28.0/23 (24.230.28.0-24.230.29.255)

  • 24.230.30.0/24 (24.230.30.0-24.230.30.255)

For more information, see OUTSCALE Public IP Addresses.


How can I synchronize my instances with 3DS OUTSCALE NTP servers?

Each Region of the 3DS OUTSCALE Cloud uses its own NTP servers, that then synchronize with public NTP servers available in the Region.

To synchronize your instances, you can use the public IP addresses of 3DS OUTSCALE NTP servers: 


RegionAvailability ZoneOUTSCALE NTP Servers
eu-west-2eu-west-2a

46.231.146.12

46.231.144.179

eu-west-2b

46.231.146.12

46.231.144.179

us-east-2us-east-2a

199.244.93.242

199.244.93.243

us-east-2b

199.244.93.242

199.244.93.243

us-west-1us-west-1a

157.250.31.66

157.250.31.67

cloudgouv-eu-west-1cloudgouv-eu-west-1a

46.231.144.141

46.231.144.142

ap-northeast-1ap-northeast-1a

24.230.16.67

24.230.16.11

ap-northeast-1b

24.230.16.67

24.230.16.11

For more information, see OUTSCALE NTP Servers.


Can I limit the bandwidth of my instance? Of all my instances?

You can use the "tc" Linux tool to directly limit bandwidth in your instance.


With what network appliances can I connect to 3DS OUTSCALE devices through VPN?

All IPSEC-compliant appliances are supported, for example: 


How can I improve network connectivity on my CentOS instance?

Network connectivity issues may arise on instances launched from official CentOs 6 or CentOS 7 OMIs (OUTSCALE machine images).

To apply the official 3DS OUTSCALE patch:


  1. Download the patch in RPM format:
  2. To apply the patch, run the following command in a terminal of your instance, using the name of the file you downloaded at Step 1:

    $ rpm -ivh PATCH_FILE_NAME.rpm
  3. To activate the patch, restart your network service. 
    The network connectivity on your instance is now restored.  

    This action may take a few minutes to be effective.




AWS™ and Amazon Web Services™ are trademarks of Amazon Technologies, Inc or its affiliates in the United States and/or other countries.