Examples of using Custom resources in English and their translations into German
{-}
-
Colloquial
-
Official
-
Ecclesiastic
-
Medicine
-
Financial
-
Ecclesiastic
-
Political
-
Computer
-
Programming
-
Official/political
-
Political
Custom resources provided by your own applications or services.
You can include those resources by using custom resources.
Information about custom resources is provided in the following topics.
AWS CloudFormation then compares the PhysicalResourceIDs of old and new custom resources.
Custom resources must send responses to a pre-signed Amazon S3 URL.
For more information, see Custom Resources or the AWS Lambda Developer Guide.
Walkthrough: Using Amazon Simple Notification Service to Create Custom Resources.
Add your own custom resources and actions to Peakon's Improve area.
Note that the walkthrough assumes that you understand how to use custom resources and Lambda.
You can update custom resources that require a replacement of the underlying physical resource. .
For more information about how you can use a Lambda function with AWS CloudFormation custom resources, see AWS Lambda-backed Custom Resources.
Custom resources require one property: the service token, which specifies where AWS CloudFormation sends requests to, such as an Amazon SNS topic.
Whenever you delete a stack or make an update that removes or replaces the custom resource, AWS CloudFormation compares the PhysicalResourceId between the old and new custom resources.
If a template includes custom resources or wait conditions in a VPC, the VPC endpoint policy must allow users to send responses to the following buckets.
By using custom resources and AWS Lambda(Lambda), you can create a function that gets the IDs of the latest AMIs for the region and instance type that you're using so that you don't have to maintain mappings.
Custom resources enable you to write custom provisioning logic in templates that AWS CloudFormation runs anytime you create, update(if you changed the custom resource), or delete stacks.
As a result, AWS and custom resources can be created, provisioned, updated, or terminated automatically during a pipeline execution according to the specifications you provide in AWS CloudFormation templates and parameter definitions.
Any output data from the custom resource is stored in the pre-signed URL location.
Replacing a Custom Resource During an Update.
Using an AWS Lambda function in a custom resource.
The custom resource provider must provide a service token that the template developer uses.
The custom resource provider processes the data sent by AWS CloudFormation.
The template developer deletes a stack that contains a custom resource.
This value should be an identifier unique to the custom resource vendor, and can be up to 1 Kb in size.
Depending on the custom resource, the input data might be required; however, the service token is always required.
When you associate an Amazon SNS topic with a custom resource, you use Amazon SNS notifications to triggercustom provisioning logic.
The following example shows a custom resource Create request which includes a custom resource type name,Custom:: SeleniumTester, created with a LogicalResourceId of MySeleniumTester.
If you didn't make changes to the custom resource, AWS CloudFormation won't send requests to it during a stack update.
Whenever anyone uses the template to create, update, or delete a custom resource, AWS CloudFormation sends a request to the specified service token.
For this walkthrough, you will create a stack with a custom resource, a Lambda function, and an EC2 instance.