选择您的 Cookie 首选项

我们使用必要 Cookie 和类似工具提供我们的网站和服务。我们使用性能 Cookie 收集匿名统计数据,以便我们可以了解客户如何使用我们的网站并进行改进。必要 Cookie 无法停用,但您可以单击“自定义”或“拒绝”来拒绝性能 Cookie。

如果您同意,AWS 和经批准的第三方还将使用 Cookie 提供有用的网站功能、记住您的首选项并显示相关内容,包括相关广告。要接受或拒绝所有非必要 Cookie,请单击“接受”或“拒绝”。要做出更详细的选择,请单击“自定义”。

DNS friendly bastion names

聚焦模式
DNS friendly bastion names - AMS Advanced User Guide
此页面尚未翻译为您的语言。 请求翻译

AWS Managed Services (AMS) uses DNS friendly bastion names.

MALZ

For Multi-account landing zone (MALZ), DNS records are created for the bastions in the FQDN of the AMS-managed Active Directory. AMS replaces Linux and Windows bastions as required. For example, if there is a new bastion AMI that must be deployed, the bastion DNS records dynamically update to point to new, valid bastions.

  1. To access SSH (Linux) bastions, use DNS records like this: sshbastion(1-4).Your_Domain.com

    For example, where the domain is Your_Domain:

    • sshbastion1.Your_Domain.com

    • sshbastion2.Your_Domain.com

    • sshbastion3.Your_Domain.com

    • sshbastion4.Your_Domain.com

  2. To access RDP (Windows) bastions, use DNS records like this: rdp-Username.Your_Domain.com.

    For example, where the user name is alex, test, demo, or bob, and the domain is Your_Domain.com:

    • rdp-alex.Your_Domain.com

    • rdp-test.Your_Domain.com

    • rdp-demo.Your_Domain.com

    • rdp-bob.Your_Domain.com

SALZ

Single-account landing zone (SALZ) replaces Linux and Windows bastions as required. For example, if there is a new bastion AMI that must be deployed, the bastion DNS records dynamically update to point to new, valid bastions.

  1. To access SSH (Linux) bastions, use DNS records like this: sshbastion(1-4).AAccountNumber.amazonaws.com.

    For example, where 123456789012 is the account number:

    • sshbastion1.A123456789012.amazonaws.com

    • sshbastion2.A123456789012.amazonaws.com

    • sshbastion3.A123456789012.amazonaws.com

    • sshbastion4.A123456789012.amazonaws.com

  2. To access RDP (Windows) bastions, use DNS records like this: rdpbastion(1-4).AACCOUNT_NUMBER.amazonaws.com.

    For example, where 123456789012 is the account number:

    • rdpbastion1.A123456789012.amazonaws.com

    • rdpbastion2.A123456789012.amazonaws.com

    • rdpbastion3.A123456789012.amazonaws.com

    • rdpbastion4.A123456789012.amazonaws.com

For Multi-account landing zone (MALZ), DNS records are created for the bastions in the FQDN of the AMS-managed Active Directory. AMS replaces Linux and Windows bastions as required. For example, if there is a new bastion AMI that must be deployed, the bastion DNS records dynamically update to point to new, valid bastions.

  1. To access SSH (Linux) bastions, use DNS records like this: sshbastion(1-4).Your_Domain.com

    For example, where the domain is Your_Domain:

    • sshbastion1.Your_Domain.com

    • sshbastion2.Your_Domain.com

    • sshbastion3.Your_Domain.com

    • sshbastion4.Your_Domain.com

  2. To access RDP (Windows) bastions, use DNS records like this: rdp-Username.Your_Domain.com.

    For example, where the user name is alex, test, demo, or bob, and the domain is Your_Domain.com:

    • rdp-alex.Your_Domain.com

    • rdp-test.Your_Domain.com

    • rdp-demo.Your_Domain.com

    • rdp-bob.Your_Domain.com

隐私网站条款Cookie 首选项
© 2025, Amazon Web Services, Inc. 或其附属公司。保留所有权利。