Documentation: Update aws.md

[mule-bob]

Description

Addressing typos in aws.md:

external-dns/docs/tutorials/aws.md

Line 127 in cc82c6b

With the instnace host name, you can then get the instance id:

external-dns/docs/tutorials/aws.md

Line 100 in cc82c6b

From the comand line, if you have a single managed node group, the default with `eksctl create cluster`, you can find the role name with the following:

external-dns/docs/tutorials/aws.md

Line 115 in cc82c6b

If you have multiple node groups or any unmanaged node groups, the process gets more complex. The first step is to get the instance host name of the destired node to where ExternalDNS will be deployed or is already deployed:

external-dns/docs/tutorials/aws.md

Line 160 in cc82c6b

# get all the instances with this associated instance prfile

external-dns/docs/tutorials/aws.md

Line 197 in cc82c6b

This method is not the preferred method as the secrets in the credential file could be copied and used by an unauthorized threat actor. However, if the Kubernetes cluster is not hosted on AWS, it may be the only method available. Given this situation, it is important to limit the associated privileges to just minimal requried privileges, i.e. read-write access to Route53, and not used a credentials file that has extra privileges beyond what is required.

external-dns/docs/tutorials/aws.md

Line 568 in cc82c6b

For this verification phase, you can can use default or another namespace for the nginx demo, for example:

external-dns/docs/tutorials/aws.md

Line 704 in cc82c6b

This shold show something like:

external-dns/docs/tutorials/aws.md

Line 726 in cc82c6b

For this tutorial, we have two endpoints, the service with `LoadBalancer` type and an ingress. For practical purposes, if an ingress is used, the service type can be changed to `ClusterIP` as two endpoints are unecessary in this scenario.

external-dns/docs/tutorials/aws.md

Line 909 in cc82c6b

Delete any uneeded policies:

Checklist

• Unit tests updated
• End user documentation updated

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: mule-bob / name: Bobby Argenbright (138ac3d, 894f8e3)

[k8s-ci-robot]

Welcome @mule-bob!

It looks like this is your first PR to kubernetes-sigs/external-dns 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/external-dns has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[szuecs]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mule-bob, szuecs

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [szuecs]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[szuecs]

@mule-bob thanks!

[szuecs]

/lgtm