Simple credentials which can be used to configure the static credentials. This credentials
can be either hard-coded in the XML (not recommended), evaluated through an EL expression or
replaced by a property place holder variable.
This credentials will be fetched through the particular instance profile. So there is no
need to define any additional information. NOTE: In order to use the instance profile
credentials, the application context must run inside an EC2 instance.
Profile based credentials provider that allows to configure the profiles inside an
AWS SDK specific configuration file using different profile names.
Configures the profile name used by the profile credentials provider. The profile
name is specified according to the profile file format.
Allows to configure the profile path. By default the profile file will be read
inside
the users directory in the folder .aws/credentials .
Configures a resource loader that supports amazon S3 resources to be loaded by the application context
resource loader.
Defines that the region should be auto detected through the EC2 meta data
Instance id provider, by default the instance id is taken from the instance
meta-data. Might be changed with another strategy
Reference to a custom Amazon EC2 client bean if user tags should be retrieved
from EC2 meta-data. This attribute is ignored if there is no user-tags-map attribute configured
Value separator used to separate the values inside the user data (same default
like property place holders default)
Attribute separator used to separate the attributes inside the global user data
string
Attribute group that can be used by components which are region aware. This group
allows users to configure the particular region.
The region that will be used, must be one of the valid regions.
Exposed map that contains all user tags to be accessed via EL expression
The access key used to make the request. An access key is assigned to one account or IAM user.
The secret key which is assigned for the particular access key.
Configures an Amazon Cloud Formation stack and enables lookup of physical ids by logical ids for
resources defined in the specified stack.
The name of the stack to be configured. The corresponding stack must exist and must be
available. If no stack name is configured, the stack name is automatically detected
based on the stack the current Amazon EC2 instance is part of.
A reference to an externally configured AmazonCloudFormation client, to be used to retrieve
stack information from the CloudFormation service.