mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
83 lines
2.3 KiB
Plaintext
83 lines
2.3 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * rosa_hcp/rosa-hcp-quickstart-guide.adoc
|
|
// * rosa_hcp/rosa-hcp-egress-zero-install.adoc
|
|
// * rosa_hcp/rosa-hcp-creating-cluster-with-aws-kms-key.adoc
|
|
// * rosa_hcp/rosa-hcp-sts-creating-a-cluster-quickly.adoc
|
|
|
|
ifeval::["{context}" == "rosa-hcp-egress-zero-install"]
|
|
:rosa-egress-lockdown:
|
|
endif::[]
|
|
|
|
:_mod-docs-content-type: PREFERENCE
|
|
[id="rosa-hcp-vpc-manual_{context}"]
|
|
= Creating an AWS Virtual Private Cloud manually
|
|
|
|
If you choose to manually create your AWS Virtual Private Cloud (VPC) instead of using Terraform, go to link:https://us-east-1.console.aws.amazon.com/vpc/[the VPC page in the AWS console].
|
|
|
|
include::snippets/rosa-existing-vpc-requirements.adoc[leveloffset=+0]
|
|
|
|
ifdef::rosa-egress-lockdown[]
|
|
[discrete]
|
|
[id="rosa-hcp-vpc-subnet-tagging-manual_{context}"]
|
|
== Tagging your subnets
|
|
|
|
Before you can use your VPC to create a {product-title} cluster, you must tag your VPC subnets. Automated service preflight checks verify that these resources are tagged correctly. The following table shows how to tag your resources:
|
|
|
|
[cols="3a,8a,8a", options="header"]
|
|
|===
|
|
| Resource
|
|
| Key
|
|
| Value
|
|
|
|
| Public subnet
|
|
| `kubernetes.io/role/elb`
|
|
| `1` or no value
|
|
|
|
| Private subnet
|
|
| `kubernetes.io/role/internal-elb`
|
|
| `1` or no value
|
|
|
|
|===
|
|
|
|
[NOTE]
|
|
====
|
|
You must tag at least one private subnet and one public subnet, if applicable.
|
|
====
|
|
|
|
. Tag your resources in your terminal:
|
|
.. For public subnets, run the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ aws ec2 create-tags --resources <public_subnet_id> --region <aws_region> --tags Key=kubernetes.io/role/elb,Value=1
|
|
----
|
|
.. For private subnets, run the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ aws ec2 create-tags --resources <private_subnet_id> --region <aws_region> --tags Key=kubernetes.io/role/internal-elb,Value=1
|
|
----
|
|
|
|
.Verification
|
|
|
|
* Verify that the tag is correct by running the following command:
|
|
+
|
|
[source,terminal]
|
|
----
|
|
$ aws ec2 describe-tags --filters "Name=resource-id,Values=<subnet_id>"
|
|
----
|
|
+
|
|
.Example output
|
|
+
|
|
[source,text]
|
|
----
|
|
TAGS Name <subnet_id> subnet <prefix>-subnet-public1-us-east-1a
|
|
TAGS kubernetes.io/role/elb <subnet_id> subnet 1
|
|
----
|
|
endif::rosa-egress-lockdown[]
|
|
|
|
ifeval::["{context}" == "rosa-hcp-egress-zero-install"]
|
|
:!rosa-egress-lockdown:
|
|
endif::[]
|