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
@@ -101,7 +101,7 @@ In both of the scenarios, powertools-java will assign the `physicalResourceId` b
101
101
- if present, use the `physicalResourceId` provided in the `CloudFormationCustomResourceEvent`
102
102
- if it is not present, use the `LogStreamName` from the Lambda context
103
103
104
-
#### Why does this matter?
104
+
#### Why do you need a physicalResourceId?
105
105
106
106
It is recommended that you always provide a `physicalResourceId` in your response because `physicalResourceId` has a crucial role in the lifecycle of a CloudFormation custom resource.
107
107
If the `physicalResourceId` changes between calls from Cloudformation, for instance in response to an `Update` event, Cloudformation [treats the resource update as a replacement](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cfn-customresource.html).
@@ -114,7 +114,7 @@ You customise the responses when you need additional attributes to be shared wit
114
114
In the example below, the Lambda function creates a [Chime AppInstance](https://docs.aws.amazon.com/chime/latest/dg/create-app-instance.html)
115
115
and maps the returned ARN to a "ChimeAppInstanceArn" attribute.
0 commit comments