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
{{ message }}
This repository was archived by the owner on May 20, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: docs/providers/pulumi/aws/index.mdx
+10-8Lines changed: 10 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -55,23 +55,25 @@ You can create an Access Key by logging into the [AWS console](https://aws.amazo
55
55
for full details on credentials and configuration.
56
56
</Note>
57
57
58
-
## Locating resources deployed with Nitric
58
+
## Locating deployed resources
59
59
60
-
Nitric creates a resource tag manager group and tags all possible resources to be referenced by this group. You can locate resources in the console by going to the [AWS Console](https://console.aws.amazon.com/)
60
+
This Nitric AWS provider creates a resource tag manager group and tags all possible resources to be referenced by this group. You can locate resources using the [AWS Console](https://console.aws.amazon.com/).
61
61
62
-
Navigate to the resource groups service:
62
+
Start by navigating to the [Resource Groups service](https://console.aws.amazon.com/resource-groups/home):
63
63
64
64

65
65
66
-
Find your resource group in the resource groups list and click it:
66
+
Find your stack's resource group in the list and click it:
67
67
68
-

68
+
<Note>
69
+
Resource groups are conventionally named `<project-name>-<stack-name>`
69
70
70
-
Resource groups are conventionally named `<project-name>-<stack-name>`
71
+
In this example the project name is `api-testing` and the stack name is `aws`.
72
+
</Note>
71
73
72
-
So in the example above, the project name is `api-testing` and the stack name is `aws`.
74
+

73
75
74
-
More recent versions of the Nitric AWS provider also output a direct link to it's resource group in the console from running `nitric up`
76
+
More recent versions of the Nitric AWS provider also display a direct link to the resource group in output from `nitric up`.
Nitric deploys all Azure resources for a stack into a resource group dedicated to that stack. You can either use one your already have by configuring it in the stack configuration or let Nitric create one for you.
80
+
This Nitric Azure provider deploys resources for a stack into a resource group dedicated to that stack. You can either use one your already have by configuring it in the stack configuration or let Nitric create one for you.
81
81
82
-
Once a nitric stack is deployed to azure it's resource group should be present in the [Resource groups](https://portal.azure.com/#blade/HubsExtension/BrowseResourceGroupBlade/resourceType/Microsoft.Resources%2Fsubscriptions%2FresourceGroups) page of your portal. Assuming it was deployed to a subscription you have access to.
82
+
Once a stack has been deployed to Azure it's resource group should be present in the [Resource groups](https://portal.azure.com/#blade/HubsExtension/BrowseResourceGroupBlade/resourceType/Microsoft.Resources%2Fsubscriptions%2FresourceGroups) page of the portal. Assuming it was deployed to a subscription you have access to.
83
83
84
-
Resource groups are named conventionally `<project-name>-<stack-name>-<randomId>`
84
+
<Note>
85
+
Resource groups are conventionally named `<project-name>-<stack-name>-<randomId>`
85
86
86
-
For example:
87
-

87
+
In this example the project name is `api-testing` and the stack name is `az`.
88
+
</Note>
88
89
89
-
So in the example above, the project name is `api-testing` and the stack name is `az`.
90
+

90
91
91
-
More recent versions of the Nitric Azure provider also output a direct link to it's resource group in the console from running `nitric up`
92
+
More recent versions of the Nitric Azure provider display a direct link to the resource group in output from `nitric up`.
Copy file name to clipboardExpand all lines: docs/providers/terraform/aws.mdx
+8-7Lines changed: 8 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,22 +70,23 @@ You can create an Access Key by logging into the [AWS console](https://aws.amazo
70
70
for full details on credentials and configuration.
71
71
</Note>
72
72
73
-
## Locating resources deployed with Nitric
73
+
## Locating deployed resources
74
74
75
75
Nitric creates a resource tag manager group and tags all possible resources to be referenced by this group. You can locate resources in the console by going to the [AWS Console](https://console.aws.amazon.com/)
76
76
77
-
Navigate to the resource groups service:
77
+
Next, navigate to the [Resource Groups service](https://console.aws.amazon.com/resource-groups/home):
78
78
79
79

80
80
81
-
Find your resource group in the resource groups list and click it:
81
+
Find your stack's resource group in the list and click it:
82
82
83
-

84
-
85
-
Resource groups are conventionally named `<project-name>-<stack-name>`
83
+
<Note>
84
+
Resource groups are conventionally named `<project-name>-<stack-name>`
86
85
87
-
So in the example above, the project name is `api-testing` and the stack name is `aws`.
86
+
In this example the project name is `api-testing` and the stack name is `aws`.
87
+
</Note>
88
88
89
+

0 commit comments