|
22 | 22 | "OpenVPN" |
23 | 23 | ], |
24 | 24 | "short_description": "Creates client-to-site VPN connectivity to VPC", |
25 | | - "long_description": "Some VPC patterns are configured with private networks not available over the internet. To access these networks, there are several connectivity options. This deployable architecture pattern configures the client-to-site VPN Server connectivity with only a few required inputs to configure it within an existing VPC. Once deployed, you can install an OpenVPN client application and import a profile from the VPN Server on the devices you want to access the VPN. The configuration can include a list of users that will be provided access to the private network, controlled by IBM Cloud IAM.", |
| 25 | + "long_description": "Some VPC patterns are configured with private networks not available over the internet. To access these networks, there are several connectivity options. This deployable architecture pattern configures the client-to-site VPN Server connectivity with only a few required inputs to configure it within an existing VPC. Once deployed, you can install an [OpenVPN client application](https://cloud.ibm.com/docs/vpc?topic=vpc-setting-up-vpn-client) and import a profile from the VPN Server on the devices you want to access the VPN. The configuration can include a list of users that will be provided access to the private network, controlled by IBM Cloud IAM.\n\nℹ️ This Terraform-based automation is part of a broader suite of IBM-maintained Infrastructure as Code (IaC) assets, each following the naming pattern \"Cloud automation for *servicename*\" and focusing on single IBM Cloud service. These single-service deployable architectures can be used on their own to streamline and automate service deployments through an [IaC approach](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-understanding-projects), or assembled together into a broader [automated IaC stack](https://cloud.ibm.com/docs/secure-enterprise?topic=secure-enterprise-config-stack) to automate the deployment of an end-to-end solution architecture.", |
26 | 26 | "offering_docs_url": "https://github.com/terraform-ibm-modules/terraform-ibm-client-to-site-vpn/blob/main/solutions/fully-configurable/README.md", |
27 | 27 | "offering_icon_url": "https://raw.githubusercontent.com/terraform-ibm-modules/terraform-ibm-client-to-site-vpn/main/images/c2s_vpn.svg", |
28 | 28 | "provider_name": "IBM", |
29 | 29 | "support_details": "This product is in the community registry, as such support is handled through the originated repo. If you experience issues please open an issue in the repository [https://github.com/terraform-ibm-modules/terraform-ibm-client-to-site-vpn/issues](https://github.com/terraform-ibm-modules/terraform-ibm-client-to-site-vpn/issues). Please note this product is not supported via the IBM Cloud Support Center.", |
30 | 30 | "features": [ |
31 | 31 | { |
32 | | - "description": "Supports using an existing Secrets Manager instance, to create a secret group and a new private cert.", |
33 | | - "title": "Configures existing Secrets Manager instance, and create a secret group and a new private cert." |
| 32 | + "description": "Secrets Manager", |
| 33 | + "title": "Supports configuring an existing [Secrets Manager](https://cloud.ibm.com/docs/secrets-manager?topic=secrets-manager-getting-started) instance to create a secret group and a new private certificate." |
34 | 34 | }, |
35 | 35 | { |
36 | | - "description": "The network ACL on this subnet grants the access from sources according to the rules defined with 'network_acls' input variable.", |
37 | | - "title": "A subnet named 'client-to-site-subnet' in the VPC" |
| 36 | + "description": "ACL rules", |
| 37 | + "title": "The [network ACL](https://cloud.ibm.com/docs/vpc?topic=vpc-configuring-acls-vpn) on the `client-to-site-subnet` subnet grants access based on the rules defined by the `network_acls` input variable." |
38 | 38 | }, |
39 | 39 | { |
40 | | - "description": "A new security group named 'client-to-site-sg' that allows incoming request from sources defined in'security_group_rules'", |
41 | | - "title": "client-to-site Security Group" |
| 40 | + "description": "Security group", |
| 41 | + "title": "Creates a new [security group](https://cloud.ibm.com/docs/security-groups?topic=security-groups-about-ibm-security-groups) named `client-to-site-sg` that allows incoming requests from sources defined in the `security_group_rules` input variable." |
42 | 42 | }, |
43 | 43 | { |
44 | | - "description": "An IAM access group allowing users to authenticate and connect to the client-to-site VPN gateway", |
45 | | - "title": "A new IAM Access Group for VPN users" |
| 44 | + "description": "IAM access group", |
| 45 | + "title": "Creates an [IAM access group](https://cloud.ibm.com/docs/account?topic=account-groups&interface=ui) that allows users to authenticate and connect to the client-to-site VPN gateway." |
46 | 46 | }, |
47 | 47 | { |
48 | | - "description": "VPN gateway located in the client-to-site-subnet subnet with routes configured to allow accessing the VPCs.", |
49 | | - "title": "A client-to-site VPN server" |
| 48 | + "description": "VPN gateway", |
| 49 | + "title": "Creates a [VPN gateway](https://cloud.ibm.com/docs/vpc?topic=vpc-using-vpn) in the `client-to-site-subnet` subnet, with routes configured to allow access to the VPCs." |
50 | 50 | } |
51 | 51 | ], |
52 | 52 | "flavors": [ |
53 | 53 | { |
54 | 54 | "label": "Fully configurable", |
55 | 55 | "name": "fully-configurable", |
| 56 | + "index": 1, |
56 | 57 | "install_type": "fullstack", |
57 | 58 | "working_directory": "solutions/fully-configurable", |
58 | 59 | "dependency_version_2": true, |
|
101 | 102 | }, |
102 | 103 | { |
103 | 104 | "key": "prefix", |
104 | | - "required": true |
| 105 | + "value_constraints": [ |
| 106 | + { |
| 107 | + "type": "regex", |
| 108 | + "description": "Prefix must begin with a lowercase letter and may contain only lowercase letters, digits, and hyphens '-'. It must not end with a hyphen ('-'), and cannot contain consecutive hyphens ('--'). It should not exceed 16 characters.", |
| 109 | + "value": "^$|^__NULL__$|^[a-z](?!.*--)(?:[a-z0-9-]{0,14}[a-z0-9])?$" |
| 110 | + } |
| 111 | + ] |
105 | 112 | }, |
106 | 113 | { |
107 | 114 | "key": "vpn_name", |
|
281 | 288 | "displayname": "public-and-private", |
282 | 289 | "value": "public-and-private" |
283 | 290 | } |
284 | | - ] |
| 291 | + ], |
| 292 | + "hidden": true |
285 | 293 | } |
286 | 294 | ], |
287 | 295 | "iam_permissions": [ |
288 | 296 | { |
289 | 297 | "role_crns": [ |
290 | | - "crn:v1:bluemix:public:iam::::role:Administrator" |
| 298 | + "crn:v1:bluemix:public:iam::::role:Viewer" |
291 | 299 | ], |
292 | | - "service_name": "iam-identity" |
| 300 | + "service_name": "Resource group only", |
| 301 | + "notes": "Viewer access is required in the resource group you want to provision in." |
293 | 302 | }, |
294 | 303 | { |
295 | 304 | "role_crns": [ |
296 | | - "crn:v1:bluemix:public:iam::::role:Administrator" |
| 305 | + "crn:v1:bluemix:public:iam::::role:Editor" |
297 | 306 | ], |
298 | | - "service_name": "is.vpc" |
| 307 | + "service_name": "iam-identity", |
| 308 | + "notes": "Required for defining IAM access groups, policies, and members for controlled access." |
| 309 | + }, |
| 310 | + { |
| 311 | + "role_crns": [ |
| 312 | + "crn:v1:bluemix:public:iam::::role:Editor" |
| 313 | + ], |
| 314 | + "service_name": "is.vpc", |
| 315 | + "notes": "Required to manage and modify VPC resources." |
299 | 316 | } |
300 | 317 | ], |
301 | 318 | "architecture": { |
302 | 319 | "features": [ |
303 | 320 | { |
304 | | - "title": "Supports OpenVPN Clients", |
305 | | - "description": "Yes" |
306 | | - }, |
307 | | - { |
308 | | - "title": "Separate IAM access list for VPN users", |
309 | | - "description": "Yes" |
310 | | - }, |
311 | | - { |
312 | | - "title": "Separate secured VPC subnets for VPN Server", |
313 | | - "description": "Yes" |
314 | | - }, |
315 | | - { |
316 | | - "title": "ACL that controls the access from different source", |
317 | | - "description": "Yes" |
318 | | - }, |
319 | | - { |
320 | | - "title": "Security group that restricts the incoming request from different source", |
321 | | - "description": "Yes" |
322 | | - }, |
323 | | - { |
324 | | - "title": "IBM-managed VPN Server", |
325 | | - "description": "Yes" |
326 | | - }, |
327 | | - { |
328 | | - "title": "Access to private network via VPN clients", |
329 | | - "description": "Yes" |
| 321 | + "title": " ", |
| 322 | + "description": "Configured to use IBM secure by default standards, but can be edited to fit your use case." |
330 | 323 | } |
331 | 324 | ], |
332 | 325 | "diagrams": [ |
333 | 326 | { |
334 | 327 | "diagram": { |
335 | 328 | "caption": "Client-to-site VPN configuration.", |
336 | | - "url": "https://raw.githubusercontent.com/terraform-ibm-modules/terraform-ibm-client-to-site-vpn/main/reference-architectures/reference-architectures/cts-fully-configurable-da.svg", |
| 329 | + "url": "https://raw.githubusercontent.com/terraform-ibm-modules/terraform-ibm-client-to-site-vpn/main/reference-architectures/reference-architectures/deployable-architecture-cts.svg", |
337 | 330 | "type": "image/svg+xml" |
338 | 331 | }, |
339 | 332 | "description": "Client-to-site VPN configuration." |
|
0 commit comments