Examples of using Opsworks stack in English and their translations into German
{-}
-
Colloquial
-
Official
-
Ecclesiastic
-
Medicine
-
Financial
-
Ecclesiastic
-
Political
-
Computer
-
Programming
-
Official/political
-
Political
Step 2: Create an AWS OpsWorks Stack.
The ID of the AWS OpsWorks stack that this layer will be associated with.
Defines an AWS OpsWorks app for an AWS OpsWorks stack.
For the AWS OpsWorks stack myApp, Ref returns the ID of the AWS OpsWorks app.
The ID of the Amazon EBS volume to register with the AWS OpsWorks stack.
Creates an AWS OpsWorks stack with a load-balanced application that runs inside a VPC.
A list of Elastic IP addresses to register with the AWS OpsWorks stack.
You create the AWS OpsWorks stack and layer you want to use before you create the pipeline.
For valid values, see CreateInstance in the AWS OpsWorks Stacks API Reference.
If you're cloning an AWS OpsWorks stack, indicates whether to clone the source stack's permissions.
For valid values, see VolumeConfiguration in the AWS OpsWorks Stacks API Reference.
Creates an AWS OpsWorks stack, layer, instances and associated resources to run a PHP application.
For more information and valid values, see Source in the AWS OpsWorks Stacks API Reference.
Instances for AWS OpsWorks stacks handle the work of serving applications and balancing traffic, for example.
You can also use the AWSOpsWorks built-in security groups with your AWS OpsWorks stacks.
If a user requires access only to AWS OpsWorks Stacks, you might not need to attach a policy at all.
For valid values,see the AgentVersion parameter for the CreateStack action in the AWS OpsWorks Stacks API Reference.
If you're cloning an AWS OpsWorks stack, the stack ID of the source AWS OpsWorks stack to clone.
For valid values,see the AgentVersion parameter for the CreateInstance action in the AWS OpsWorks Stacks API Reference.
For AWS OpsWorks stacks that are running in a VPC, whether to automatically assign a public IP address to Amazon EC2 instances in this layer.
In the navigation pane, choose Roles, and then in the contents pane, for Role Name,select the name of the instance role used by your AWS OpsWorks stack.
An AWS OpsWorks stack represents a set of instances that you want to manage collectively, typically because they have a common purpose such as serving PHP applications.
The following snippet creates a load-based automatic scaling AWS OpsWorks PHPlayer that is associated with the myStack AWS OpsWorks stack.
If you specify a cluster that's registered with another AWS OpsWorks stack, AWS CloudFormation deregisters the existing association before registering the cluster.
These credentials provide the permissions required to access AWS resources, such as putting and retrieving artifacts from Amazon S3 buckets andintegrating AWS OpsWorks stacks into your pipelines.
If you specify a DB instance that's registered with another AWS OpsWorks stack, AWS CloudFormation deregisters the existing association before registering the DB instance.
The following snippet creates an AWS OpsWorks stack that uses the default service role and Amazon EC2 role, which are created after you use AWS OpsWorks for the first time.
You can configure AWS CodePipeline to use AWS OpsWorks Stacks to deploy your code in conjunction with custom Chef cookbooks and applications in AWS OpsWorks. .