You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/hopsworksai/aws/restrictive_permissions.md
+8-2Lines changed: 8 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,12 +12,18 @@ Hopsworks.ai to only access resources in a specific VPC.
12
12
To restrict Hopsworks.ai from accessing resources outside of a specific VPC, you need to create a new VPC
13
13
connected to an Internet Gateway. This can be achieved in the AWS Management Console following this guide:
14
14
[Create the VPC](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-getting-started.html#getting-started-create-vpc).
15
-
The option VPC with a Single Public Subnet from the Launch VPC Wizard should work out of the box.
15
+
The option VPC with a `Single Public Subnet` from the Launch VPC Wizard should work out of the box.
16
16
Alternatively, an existing VPC such as the default VPC can be used and Hopsworks.ai will be restricted to this VPC.
17
17
Note the VPC ID of the VPC you want to use for the following steps.
18
18
19
19
!!! note
20
-
The VPC and its Network ACLs need to be configured so that at least port 80 is reachable from the internet or creating Hopsworks instances will fail when creating SSL certificates. DNS hostnames need to be enabled as well.
20
+
Make sure you enable `DNS hostnames` for your VPC
21
+
22
+
After you have created the VPC either [Create a Security Group](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_SecurityGroups.html#CreatingSecurityGroups) or use VPC's default.
23
+
24
+
!!! note
25
+
The [Security Group](https://docs.aws.amazon.com/vpc/latest/userguide/VPC_SecurityGroups.html#AddRemoveRules) and/or [Network ACLs](https://docs.aws.amazon.com/vpc/latest/userguide/vpc-network-acls.html#Rules)
26
+
need to be configured so that at least port `80` is reachable from the internet otherwise creating Hopsworks instances will fail when creating SSL certificates.
0 commit comments