Ubuntu 18.04 added. DB tier added.

[Vadim-Zenin]

Two-tier example's update

Changes proposed in this pull request:

• Old Ubuntu AMIs replaced with Ubuntu 18.04
• DB tier added
• DB instance, Security Group added
• ELB configuration fixed
• variables.tf extended
• README.md updated

Output from acceptance testing:

$ terraform apply

Apply complete! Resources: 12 added, 0 changed, 0 destroyed.

Outputs:

db_private_ip = 10.0.160.88
db_public_ip = 54.169.31.85
elb_dns_name = test02-elb-1339856605.ap-southeast-1.elb.amazonaws.com
web_private_ip = 10.0.0.42
web_public_ip = 52.77.209.127
...

[zhelding]

Pull request #21306 has significantly refactored the AWS Provider codebase. As a result, most PRs opened prior to the refactor now have merge conflicts that must be resolved before proceeding.

Specifically, PR #21306 relocated the code for all AWS resources and data sources from a single aws directory to a large number of separate directories in internal/service, each corresponding to a particular AWS service. This separation of code has also allowed for us to simplify the names of underlying functions -- while still avoiding namespace collisions.

We recognize that many pull requests have been open for some time without yet being addressed by our maintainers. Therefore, we want to make it clear that resolving these conflicts in no way affects the prioritization of a particular pull request. Once a pull request has been prioritized for review, the necessary changes will be made by a maintainer -- either directly or in collaboration with the pull request author.

For a more complete description of this refactor, including examples of how old filepaths and function names correspond to their new counterparts: please refer to issue #20000.

For a quick guide on how to amend your pull request to resolve the merge conflicts resulting from this refactor and bring it in line with our new code patterns: please refer to our Service Package Refactor Pull Request Guide.

[github-actions]

Marking this pull request as stale due to inactivity. This helps our maintainers find and focus on the active pull requests. If this pull request receives no comments in the next 30 days it will automatically be closed. Maintainers can also remove the stale label.

If this pull request was automatically closed and you feel this pull request should be reopened, we encourage creating a new pull request linking back to this one for added context. Thank you!

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.