We recommend new projects start with resources from the AWS provider.
aws-native.amplify.App
Explore with Pulumi AI
We recommend new projects start with resources from the AWS provider.
The AWS::Amplify::App resource creates Apps in the Amplify Console. An App is a collection of branches.
Create App Resource
Resources are created with functions called constructors. To learn more about declaring and configuring resources, see Resources.
Constructor syntax
new App(name: string, args?: AppArgs, opts?: CustomResourceOptions);
@overload
def App(resource_name: str,
args: Optional[AppArgs] = None,
opts: Optional[ResourceOptions] = None)
@overload
def App(resource_name: str,
opts: Optional[ResourceOptions] = None,
access_token: Optional[str] = None,
auto_branch_creation_config: Optional[AppAutoBranchCreationConfigArgs] = None,
basic_auth_config: Optional[AppBasicAuthConfigArgs] = None,
build_spec: Optional[str] = None,
cache_config: Optional[AppCacheConfigArgs] = None,
custom_headers: Optional[str] = None,
custom_rules: Optional[Sequence[AppCustomRuleArgs]] = None,
description: Optional[str] = None,
enable_branch_auto_deletion: Optional[bool] = None,
environment_variables: Optional[Sequence[AppEnvironmentVariableArgs]] = None,
iam_service_role: Optional[str] = None,
name: Optional[str] = None,
oauth_token: Optional[str] = None,
platform: Optional[AppPlatform] = None,
repository: Optional[str] = None,
tags: Optional[Sequence[_root_inputs.TagArgs]] = None)
func NewApp(ctx *Context, name string, args *AppArgs, opts ...ResourceOption) (*App, error)
public App(string name, AppArgs? args = null, CustomResourceOptions? opts = null)
type: aws-native:amplify:App
properties: # The arguments to resource properties.
options: # Bag of options to control resource's behavior.
Parameters
- name string
- The unique name of the resource.
- args AppArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- resource_name str
- The unique name of the resource.
- args AppArgs
- The arguments to resource properties.
- opts ResourceOptions
- Bag of options to control resource's behavior.
- ctx Context
- Context object for the current deployment.
- name string
- The unique name of the resource.
- args AppArgs
- The arguments to resource properties.
- opts ResourceOption
- Bag of options to control resource's behavior.
- name string
- The unique name of the resource.
- args AppArgs
- The arguments to resource properties.
- opts CustomResourceOptions
- Bag of options to control resource's behavior.
- name String
- The unique name of the resource.
- args AppArgs
- The arguments to resource properties.
- options CustomResourceOptions
- Bag of options to control resource's behavior.
App Resource Properties
To learn more about resource properties and how to use them, see Inputs and Outputs in the Architecture and Concepts docs.
Inputs
In Python, inputs that are objects can be passed either as argument classes or as dictionary literals.
The App resource accepts the following input properties:
- Access
Token string The personal access token for a GitHub repository for an Amplify app. The personal access token is used to authorize access to a GitHub repository using the Amplify GitHub App. The token is not stored.
Use
AccessToken
for GitHub repositories only. To authorize access to a repository provider such as Bitbucket or CodeCommit, useOauthToken
.You must specify either
AccessToken
orOauthToken
when you create a new app.Existing Amplify apps deployed from a GitHub repository using OAuth continue to work with CI/CD. However, we strongly recommend that you migrate these apps to use the GitHub App. For more information, see Migrating an existing OAuth app to the Amplify GitHub App in the Amplify User Guide .
- Auto
Branch Pulumi.Creation Config Aws Native. Amplify. Inputs. App Auto Branch Creation Config - Sets the configuration for your automatic branch creation.
- Basic
Auth Pulumi.Config Aws Native. Amplify. Inputs. App Basic Auth Config - The credentials for basic authorization for an Amplify app. You must base64-encode the authorization credentials and provide them in the format
user:password
. - Build
Spec string - The build specification (build spec) for an Amplify app.
- Cache
Config Pulumi.Aws Native. Amplify. Inputs. App Cache Config - The cache configuration for the Amplify app. If you don't specify the cache configuration
type
, Amplify uses the defaultAMPLIFY_MANAGED
setting. - Custom
Headers string - The custom HTTP headers for an Amplify app.
- Custom
Rules List<Pulumi.Aws Native. Amplify. Inputs. App Custom Rule> - The custom rewrite and redirect rules for an Amplify app.
- Description string
- The description of the Amplify app.
- Enable
Branch boolAuto Deletion - Automatically disconnect a branch in Amplify Hosting when you delete a branch from your Git repository.
- Environment
Variables List<Pulumi.Aws Native. Amplify. Inputs. App Environment Variable> The environment variables for the Amplify app.
For a list of the environment variables that are accessible to Amplify by default, see Amplify Environment variables in the Amplify Hosting User Guide .
- Iam
Service stringRole - AWS Identity and Access Management ( IAM ) service role for the Amazon Resource Name (ARN) of the Amplify app.
- Name string
- The name of the Amplify app.
- Oauth
Token string The OAuth token for a third-party source control system for an Amplify app. The OAuth token is used to create a webhook and a read-only deploy key using SSH cloning. The OAuth token is not stored.
Use
OauthToken
for repository providers other than GitHub, such as Bitbucket or CodeCommit. To authorize access to GitHub as your repository provider, useAccessToken
.You must specify either
OauthToken
orAccessToken
when you create a new app.Existing Amplify apps deployed from a GitHub repository using OAuth continue to work with CI/CD. However, we strongly recommend that you migrate these apps to use the GitHub App. For more information, see Migrating an existing OAuth app to the Amplify GitHub App in the Amplify User Guide .
- Platform
Pulumi.
Aws Native. Amplify. App Platform The platform for the Amplify app. For a static app, set the platform type to
WEB
. For a dynamic server-side rendered (SSR) app, set the platform type toWEB_COMPUTE
. For an app requiring Amplify Hosting's original SSR support only, set the platform type toWEB_DYNAMIC
.If you are deploying an SSG only app with Next.js version 14 or later, you must set the platform type to
WEB_COMPUTE
and set the artifactsbaseDirectory
to.next
in the application's build settings. For an example of the build specification settings, see Amplify build settings for a Next.js 14 SSG application in the Amplify Hosting User Guide .- Repository string
- The Git repository for the Amplify app.
- List<Pulumi.
Aws Native. Inputs. Tag> - The tag for an Amplify app.
- Access
Token string The personal access token for a GitHub repository for an Amplify app. The personal access token is used to authorize access to a GitHub repository using the Amplify GitHub App. The token is not stored.
Use
AccessToken
for GitHub repositories only. To authorize access to a repository provider such as Bitbucket or CodeCommit, useOauthToken
.You must specify either
AccessToken
orOauthToken
when you create a new app.Existing Amplify apps deployed from a GitHub repository using OAuth continue to work with CI/CD. However, we strongly recommend that you migrate these apps to use the GitHub App. For more information, see Migrating an existing OAuth app to the Amplify GitHub App in the Amplify User Guide .
- Auto
Branch AppCreation Config Auto Branch Creation Config Args - Sets the configuration for your automatic branch creation.
- Basic
Auth AppConfig Basic Auth Config Args - The credentials for basic authorization for an Amplify app. You must base64-encode the authorization credentials and provide them in the format
user:password
. - Build
Spec string - The build specification (build spec) for an Amplify app.
- Cache
Config AppCache Config Args - The cache configuration for the Amplify app. If you don't specify the cache configuration
type
, Amplify uses the defaultAMPLIFY_MANAGED
setting. - Custom
Headers string - The custom HTTP headers for an Amplify app.
- Custom
Rules []AppCustom Rule Args - The custom rewrite and redirect rules for an Amplify app.
- Description string
- The description of the Amplify app.
- Enable
Branch boolAuto Deletion - Automatically disconnect a branch in Amplify Hosting when you delete a branch from your Git repository.
- Environment
Variables []AppEnvironment Variable Args The environment variables for the Amplify app.
For a list of the environment variables that are accessible to Amplify by default, see Amplify Environment variables in the Amplify Hosting User Guide .
- Iam
Service stringRole - AWS Identity and Access Management ( IAM ) service role for the Amazon Resource Name (ARN) of the Amplify app.
- Name string
- The name of the Amplify app.
- Oauth
Token string The OAuth token for a third-party source control system for an Amplify app. The OAuth token is used to create a webhook and a read-only deploy key using SSH cloning. The OAuth token is not stored.
Use
OauthToken
for repository providers other than GitHub, such as Bitbucket or CodeCommit. To authorize access to GitHub as your repository provider, useAccessToken
.You must specify either
OauthToken
orAccessToken
when you create a new app.Existing Amplify apps deployed from a GitHub repository using OAuth continue to work with CI/CD. However, we strongly recommend that you migrate these apps to use the GitHub App. For more information, see Migrating an existing OAuth app to the Amplify GitHub App in the Amplify User Guide .
- Platform
App
Platform The platform for the Amplify app. For a static app, set the platform type to
WEB
. For a dynamic server-side rendered (SSR) app, set the platform type toWEB_COMPUTE
. For an app requiring Amplify Hosting's original SSR support only, set the platform type toWEB_DYNAMIC
.If you are deploying an SSG only app with Next.js version 14 or later, you must set the platform type to
WEB_COMPUTE
and set the artifactsbaseDirectory
to.next
in the application's build settings. For an example of the build specification settings, see Amplify build settings for a Next.js 14 SSG application in the Amplify Hosting User Guide .- Repository string
- The Git repository for the Amplify app.
- Tag
Args - The tag for an Amplify app.
- access
Token String The personal access token for a GitHub repository for an Amplify app. The personal access token is used to authorize access to a GitHub repository using the Amplify GitHub App. The token is not stored.
Use
AccessToken
for GitHub repositories only. To authorize access to a repository provider such as Bitbucket or CodeCommit, useOauthToken
.You must specify either
AccessToken
orOauthToken
when you create a new app.Existing Amplify apps deployed from a GitHub repository using OAuth continue to work with CI/CD. However, we strongly recommend that you migrate these apps to use the GitHub App. For more information, see Migrating an existing OAuth app to the Amplify GitHub App in the Amplify User Guide .
- auto
Branch AppCreation Config Auto Branch Creation Config - Sets the configuration for your automatic branch creation.
- basic
Auth AppConfig Basic Auth Config - The credentials for basic authorization for an Amplify app. You must base64-encode the authorization credentials and provide them in the format
user:password
. - build
Spec String - The build specification (build spec) for an Amplify app.
- cache
Config AppCache Config - The cache configuration for the Amplify app. If you don't specify the cache configuration
type
, Amplify uses the defaultAMPLIFY_MANAGED
setting. - custom
Headers String - The custom HTTP headers for an Amplify app.
- custom
Rules List<AppCustom Rule> - The custom rewrite and redirect rules for an Amplify app.
- description String
- The description of the Amplify app.
- enable
Branch BooleanAuto Deletion - Automatically disconnect a branch in Amplify Hosting when you delete a branch from your Git repository.
- environment
Variables List<AppEnvironment Variable> The environment variables for the Amplify app.
For a list of the environment variables that are accessible to Amplify by default, see Amplify Environment variables in the Amplify Hosting User Guide .
- iam
Service StringRole - AWS Identity and Access Management ( IAM ) service role for the Amazon Resource Name (ARN) of the Amplify app.
- name String
- The name of the Amplify app.
- oauth
Token String The OAuth token for a third-party source control system for an Amplify app. The OAuth token is used to create a webhook and a read-only deploy key using SSH cloning. The OAuth token is not stored.
Use
OauthToken
for repository providers other than GitHub, such as Bitbucket or CodeCommit. To authorize access to GitHub as your repository provider, useAccessToken
.You must specify either
OauthToken
orAccessToken
when you create a new app.Existing Amplify apps deployed from a GitHub repository using OAuth continue to work with CI/CD. However, we strongly recommend that you migrate these apps to use the GitHub App. For more information, see Migrating an existing OAuth app to the Amplify GitHub App in the Amplify User Guide .
- platform
App
Platform The platform for the Amplify app. For a static app, set the platform type to
WEB
. For a dynamic server-side rendered (SSR) app, set the platform type toWEB_COMPUTE
. For an app requiring Amplify Hosting's original SSR support only, set the platform type toWEB_DYNAMIC
.If you are deploying an SSG only app with Next.js version 14 or later, you must set the platform type to
WEB_COMPUTE
and set the artifactsbaseDirectory
to.next
in the application's build settings. For an example of the build specification settings, see Amplify build settings for a Next.js 14 SSG application in the Amplify Hosting User Guide .- repository String
- The Git repository for the Amplify app.
- List<Tag>
- The tag for an Amplify app.
- access
Token string The personal access token for a GitHub repository for an Amplify app. The personal access token is used to authorize access to a GitHub repository using the Amplify GitHub App. The token is not stored.
Use
AccessToken
for GitHub repositories only. To authorize access to a repository provider such as Bitbucket or CodeCommit, useOauthToken
.You must specify either
AccessToken
orOauthToken
when you create a new app.Existing Amplify apps deployed from a GitHub repository using OAuth continue to work with CI/CD. However, we strongly recommend that you migrate these apps to use the GitHub App. For more information, see Migrating an existing OAuth app to the Amplify GitHub App in the Amplify User Guide .
- auto
Branch AppCreation Config Auto Branch Creation Config - Sets the configuration for your automatic branch creation.
- basic
Auth AppConfig Basic Auth Config - The credentials for basic authorization for an Amplify app. You must base64-encode the authorization credentials and provide them in the format
user:password
. - build
Spec string - The build specification (build spec) for an Amplify app.
- cache
Config AppCache Config - The cache configuration for the Amplify app. If you don't specify the cache configuration
type
, Amplify uses the defaultAMPLIFY_MANAGED
setting. - custom
Headers string - The custom HTTP headers for an Amplify app.
- custom
Rules AppCustom Rule[] - The custom rewrite and redirect rules for an Amplify app.
- description string
- The description of the Amplify app.
- enable
Branch booleanAuto Deletion - Automatically disconnect a branch in Amplify Hosting when you delete a branch from your Git repository.
- environment
Variables AppEnvironment Variable[] The environment variables for the Amplify app.
For a list of the environment variables that are accessible to Amplify by default, see Amplify Environment variables in the Amplify Hosting User Guide .
- iam
Service stringRole - AWS Identity and Access Management ( IAM ) service role for the Amazon Resource Name (ARN) of the Amplify app.
- name string
- The name of the Amplify app.
- oauth
Token string The OAuth token for a third-party source control system for an Amplify app. The OAuth token is used to create a webhook and a read-only deploy key using SSH cloning. The OAuth token is not stored.
Use
OauthToken
for repository providers other than GitHub, such as Bitbucket or CodeCommit. To authorize access to GitHub as your repository provider, useAccessToken
.You must specify either
OauthToken
orAccessToken
when you create a new app.Existing Amplify apps deployed from a GitHub repository using OAuth continue to work with CI/CD. However, we strongly recommend that you migrate these apps to use the GitHub App. For more information, see Migrating an existing OAuth app to the Amplify GitHub App in the Amplify User Guide .
- platform
App
Platform The platform for the Amplify app. For a static app, set the platform type to
WEB
. For a dynamic server-side rendered (SSR) app, set the platform type toWEB_COMPUTE
. For an app requiring Amplify Hosting's original SSR support only, set the platform type toWEB_DYNAMIC
.If you are deploying an SSG only app with Next.js version 14 or later, you must set the platform type to
WEB_COMPUTE
and set the artifactsbaseDirectory
to.next
in the application's build settings. For an example of the build specification settings, see Amplify build settings for a Next.js 14 SSG application in the Amplify Hosting User Guide .- repository string
- The Git repository for the Amplify app.
- Tag[]
- The tag for an Amplify app.
- access_
token str The personal access token for a GitHub repository for an Amplify app. The personal access token is used to authorize access to a GitHub repository using the Amplify GitHub App. The token is not stored.
Use
AccessToken
for GitHub repositories only. To authorize access to a repository provider such as Bitbucket or CodeCommit, useOauthToken
.You must specify either
AccessToken
orOauthToken
when you create a new app.Existing Amplify apps deployed from a GitHub repository using OAuth continue to work with CI/CD. However, we strongly recommend that you migrate these apps to use the GitHub App. For more information, see Migrating an existing OAuth app to the Amplify GitHub App in the Amplify User Guide .
- auto_
branch_ Appcreation_ config Auto Branch Creation Config Args - Sets the configuration for your automatic branch creation.
- basic_
auth_ Appconfig Basic Auth Config Args - The credentials for basic authorization for an Amplify app. You must base64-encode the authorization credentials and provide them in the format
user:password
. - build_
spec str - The build specification (build spec) for an Amplify app.
- cache_
config AppCache Config Args - The cache configuration for the Amplify app. If you don't specify the cache configuration
type
, Amplify uses the defaultAMPLIFY_MANAGED
setting. - custom_
headers str - The custom HTTP headers for an Amplify app.
- custom_
rules Sequence[AppCustom Rule Args] - The custom rewrite and redirect rules for an Amplify app.
- description str
- The description of the Amplify app.
- enable_
branch_ boolauto_ deletion - Automatically disconnect a branch in Amplify Hosting when you delete a branch from your Git repository.
- environment_
variables Sequence[AppEnvironment Variable Args] The environment variables for the Amplify app.
For a list of the environment variables that are accessible to Amplify by default, see Amplify Environment variables in the Amplify Hosting User Guide .
- iam_
service_ strrole - AWS Identity and Access Management ( IAM ) service role for the Amazon Resource Name (ARN) of the Amplify app.
- name str
- The name of the Amplify app.
- oauth_
token str The OAuth token for a third-party source control system for an Amplify app. The OAuth token is used to create a webhook and a read-only deploy key using SSH cloning. The OAuth token is not stored.
Use
OauthToken
for repository providers other than GitHub, such as Bitbucket or CodeCommit. To authorize access to GitHub as your repository provider, useAccessToken
.You must specify either
OauthToken
orAccessToken
when you create a new app.Existing Amplify apps deployed from a GitHub repository using OAuth continue to work with CI/CD. However, we strongly recommend that you migrate these apps to use the GitHub App. For more information, see Migrating an existing OAuth app to the Amplify GitHub App in the Amplify User Guide .
- platform
App
Platform The platform for the Amplify app. For a static app, set the platform type to
WEB
. For a dynamic server-side rendered (SSR) app, set the platform type toWEB_COMPUTE
. For an app requiring Amplify Hosting's original SSR support only, set the platform type toWEB_DYNAMIC
.If you are deploying an SSG only app with Next.js version 14 or later, you must set the platform type to
WEB_COMPUTE
and set the artifactsbaseDirectory
to.next
in the application's build settings. For an example of the build specification settings, see Amplify build settings for a Next.js 14 SSG application in the Amplify Hosting User Guide .- repository str
- The Git repository for the Amplify app.
- Sequence[Tag
Args] - The tag for an Amplify app.
- access
Token String The personal access token for a GitHub repository for an Amplify app. The personal access token is used to authorize access to a GitHub repository using the Amplify GitHub App. The token is not stored.
Use
AccessToken
for GitHub repositories only. To authorize access to a repository provider such as Bitbucket or CodeCommit, useOauthToken
.You must specify either
AccessToken
orOauthToken
when you create a new app.Existing Amplify apps deployed from a GitHub repository using OAuth continue to work with CI/CD. However, we strongly recommend that you migrate these apps to use the GitHub App. For more information, see Migrating an existing OAuth app to the Amplify GitHub App in the Amplify User Guide .
- auto
Branch Property MapCreation Config - Sets the configuration for your automatic branch creation.
- basic
Auth Property MapConfig - The credentials for basic authorization for an Amplify app. You must base64-encode the authorization credentials and provide them in the format
user:password
. - build
Spec String - The build specification (build spec) for an Amplify app.
- cache
Config Property Map - The cache configuration for the Amplify app. If you don't specify the cache configuration
type
, Amplify uses the defaultAMPLIFY_MANAGED
setting. - custom
Headers String - The custom HTTP headers for an Amplify app.
- custom
Rules List<Property Map> - The custom rewrite and redirect rules for an Amplify app.
- description String
- The description of the Amplify app.
- enable
Branch BooleanAuto Deletion - Automatically disconnect a branch in Amplify Hosting when you delete a branch from your Git repository.
- environment
Variables List<Property Map> The environment variables for the Amplify app.
For a list of the environment variables that are accessible to Amplify by default, see Amplify Environment variables in the Amplify Hosting User Guide .
- iam
Service StringRole - AWS Identity and Access Management ( IAM ) service role for the Amazon Resource Name (ARN) of the Amplify app.
- name String
- The name of the Amplify app.
- oauth
Token String The OAuth token for a third-party source control system for an Amplify app. The OAuth token is used to create a webhook and a read-only deploy key using SSH cloning. The OAuth token is not stored.
Use
OauthToken
for repository providers other than GitHub, such as Bitbucket or CodeCommit. To authorize access to GitHub as your repository provider, useAccessToken
.You must specify either
OauthToken
orAccessToken
when you create a new app.Existing Amplify apps deployed from a GitHub repository using OAuth continue to work with CI/CD. However, we strongly recommend that you migrate these apps to use the GitHub App. For more information, see Migrating an existing OAuth app to the Amplify GitHub App in the Amplify User Guide .
- platform "WEB" | "WEB_DYNAMIC" | "WEB_COMPUTE"
The platform for the Amplify app. For a static app, set the platform type to
WEB
. For a dynamic server-side rendered (SSR) app, set the platform type toWEB_COMPUTE
. For an app requiring Amplify Hosting's original SSR support only, set the platform type toWEB_DYNAMIC
.If you are deploying an SSG only app with Next.js version 14 or later, you must set the platform type to
WEB_COMPUTE
and set the artifactsbaseDirectory
to.next
in the application's build settings. For an example of the build specification settings, see Amplify build settings for a Next.js 14 SSG application in the Amplify Hosting User Guide .- repository String
- The Git repository for the Amplify app.
- List<Property Map>
- The tag for an Amplify app.
Outputs
All input properties are implicitly available as output properties. Additionally, the App resource produces the following output properties:
- App
Id string - Unique Id for the Amplify App.
- App
Name string - Name for the Amplify App.
- Arn string
- ARN for the Amplify App.
- Default
Domain string - Default domain for the Amplify App.
- Id string
- The provider-assigned unique ID for this managed resource.
- App
Id string - Unique Id for the Amplify App.
- App
Name string - Name for the Amplify App.
- Arn string
- ARN for the Amplify App.
- Default
Domain string - Default domain for the Amplify App.
- Id string
- The provider-assigned unique ID for this managed resource.
- app
Id String - Unique Id for the Amplify App.
- app
Name String - Name for the Amplify App.
- arn String
- ARN for the Amplify App.
- default
Domain String - Default domain for the Amplify App.
- id String
- The provider-assigned unique ID for this managed resource.
- app
Id string - Unique Id for the Amplify App.
- app
Name string - Name for the Amplify App.
- arn string
- ARN for the Amplify App.
- default
Domain string - Default domain for the Amplify App.
- id string
- The provider-assigned unique ID for this managed resource.
- app_
id str - Unique Id for the Amplify App.
- app_
name str - Name for the Amplify App.
- arn str
- ARN for the Amplify App.
- default_
domain str - Default domain for the Amplify App.
- id str
- The provider-assigned unique ID for this managed resource.
- app
Id String - Unique Id for the Amplify App.
- app
Name String - Name for the Amplify App.
- arn String
- ARN for the Amplify App.
- default
Domain String - Default domain for the Amplify App.
- id String
- The provider-assigned unique ID for this managed resource.
Supporting Types
AppAutoBranchCreationConfig, AppAutoBranchCreationConfigArgs
- Auto
Branch List<string>Creation Patterns - Automated branch creation glob patterns for the Amplify app.
- Basic
Auth Pulumi.Config Aws Native. Amplify. Inputs. App Basic Auth Config - Sets password protection for your auto created branch.
- Build
Spec string - The build specification (build spec) for the autocreated branch.
- Enable
Auto boolBranch Creation - Enables automated branch creation for the Amplify app.
- Enable
Auto boolBuild - Enables auto building for the auto created branch.
- Enable
Performance boolMode Enables performance mode for the branch.
Performance mode optimizes for faster hosting performance by keeping content cached at the edge for a longer interval. When performance mode is enabled, hosting configuration or code changes can take up to 10 minutes to roll out.
- Enable
Pull boolRequest Preview Sets whether pull request previews are enabled for each branch that Amplify Hosting automatically creates for your app. Amplify creates previews by deploying your app to a unique URL whenever a pull request is opened for the branch. Development and QA teams can use this preview to test the pull request before it's merged into a production or integration branch.
To provide backend support for your preview, Amplify Hosting automatically provisions a temporary backend environment that it deletes when the pull request is closed. If you want to specify a dedicated backend environment for your previews, use the
PullRequestEnvironmentName
property.For more information, see Web Previews in the AWS Amplify Hosting User Guide .
- Environment
Variables List<Pulumi.Aws Native. Amplify. Inputs. App Environment Variable> - The environment variables for the autocreated branch.
- Framework string
- The framework for the autocreated branch.
- Pull
Request stringEnvironment Name If pull request previews are enabled, you can use this property to specify a dedicated backend environment for your previews. For example, you could specify an environment named
prod
,test
, ordev
that you initialized with the Amplify CLI.To enable pull request previews, set the
EnablePullRequestPreview
property totrue
.If you don't specify an environment, Amplify Hosting provides backend support for each preview by automatically provisioning a temporary backend environment. Amplify deletes this environment when the pull request is closed.
For more information about creating backend environments, see Feature Branch Deployments and Team Workflows in the AWS Amplify Hosting User Guide .
- Stage
Pulumi.
Aws Native. Amplify. App Auto Branch Creation Config Stage - Stage for the auto created branch.
- Auto
Branch []stringCreation Patterns - Automated branch creation glob patterns for the Amplify app.
- Basic
Auth AppConfig Basic Auth Config - Sets password protection for your auto created branch.
- Build
Spec string - The build specification (build spec) for the autocreated branch.
- Enable
Auto boolBranch Creation - Enables automated branch creation for the Amplify app.
- Enable
Auto boolBuild - Enables auto building for the auto created branch.
- Enable
Performance boolMode Enables performance mode for the branch.
Performance mode optimizes for faster hosting performance by keeping content cached at the edge for a longer interval. When performance mode is enabled, hosting configuration or code changes can take up to 10 minutes to roll out.
- Enable
Pull boolRequest Preview Sets whether pull request previews are enabled for each branch that Amplify Hosting automatically creates for your app. Amplify creates previews by deploying your app to a unique URL whenever a pull request is opened for the branch. Development and QA teams can use this preview to test the pull request before it's merged into a production or integration branch.
To provide backend support for your preview, Amplify Hosting automatically provisions a temporary backend environment that it deletes when the pull request is closed. If you want to specify a dedicated backend environment for your previews, use the
PullRequestEnvironmentName
property.For more information, see Web Previews in the AWS Amplify Hosting User Guide .
- Environment
Variables []AppEnvironment Variable - The environment variables for the autocreated branch.
- Framework string
- The framework for the autocreated branch.
- Pull
Request stringEnvironment Name If pull request previews are enabled, you can use this property to specify a dedicated backend environment for your previews. For example, you could specify an environment named
prod
,test
, ordev
that you initialized with the Amplify CLI.To enable pull request previews, set the
EnablePullRequestPreview
property totrue
.If you don't specify an environment, Amplify Hosting provides backend support for each preview by automatically provisioning a temporary backend environment. Amplify deletes this environment when the pull request is closed.
For more information about creating backend environments, see Feature Branch Deployments and Team Workflows in the AWS Amplify Hosting User Guide .
- Stage
App
Auto Branch Creation Config Stage - Stage for the auto created branch.
- auto
Branch List<String>Creation Patterns - Automated branch creation glob patterns for the Amplify app.
- basic
Auth AppConfig Basic Auth Config - Sets password protection for your auto created branch.
- build
Spec String - The build specification (build spec) for the autocreated branch.
- enable
Auto BooleanBranch Creation - Enables automated branch creation for the Amplify app.
- enable
Auto BooleanBuild - Enables auto building for the auto created branch.
- enable
Performance BooleanMode Enables performance mode for the branch.
Performance mode optimizes for faster hosting performance by keeping content cached at the edge for a longer interval. When performance mode is enabled, hosting configuration or code changes can take up to 10 minutes to roll out.
- enable
Pull BooleanRequest Preview Sets whether pull request previews are enabled for each branch that Amplify Hosting automatically creates for your app. Amplify creates previews by deploying your app to a unique URL whenever a pull request is opened for the branch. Development and QA teams can use this preview to test the pull request before it's merged into a production or integration branch.
To provide backend support for your preview, Amplify Hosting automatically provisions a temporary backend environment that it deletes when the pull request is closed. If you want to specify a dedicated backend environment for your previews, use the
PullRequestEnvironmentName
property.For more information, see Web Previews in the AWS Amplify Hosting User Guide .
- environment
Variables List<AppEnvironment Variable> - The environment variables for the autocreated branch.
- framework String
- The framework for the autocreated branch.
- pull
Request StringEnvironment Name If pull request previews are enabled, you can use this property to specify a dedicated backend environment for your previews. For example, you could specify an environment named
prod
,test
, ordev
that you initialized with the Amplify CLI.To enable pull request previews, set the
EnablePullRequestPreview
property totrue
.If you don't specify an environment, Amplify Hosting provides backend support for each preview by automatically provisioning a temporary backend environment. Amplify deletes this environment when the pull request is closed.
For more information about creating backend environments, see Feature Branch Deployments and Team Workflows in the AWS Amplify Hosting User Guide .
- stage
App
Auto Branch Creation Config Stage - Stage for the auto created branch.
- auto
Branch string[]Creation Patterns - Automated branch creation glob patterns for the Amplify app.
- basic
Auth AppConfig Basic Auth Config - Sets password protection for your auto created branch.
- build
Spec string - The build specification (build spec) for the autocreated branch.
- enable
Auto booleanBranch Creation - Enables automated branch creation for the Amplify app.
- enable
Auto booleanBuild - Enables auto building for the auto created branch.
- enable
Performance booleanMode Enables performance mode for the branch.
Performance mode optimizes for faster hosting performance by keeping content cached at the edge for a longer interval. When performance mode is enabled, hosting configuration or code changes can take up to 10 minutes to roll out.
- enable
Pull booleanRequest Preview Sets whether pull request previews are enabled for each branch that Amplify Hosting automatically creates for your app. Amplify creates previews by deploying your app to a unique URL whenever a pull request is opened for the branch. Development and QA teams can use this preview to test the pull request before it's merged into a production or integration branch.
To provide backend support for your preview, Amplify Hosting automatically provisions a temporary backend environment that it deletes when the pull request is closed. If you want to specify a dedicated backend environment for your previews, use the
PullRequestEnvironmentName
property.For more information, see Web Previews in the AWS Amplify Hosting User Guide .
- environment
Variables AppEnvironment Variable[] - The environment variables for the autocreated branch.
- framework string
- The framework for the autocreated branch.
- pull
Request stringEnvironment Name If pull request previews are enabled, you can use this property to specify a dedicated backend environment for your previews. For example, you could specify an environment named
prod
,test
, ordev
that you initialized with the Amplify CLI.To enable pull request previews, set the
EnablePullRequestPreview
property totrue
.If you don't specify an environment, Amplify Hosting provides backend support for each preview by automatically provisioning a temporary backend environment. Amplify deletes this environment when the pull request is closed.
For more information about creating backend environments, see Feature Branch Deployments and Team Workflows in the AWS Amplify Hosting User Guide .
- stage
App
Auto Branch Creation Config Stage - Stage for the auto created branch.
- auto_
branch_ Sequence[str]creation_ patterns - Automated branch creation glob patterns for the Amplify app.
- basic_
auth_ Appconfig Basic Auth Config - Sets password protection for your auto created branch.
- build_
spec str - The build specification (build spec) for the autocreated branch.
- enable_
auto_ boolbranch_ creation - Enables automated branch creation for the Amplify app.
- enable_
auto_ boolbuild - Enables auto building for the auto created branch.
- enable_
performance_ boolmode Enables performance mode for the branch.
Performance mode optimizes for faster hosting performance by keeping content cached at the edge for a longer interval. When performance mode is enabled, hosting configuration or code changes can take up to 10 minutes to roll out.
- enable_
pull_ boolrequest_ preview Sets whether pull request previews are enabled for each branch that Amplify Hosting automatically creates for your app. Amplify creates previews by deploying your app to a unique URL whenever a pull request is opened for the branch. Development and QA teams can use this preview to test the pull request before it's merged into a production or integration branch.
To provide backend support for your preview, Amplify Hosting automatically provisions a temporary backend environment that it deletes when the pull request is closed. If you want to specify a dedicated backend environment for your previews, use the
PullRequestEnvironmentName
property.For more information, see Web Previews in the AWS Amplify Hosting User Guide .
- environment_
variables Sequence[AppEnvironment Variable] - The environment variables for the autocreated branch.
- framework str
- The framework for the autocreated branch.
- pull_
request_ strenvironment_ name If pull request previews are enabled, you can use this property to specify a dedicated backend environment for your previews. For example, you could specify an environment named
prod
,test
, ordev
that you initialized with the Amplify CLI.To enable pull request previews, set the
EnablePullRequestPreview
property totrue
.If you don't specify an environment, Amplify Hosting provides backend support for each preview by automatically provisioning a temporary backend environment. Amplify deletes this environment when the pull request is closed.
For more information about creating backend environments, see Feature Branch Deployments and Team Workflows in the AWS Amplify Hosting User Guide .
- stage
App
Auto Branch Creation Config Stage - Stage for the auto created branch.
- auto
Branch List<String>Creation Patterns - Automated branch creation glob patterns for the Amplify app.
- basic
Auth Property MapConfig - Sets password protection for your auto created branch.
- build
Spec String - The build specification (build spec) for the autocreated branch.
- enable
Auto BooleanBranch Creation - Enables automated branch creation for the Amplify app.
- enable
Auto BooleanBuild - Enables auto building for the auto created branch.
- enable
Performance BooleanMode Enables performance mode for the branch.
Performance mode optimizes for faster hosting performance by keeping content cached at the edge for a longer interval. When performance mode is enabled, hosting configuration or code changes can take up to 10 minutes to roll out.
- enable
Pull BooleanRequest Preview Sets whether pull request previews are enabled for each branch that Amplify Hosting automatically creates for your app. Amplify creates previews by deploying your app to a unique URL whenever a pull request is opened for the branch. Development and QA teams can use this preview to test the pull request before it's merged into a production or integration branch.
To provide backend support for your preview, Amplify Hosting automatically provisions a temporary backend environment that it deletes when the pull request is closed. If you want to specify a dedicated backend environment for your previews, use the
PullRequestEnvironmentName
property.For more information, see Web Previews in the AWS Amplify Hosting User Guide .
- environment
Variables List<Property Map> - The environment variables for the autocreated branch.
- framework String
- The framework for the autocreated branch.
- pull
Request StringEnvironment Name If pull request previews are enabled, you can use this property to specify a dedicated backend environment for your previews. For example, you could specify an environment named
prod
,test
, ordev
that you initialized with the Amplify CLI.To enable pull request previews, set the
EnablePullRequestPreview
property totrue
.If you don't specify an environment, Amplify Hosting provides backend support for each preview by automatically provisioning a temporary backend environment. Amplify deletes this environment when the pull request is closed.
For more information about creating backend environments, see Feature Branch Deployments and Team Workflows in the AWS Amplify Hosting User Guide .
- stage "EXPERIMENTAL" | "BETA" | "PULL_REQUEST" | "PRODUCTION" | "DEVELOPMENT"
- Stage for the auto created branch.
AppAutoBranchCreationConfigStage, AppAutoBranchCreationConfigStageArgs
- Experimental
- EXPERIMENTAL
- Beta
- BETA
- Pull
Request - PULL_REQUEST
- Production
- PRODUCTION
- Development
- DEVELOPMENT
- App
Auto Branch Creation Config Stage Experimental - EXPERIMENTAL
- App
Auto Branch Creation Config Stage Beta - BETA
- App
Auto Branch Creation Config Stage Pull Request - PULL_REQUEST
- App
Auto Branch Creation Config Stage Production - PRODUCTION
- App
Auto Branch Creation Config Stage Development - DEVELOPMENT
- Experimental
- EXPERIMENTAL
- Beta
- BETA
- Pull
Request - PULL_REQUEST
- Production
- PRODUCTION
- Development
- DEVELOPMENT
- Experimental
- EXPERIMENTAL
- Beta
- BETA
- Pull
Request - PULL_REQUEST
- Production
- PRODUCTION
- Development
- DEVELOPMENT
- EXPERIMENTAL
- EXPERIMENTAL
- BETA
- BETA
- PULL_REQUEST
- PULL_REQUEST
- PRODUCTION
- PRODUCTION
- DEVELOPMENT
- DEVELOPMENT
- "EXPERIMENTAL"
- EXPERIMENTAL
- "BETA"
- BETA
- "PULL_REQUEST"
- PULL_REQUEST
- "PRODUCTION"
- PRODUCTION
- "DEVELOPMENT"
- DEVELOPMENT
AppBasicAuthConfig, AppBasicAuthConfigArgs
- Enable
Basic boolAuth - Enables basic authorization for the Amplify app's branches.
- Password string
- The password for basic authorization.
- Username string
- The user name for basic authorization.
- Enable
Basic boolAuth - Enables basic authorization for the Amplify app's branches.
- Password string
- The password for basic authorization.
- Username string
- The user name for basic authorization.
- enable
Basic BooleanAuth - Enables basic authorization for the Amplify app's branches.
- password String
- The password for basic authorization.
- username String
- The user name for basic authorization.
- enable
Basic booleanAuth - Enables basic authorization for the Amplify app's branches.
- password string
- The password for basic authorization.
- username string
- The user name for basic authorization.
- enable_
basic_ boolauth - Enables basic authorization for the Amplify app's branches.
- password str
- The password for basic authorization.
- username str
- The user name for basic authorization.
- enable
Basic BooleanAuth - Enables basic authorization for the Amplify app's branches.
- password String
- The password for basic authorization.
- username String
- The user name for basic authorization.
AppCacheConfig, AppCacheConfigArgs
- Type
Pulumi.
Aws Native. Amplify. App Cache Config Type The type of cache configuration to use for an Amplify app.
The
AMPLIFY_MANAGED
cache configuration automatically applies an optimized cache configuration for your app based on its platform, routing rules, and rewrite rules. This is the default setting.The
AMPLIFY_MANAGED_NO_COOKIES
cache configuration type is the same asAMPLIFY_MANAGED
, except that it excludes all cookies from the cache key.
- Type
App
Cache Config Type The type of cache configuration to use for an Amplify app.
The
AMPLIFY_MANAGED
cache configuration automatically applies an optimized cache configuration for your app based on its platform, routing rules, and rewrite rules. This is the default setting.The
AMPLIFY_MANAGED_NO_COOKIES
cache configuration type is the same asAMPLIFY_MANAGED
, except that it excludes all cookies from the cache key.
- type
App
Cache Config Type The type of cache configuration to use for an Amplify app.
The
AMPLIFY_MANAGED
cache configuration automatically applies an optimized cache configuration for your app based on its platform, routing rules, and rewrite rules. This is the default setting.The
AMPLIFY_MANAGED_NO_COOKIES
cache configuration type is the same asAMPLIFY_MANAGED
, except that it excludes all cookies from the cache key.
- type
App
Cache Config Type The type of cache configuration to use for an Amplify app.
The
AMPLIFY_MANAGED
cache configuration automatically applies an optimized cache configuration for your app based on its platform, routing rules, and rewrite rules. This is the default setting.The
AMPLIFY_MANAGED_NO_COOKIES
cache configuration type is the same asAMPLIFY_MANAGED
, except that it excludes all cookies from the cache key.
- type
App
Cache Config Type The type of cache configuration to use for an Amplify app.
The
AMPLIFY_MANAGED
cache configuration automatically applies an optimized cache configuration for your app based on its platform, routing rules, and rewrite rules. This is the default setting.The
AMPLIFY_MANAGED_NO_COOKIES
cache configuration type is the same asAMPLIFY_MANAGED
, except that it excludes all cookies from the cache key.
- type "AMPLIFY_MANAGED" | "AMPLIFY_MANAGED_NO_COOKIES"
The type of cache configuration to use for an Amplify app.
The
AMPLIFY_MANAGED
cache configuration automatically applies an optimized cache configuration for your app based on its platform, routing rules, and rewrite rules. This is the default setting.The
AMPLIFY_MANAGED_NO_COOKIES
cache configuration type is the same asAMPLIFY_MANAGED
, except that it excludes all cookies from the cache key.
AppCacheConfigType, AppCacheConfigTypeArgs
- Amplify
Managed - AMPLIFY_MANAGED
- Amplify
Managed No Cookies - AMPLIFY_MANAGED_NO_COOKIES
- App
Cache Config Type Amplify Managed - AMPLIFY_MANAGED
- App
Cache Config Type Amplify Managed No Cookies - AMPLIFY_MANAGED_NO_COOKIES
- Amplify
Managed - AMPLIFY_MANAGED
- Amplify
Managed No Cookies - AMPLIFY_MANAGED_NO_COOKIES
- Amplify
Managed - AMPLIFY_MANAGED
- Amplify
Managed No Cookies - AMPLIFY_MANAGED_NO_COOKIES
- AMPLIFY_MANAGED
- AMPLIFY_MANAGED
- AMPLIFY_MANAGED_NO_COOKIES
- AMPLIFY_MANAGED_NO_COOKIES
- "AMPLIFY_MANAGED"
- AMPLIFY_MANAGED
- "AMPLIFY_MANAGED_NO_COOKIES"
- AMPLIFY_MANAGED_NO_COOKIES
AppCustomRule, AppCustomRuleArgs
- Source string
- The source pattern for a URL rewrite or redirect rule.
- Target string
- The target pattern for a URL rewrite or redirect rule.
- Condition string
- The condition for a URL rewrite or redirect rule, such as a country code.
- Status string
- The status code for a URL rewrite or redirect rule.
- 200 - Represents a 200 rewrite rule.
- 301 - Represents a 301 (moved pemanently) redirect rule. This and all future requests should be directed to the target URL.
- 302 - Represents a 302 temporary redirect rule.
- 404 - Represents a 404 redirect rule.
- 404-200 - Represents a 404 rewrite rule.
- Source string
- The source pattern for a URL rewrite or redirect rule.
- Target string
- The target pattern for a URL rewrite or redirect rule.
- Condition string
- The condition for a URL rewrite or redirect rule, such as a country code.
- Status string
- The status code for a URL rewrite or redirect rule.
- 200 - Represents a 200 rewrite rule.
- 301 - Represents a 301 (moved pemanently) redirect rule. This and all future requests should be directed to the target URL.
- 302 - Represents a 302 temporary redirect rule.
- 404 - Represents a 404 redirect rule.
- 404-200 - Represents a 404 rewrite rule.
- source String
- The source pattern for a URL rewrite or redirect rule.
- target String
- The target pattern for a URL rewrite or redirect rule.
- condition String
- The condition for a URL rewrite or redirect rule, such as a country code.
- status String
- The status code for a URL rewrite or redirect rule.
- 200 - Represents a 200 rewrite rule.
- 301 - Represents a 301 (moved pemanently) redirect rule. This and all future requests should be directed to the target URL.
- 302 - Represents a 302 temporary redirect rule.
- 404 - Represents a 404 redirect rule.
- 404-200 - Represents a 404 rewrite rule.
- source string
- The source pattern for a URL rewrite or redirect rule.
- target string
- The target pattern for a URL rewrite or redirect rule.
- condition string
- The condition for a URL rewrite or redirect rule, such as a country code.
- status string
- The status code for a URL rewrite or redirect rule.
- 200 - Represents a 200 rewrite rule.
- 301 - Represents a 301 (moved pemanently) redirect rule. This and all future requests should be directed to the target URL.
- 302 - Represents a 302 temporary redirect rule.
- 404 - Represents a 404 redirect rule.
- 404-200 - Represents a 404 rewrite rule.
- source str
- The source pattern for a URL rewrite or redirect rule.
- target str
- The target pattern for a URL rewrite or redirect rule.
- condition str
- The condition for a URL rewrite or redirect rule, such as a country code.
- status str
- The status code for a URL rewrite or redirect rule.
- 200 - Represents a 200 rewrite rule.
- 301 - Represents a 301 (moved pemanently) redirect rule. This and all future requests should be directed to the target URL.
- 302 - Represents a 302 temporary redirect rule.
- 404 - Represents a 404 redirect rule.
- 404-200 - Represents a 404 rewrite rule.
- source String
- The source pattern for a URL rewrite or redirect rule.
- target String
- The target pattern for a URL rewrite or redirect rule.
- condition String
- The condition for a URL rewrite or redirect rule, such as a country code.
- status String
- The status code for a URL rewrite or redirect rule.
- 200 - Represents a 200 rewrite rule.
- 301 - Represents a 301 (moved pemanently) redirect rule. This and all future requests should be directed to the target URL.
- 302 - Represents a 302 temporary redirect rule.
- 404 - Represents a 404 redirect rule.
- 404-200 - Represents a 404 rewrite rule.
AppEnvironmentVariable, AppEnvironmentVariableArgs
AppPlatform, AppPlatformArgs
- Web
- WEB
- Web
Dynamic - WEB_DYNAMIC
- Web
Compute - WEB_COMPUTE
- App
Platform Web - WEB
- App
Platform Web Dynamic - WEB_DYNAMIC
- App
Platform Web Compute - WEB_COMPUTE
- Web
- WEB
- Web
Dynamic - WEB_DYNAMIC
- Web
Compute - WEB_COMPUTE
- Web
- WEB
- Web
Dynamic - WEB_DYNAMIC
- Web
Compute - WEB_COMPUTE
- WEB
- WEB
- WEB_DYNAMIC
- WEB_DYNAMIC
- WEB_COMPUTE
- WEB_COMPUTE
- "WEB"
- WEB
- "WEB_DYNAMIC"
- WEB_DYNAMIC
- "WEB_COMPUTE"
- WEB_COMPUTE
Tag, TagArgs
Package Details
- Repository
- AWS Native pulumi/pulumi-aws-native
- License
- Apache-2.0
We recommend new projects start with resources from the AWS provider.