Use third-party private extensions that have been shared with you
To use third-party private extensions that have been shared with you, you must first register them with CloudFormation, in the accounts and Regions where you want to use them. Registering the extension uploads a copy of it to the CloudFormation registry in your account, and activates it. Once you're registered a private extension, it will appear in the CloudFormation registry for that AWS account and Region, and you can use it in your stack templates.
Topics
IAM permissions for registering a third-party private extension
As part of registering a private extension, you might specify an Amazon S3 bucket that contains the extension project package. This package contains any source files necessary for the extension you want to register. The user registering the extension must be able to access the project package in that Amazon S3 bucket. To do so, the user must have GetObject permissions for the extension package.
This is true whether you're either using the register-type command of the AWS CLI, or the submit command of the CloudFormation CLI.
For more information, see Actions, Resources, and Condition Keys for Amazon S3 in the Service Authorization Reference.
Commonly used AWS CLI commands for working with private extensions
The commonly used commands for working with private extensions include:
-
register-type to register a private extension in your account.
-
describe-type-registration to return the current status of a registration request.
-
list-types to list the extensions in your account.
-
describe-type to return detailed information about a specific extension or specific extension version, including current configuration data.
-
set-type-configuration to specify the configuration data for an extension in your account and to disable and enable Hooks.
-
set-type-default-version to specify which version of an extension is the default version.
-
deregister-type to remove a private extension or extension version from your account.
