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/utilities/custom_resources.md
+7-1
Original file line number
Diff line number
Diff line change
@@ -45,7 +45,7 @@ Inside the methods, implement your custom provisioning logic, and return a `Resp
45
45
46
46
Custom resources notify cloudformation either of `SUCCESS` or `FAILED` status. You have 2 utility methods to represent these responses: `Response.success(physicalResourceId)` and `Response.failed(physicalResourceId)`.
47
47
The `physicalResourceId` is an identifier that is used during the lifecycle operations of the Custom Resource.
48
-
You should supply a `physicalResourceId` during the `CREATE` operation, CloudFormation stores the `physicalResourceId` and includes it `UPDATE` and `DELETE` events.
48
+
You should generate a `physicalResourceId` during the `CREATE` operation, CloudFormation stores the `physicalResourceId` and includes it `UPDATE` and `DELETE` events.
49
49
50
50
Here an example of how to implement a Custom Resource using the powertools-cloudformation library:
51
51
@@ -167,7 +167,10 @@ with the Fn::GetAtt function.
0 commit comments