-
Notifications
You must be signed in to change notification settings - Fork 17
/
CfnService_SecretProperty.go
35 lines (32 loc) · 2.07 KB
/
CfnService_SecretProperty.go
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
package awsecs
// An object representing the secret to expose to your container.
//
// Secrets can be exposed to a container in the following ways:
//
// - To inject sensitive data into your containers as environment variables, use the `secrets` container definition parameter.
// - To reference sensitive information in the log configuration of a container, use the `secretOptions` container definition parameter.
//
// For more information, see [Specifying sensitive data](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/specifying-sensitive-data.html) in the *Amazon Elastic Container Service Developer Guide* .
//
// Example:
// // The code below shows an example of how to instantiate this type.
// // The values are placeholders you should change.
// import "github.com/aws/aws-cdk-go/awscdk"
//
// secretProperty := &SecretProperty{
// Name: jsii.String("name"),
// ValueFrom: jsii.String("valueFrom"),
// }
//
type CfnService_SecretProperty struct {
// The name of the secret.
Name *string `field:"required" json:"name" yaml:"name"`
// The secret to expose to the container.
//
// The supported values are either the full ARN of the AWS Secrets Manager secret or the full ARN of the parameter in the SSM Parameter Store.
//
// For information about the require AWS Identity and Access Management permissions, see [Required IAM permissions for Amazon ECS secrets](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/specifying-sensitive-data-secrets.html#secrets-iam) (for Secrets Manager) or [Required IAM permissions for Amazon ECS secrets](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/specifying-sensitive-data-parameters.html) (for Systems Manager Parameter store) in the *Amazon Elastic Container Service Developer Guide* .
//
// > If the SSM Parameter Store parameter exists in the same Region as the task you're launching, then you can use either the full ARN or name of the parameter. If the parameter exists in a different Region, then the full ARN must be specified.
ValueFrom *string `field:"required" json:"valueFrom" yaml:"valueFrom"`
}