NAT Service

outscaleNAT gatewayoutscale-nat-service

Outbound address translation letting VMs of a Net reach the internet through one public IP.

Provider
outscale
Category
Edge
Properties · 3 set by this component
propertytypevaluesrequiredkind defaultthis component
idleTimeoutMinutesinteger—no—inherited
loggingboolean—nofalseinherited
managedboolean—nofalse▸ true
publicIpRequired · component propertyboolean—notrueinherited
publicSubnetRequired · component propertyboolean—notrueinherited
servesMultipleSubnets · component propertyboolean—notrueinherited
staticIpCountinteger—no—▸ 1
zoneRedundantboolean—no—▸ false
Rules that apply · 0

Every rule whose selector covers this component's kind or its category. Whether a rule fires depends on the design: its properties, its edges and its groups.

No rule reads this kind yet. That is a gap, not a guarantee.
Use it in a design
nodes:
  - { id: "nat-service", component: "outscale-nat-service" }
Other NAT gateway products · 8
Source
# yaml-language-server: $schema=../../schema/component.schema.json
# OUTSCALE NAT Service: outbound-only address translation letting VMs in a Net reach the
# internet through one shared public IP ("About NAT Services"). That page states the facts
# behind the defaults: a single public IP per NAT service, creation inside one Subnet that
# must route to an internet service, several Subnets of the same Net served by one NAT
# service, and outbound security group rules required on the VMs.
schemaVersion: "1"
type: "component"
id: "outscale-nat-service"
kind: "nat-gateway"
provider: "outscale"
docs: "https://docs.outscale.com/en/userguide/About-NAT-Services.html"
defaults:
  managed: true
  staticIpCount: 1
  zoneRedundant: false
properties:
  publicIpRequired:
    type: "boolean"
    default: true
  publicSubnetRequired:
    type: "boolean"
    default: true
  servesMultipleSubnets:
    type: "boolean"
    default: true

The same page as markdown, for an agent: /catalogue/components/outscale-nat-service.md