This cookbook provides resources for configuring and managing nodes running in Amazon Web Services as well as several AWS service offerings. Included resources:
- CloudFormation Stack Management (
cloudformation_stack
) - CloudWatch (
cloudwatch
) - CloudWatch Instance Monitoring (
instance_monitoring
) - DynamoDB (
dynamodb_table
) - EBS Volumes (
ebs_volume
) - EC2 Instance Termination Protection (
instance_term_protection
) - Elastic IPs (
elastic_ip
) - Elastic Load Balancer (
elastic_lb
) - IAM User, Group, Policy, and Role Management: (
iam_user
,iam_group
,iam_policy
,iam_role
) - Kinesis Stream Management (
kinesis_stream
) - Resource Tags (
resource_tag
) - Route53 DNS Records (
route53_record
) - Route53 DNS Zones (
route53_zone
) - S3 Files (
s3_file
) - S3 Buckets (
s3_bucket
) - Secondary IPs (
secondary_ip
)
Unsupported AWS resources that have other cookbooks include but are not limited to:
- Any platform supported by Chef and the AWS-SDK
- Chef 12.9+
- None
In order to manage AWS components, authentication credentials need to be available to the node. There are 3 ways to handle this:
- Explicitly set the credentials when using the resources
- Use the credentials in the
~/.aws/credentials
file - Let the resource pick up credentials from the IAM role assigned to the instance
Also new resources can now assume an STS role, with support for MFA as well. Instructions are below in the relevant section.
In order to pass the credentials to the resource, credentials must be available to the node. There are a number of ways to handle this, such as node attributes applied to the node or via Chef roles/environments.
We recommend storing these in an encrypted databag, and loading them in the recipe where the resources are used.
Example Data Bag:
% knife data bag show aws main
{
"id": "main",
"aws_access_key_id": "YOUR_ACCESS_KEY",
"aws_secret_access_key": "YOUR_SECRET_ACCESS_KEY",
"aws_session_token": "YOUR_SESSION_TOKEN"
}
This can be loaded in a recipe with:
aws = data_bag_item('aws', 'main')
And to access the values:
aws['aws_access_key_id']
aws['aws_secret_access_key']
aws['aws_session_token']
We'll look at specific usage below.
If credentials are not supplied via parameters, resources will look for the credentials in the ~/.aws/credentials
file:
[default]
aws_access_key_id = ACCESS_KEY_ID
aws_secret_access_key = ACCESS_KEY
Note that this also accepts other profiles if they are supplied via the ENV['AWS_PROFILE']
environment variable.
If your instance has an IAM role, then the credentials can be automatically resolved by the cookbook using Amazon instance metadata API.
You can then omit the authentication properties aws_secret_access_key
and aws_access_key
when using the resource.
Of course, the instance role must have the required policies. Here is a sample policy for EBS volume management:
{
"Version": "2012-10-17",
"Statement": [
{
"Action": [
"ec2:AttachVolume",
"ec2:CreateVolume",
"ec2:ModifyInstanceAttribute",
"ec2:ModifyVolumeAttribute",
"ec2:DescribeVolumeAttribute",
"ec2:DescribeVolumeStatus",
"ec2:DescribeVolumes",
"ec2:DetachVolume",
"ec2:EnableVolumeIO"
],
"Sid": "Stmt1381536011000",
"Resource": [
"*"
],
"Effect": "Allow"
}
]
}
For resource tags:
{
"Version": "2012-10-17",
"Statement": [
{
"Action": [
"ec2:CreateTags",
"ec2:DescribeTags"
],
"Sid": "Stmt1381536708000",
"Resource": [
"*"
],
"Effect": "Allow"
}
]
}
The following is an example of how roles can be assumed using MFA. The following can also be used to assumes roles that do not require MFA, just ensure that the MFA arguments (serial_number
and token_code
) are omitted.
This assumes you have also stored the cfn_role_arn
, and mfa_serial
attributes as well, but there are plenty of ways these attributes can be supplied (they could be stored locally in the consuming cookbook, for example).
Note that MFA codes cannot be recycled, hence the importance of creating a single STS session and passing that to resources. If multiple roles need to be assumed using MFA, it is probably prudent that these be broken up into different recipes and chef-client
runs.
require 'aws-sdk'
require 'securerandom'
session_id = SecureRandom.hex(8)
sts = ::Aws::AssumeRoleCredentials.new(
client: ::Aws::STS::Client.new(
credentials: ::Aws::Credentials.new(
node['aws']['aws_access_key_id'],
node['aws']['aws_secret_access_key']
),
region: 'us-east-1'
),
role_arn: node['aws']['cfn_role_arn'],
role_session_name: session_id,
serial_number: node['aws']['mfa_serial'],
token_code: node['aws']['mfa_code']
)
aws_cloudformation_stack 'kitchen-test-stack' do
action :create
template_source 'kitchen-test-stack.tpl'
aws_access_key sts.access_key_id
aws_secret_access_key sts.secret_access_key
aws_session_token sts.session_token
end
When running the cookbook, ensure that an attribute JSON is passed that supplies the MFA code. Example using chef-zero:
echo '{ "aws": { "mfa_code": "123456" } }' > mfa.json && chef-client -z -o 'recipe[aws_test]' -j mfa.json
region
can be specified on each resource if the cookbook is being run outside of an AWS instance. This can prevent some kinds of failures that happen when resources try to detect region.
aws_cloudformation_stack 'kitchen-test-stack' do
action :create
template_source 'kitchen-test-stack.tpl'
region 'us-east-1'
end
Manage CloudFormation stacks.
create
: Creates the stack, or updates it if it already exists.delete
: Begins the deletion process for the stack.
template_source
: Required - the location of the CloudFormation template file. The file should be stored in thefiles
directory in the cookbook.parameters
: An array ofparameter_key
andparameter_value
pairs for parameters in the template. Follow the syntax in the example above.disable_rollback
: Set this totrue
if you want stack rollback to be disabled if creation of the stack fails. Default:false
stack_policy_body
: Optionally define a stack policy to apply to the stack, mainly used in protecting stack resources after they are created. For more information, see Prevent Updates to Stack Resources in the CloudFormation user guide.iam_capability
: Set totrue
to allow the CloudFormation template to create IAM resources. This is the equivalent of settingCAPABILITY_IAM
When using the SDK or CLI. Default:false
named_iam_capability
: Set totrue
to allow the CloudFormation template to create IAM resources with custom names. This is the equivalent of settingCAPABILITY_NAMED_IAM
When using the SDK or CLI. Default:false
aws_cloudformation_stack 'example-stack' do
region 'us-east-1'
template_source 'example-stack.tpl'
parameters ([
{
:parameter_key => 'KeyPair',
:parameter_value => 'user@host'
},
{
:parameter_key => 'SSHAllowIPAddress',
:parameter_value => '127.0.0.1/32'
}
])
end
Use this resource to manage CloudWatch alarms.
create
- Create or update CloudWatch alarms.delete
- Delete CloudWatch alarms.disable_action
- Disable action of the CloudWatch alarms.enable_action
- Enable action of the CloudWatch alarms.
aws_secret_access_key
,aws_access_key
and optionallyaws_session_token
- required, unless using IAM roles for authentication.alarm_name
- the alarm name. If none is given on assignment, will take the resource name.alarm_description
- the description of alarm. Can be blank also.actions_enabled
- true for enable action on OK, ALARM or Insufficient data. if true, any of ok_actions, alarm_actions or insufficient_data_actions must be specified.ok_actions
- array of action if alarm state is OK. If specified actions_enabled must be true.alarm_actions
- array of action if alarm state is ALARM. If specified actions_enabled must be true.insufficient_data_actions
- array of action if alarm state is INSUFFICIENT_DATA. If specified actions_enabled must be true.metric_name
- CloudWatch metric name of the alarm. eg - CPUUtilization.Required parameter.namespace
- namespace of the alarm. eg - AWS/EC2, required parameter.statistic
- statistic of the alarm. Value must be in any of SampleCount, Average, Sum, Minimum or Maximum. Required parameter.extended_statistic
- extended_statistic of the alarm. Specify a value between p0.0 and p100. Optional parameter.dimensions
- dimensions for the metric associated with the alarm. Array of name and value.period
- in seconds, over which the specified statistic is applied. Integer type and required parameter.unit
- unit of measure for the statistic. Required parameter.evaluation_periods
- number of periods over which data is compared to the specified threshold. Required parameter.threshold
- value against which the specified statistic is compared. Can be float or integer type. Required parameter.comparison_operator
- arithmetic operation to use when comparing the specified statistic and threshold. The specified statistic value is used as the first operand.
For more information about parameters, see CloudWatch Identifiers in the Using CloudWatch guide.
aws_cloudwatch "kitchen_test_alarm" do
period 21600
evaluation_periods 2
threshold 50.0
comparison_operator "LessThanThreshold"
metric_name "CPUUtilization"
namespace "AWS/EC2"
statistic "Maximum"
dimensions [{"name" : "InstanceId", "value" : "i-xxxxxxx"}]
action :create
end
Use this resource to create and delete DynamoDB tables. This includes the ability to add global secondary indexes to existing tables.
create
: Creates the table. Will update the following if the table exists:global_secondary_indexes
: Will remove non-existent indexes, add new ones, and update throughput for existing ones. All attributes need to be present inattribute_definitions
. No effect if the resource is omitted.stream_specification
: Will update as shown. No effect is the resource is omitted.provisioned_throughput
: Will update as shown.delete
: Deletes the index.
attribute_definitions
: Required. Attributes to create for the table. Mainly this is used to specify attributes that are used in keys, as otherwise one can add any attribute they want to a DynamoDB table.key_schema
: Required. Used to create the primary key for the table. Attributes need to be present inattribute_definitions
.local_secondary_indexes
: Used to create any local secondary indexes for the table. Attributes need to be present inattribute_definitions
.global_secondary_indexes
: Used to create any global secondary indexes. Can be done to an existing table. Attributes need to be present inattribute_definitions
.provisioned_throughput
: Define the throughput for this table.stream_specification
: Specify if there should be a stream for this table.
Several of the attributes shown here take parameters as shown in the AWS Ruby SDK Documentation. Also, the AWS DynamoDB Documentation may be of further help as well.
aws_dynamodb_table 'example-table' do
action :create
attribute_definitions [
{ attribute_name: 'Id', attribute_type: 'N' },
{ attribute_name: 'Foo', attribute_type: 'N' },
{ attribute_name: 'Bar', attribute_type: 'N' },
{ attribute_name: 'Baz', attribute_type: 'S' }
]
key_schema [
{ attribute_name: 'Id', key_type: 'HASH' },
{ attribute_name: 'Foo', key_type: 'RANGE' }
]
local_secondary_indexes [
{
index_name: 'BarIndex',
key_schema: [
{
attribute_name: 'Id',
key_type: 'HASH'
},
{
attribute_name: 'Bar',
key_type: 'RANGE'
}
],
projection: {
projection_type: 'ALL'
}
}
]
global_secondary_indexes [
{
index_name: 'BazIndex',
key_schema: [{
attribute_name: 'Baz',
key_type: 'HASH'
}],
projection: {
projection_type: 'ALL'
},
provisioned_throughput: {
read_capacity_units: 1,
write_capacity_units: 1
}
}
]
provisioned_throughput ({
read_capacity_units: 1,
write_capacity_units: 1
})
stream_specification ({
stream_enabled: true,
stream_view_type: 'KEYS_ONLY'
})
end
The resource only handles manipulating the EBS volume, additional resources need to be created in the recipe to manage the attached volume as a filesystem or logical volume.
create
- create a new volume.attach
- attach the specified volume.detach
- detach the specified volume.delete
- delete the specified volume.snapshot
- create a snapshot of the volume.prune
- prune snapshots.
aws_secret_access_key
,aws_access_key
and optionallyaws_session_token
- required, unless using IAM roles for authentication.size
- size of the volume in gigabytes.snapshot_id
- snapshot to build EBS volume from.most_recent_snapshot
- use the most recent snapshot when creating a volume from an existing volume (defaults to false)availability_zone
- EC2 region, and is normally automatically detected.device
- local block device to attach the volume to, e.g./dev/sdi
but no default value, required.volume_id
- specify an ID to attach, cannot be used with action:create
because AWS assigns new volume IDstimeout
- connection timeout for EC2 API.snapshots_to_keep
- used with action:prune
for number of snapshots to maintain.description
- used to set the description of an EBS snapshotvolume_type
- "standard", "io1", or "gp2" ("standard" is magnetic, "io1" is provisioned SSD, "gp2" is general purpose SSD)piops
- number of Provisioned IOPS to provision, must be >= 100existing_raid
- whether or not to assume the raid was previously assembled on existing volumes (default no)encrypted
- specify if the EBS should be encryptedkms_key_id
- the full ARN of the AWS Key Management Service (AWS KMS) master key to use when creating the encrypted volume (defaults to master key if not specified)delete_on_termination
- Boolean value to control whether or not the volume should be deleted when the instance it's attached to is terminated (defaults to nil). Only applies to:attach
action.
Create a 50G volume, attach it to the instance as /dev/sdi
:
aws_ebs_volume 'db_ebs_volume' do
size 50
device '/dev/sdi'
action [:create, :attach]
end
Create a new 50G volume from the snapshot ID provided and attach it as /dev/sdi
.
aws_ebs_volume 'db_ebs_volume_from_snapshot' do
size 50
device '/dev/sdi'
snapshot_id 'snap-ABCDEFGH'
action [:create, :attach]
end
The elastic_ip
resource provider does not support allocating new IPs. This must be done before running a recipe that uses the resource. After allocating a new Elastic IP, we recommend storing it in a databag and loading the item in the recipe.
associate
- Associate an allocated IP to the nodedisassociate
- Disassociate an allocated IP from the node
aws_secret_access_key
,aws_access_key
and optionallyaws_session_token
- required, unless using IAM roles for authentication.ip
: String. The IP address to associate or disassociate.timeout
: Integer. Default: 180. Time in seconds to wait. 0 for unlimited.
aws_elastic_ip '34.15.30.10' do
action :associate
end
aws_elastic_ip 'Server public IP' do
ip '34.15.30.11'
action :associate
end
elastic_lb
handles registering and removing nodes from ELBs. The resource also adds basic support for creating and deleting ELBs. Note that currently this resource is not fully idempotent so it will not update the existing configuration of an ELB.
register
- Add a node to the ELBderegister
- Remove a node from the ELBcreate
- Create a new ELBdelete
- Delete an existing ELB
aws_secret_access_key
,aws_access_key
and optionallyaws_session_token
- required, unless using IAM roles for authentication.name
- the name of the ELB, required.region
, The region of the ELB. Defaults to the region of the node.listeners
, Array or hashes. The ports/protocols the ELB will listen on. See the example for a sample.security_groups
, Array. Security groups to apply to the ELB. Only needed when creating ELBs.subnets
, Array. The subnets the ELB will listen in. Only needed when creating ELBs and when using VPCs.availability_zones
: Array. The availability zones the ELB will listen in. Only needed when creating ELBs and when using classic networking.tags
: Array.scheme
: Array.
ELB running in classic networking listening on port 80.
aws_elastic_lb 'Setup the ELB' do
name 'example-elb'
action :create
availability_zones ['us-west-2a']
listeners [
{
instance_port: 80,
instance_protocol: 'HTTP',
load_balancer_port: 80,
protocol: 'HTTP',
},
]
end
To register the node in the 'QA' ELB:
aws_elastic_lb 'elb_qa' do
name 'QA'
action :register
end
Use this resource to manage IAM users.
create
: Creates the user. No effect if the user already exists.delete
: Gracefully deletes the user (detaches from all attached entities, and deletes the user).
The IAM user takes the name of the resource. A path
can be specified as well. For more information about paths, see IAM Identifiers in the Using IAM guide.
aws_iam_user 'example-user' do
action :create
path '/'
end
Use this resource to manage IAM groups. The group takes the name of the resource.
create
: Creates the group, and updates members and attached policies if the group already exists.delete
: Gracefully deletes the group (detaches from all attached entities, and deletes the group).
path
: A path can be supplied for the group. For information on paths, see IAM Identifiers in the Using IAM guide.members
: An array of IAM users that are a member of this group.remove_members
: Set tofalse
to ensure that members are not removed from the group when they are not present in the defined resource. Default:true
policy_members
: An array of ARNs of IAM managed policies to attach to this resource. Accepts both user-defined and AWS-defined policy ARNs.remove_policy_members
: Set tofalse
to ensure that policies are not detached from the group when they are not present in the defined resource. Default:true
aws_iam_group 'example-group' do
action :create
path '/'
members [
'example-user'
]
remove_members true
policy_members [
'arn:aws:iam::123456789012:policy/example-policy'
]
remove_policy_members true
end
Use this resource to create an IAM policy. The policy takes the name of the resource.
create
: Creates or updates the policy.delete
: Gracefully deletes the policy (detaches from all attached entities, deletes all non-default policy versions, then deletes the policy).
path
: A path can be supplied for the group. For information on paths, see IAM Identifiers in the Using IAM guide.policy_document
: The JSON document for the policy.account_id
: The AWS account ID that the policy is going in. Required if using non-user credentials (ie: IAM role through STS or instance role).
aws_iam_policy 'example-policy' do
action :create
path '/'
account_id '123456789012'
policy_document <<-EOH.gsub(/^ {4}/, '')
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "Stmt1234567890",
"Effect": "Allow",
"Action": [
"sts:AssumeRole"
],
"Resource": [
"arn:aws:iam::123456789012:role/example-role"
]
}
]
}
EOH
end
Use this resource to create an IAM role. The policy takes the name of the resource.
create
: Creates the role if it does not exist. If the role exists, updates attached policies and theassume_role_policy_document
.delete
: Gracefully deletes the role (detaches from all attached entities, and deletes the role).
path
: A path can be supplied for the group. For information on paths, see IAM Identifiers in the Using IAM guide.policy_members
: An array of ARNs of IAM managed policies to attach to this resource. Accepts both user-defined and AWS-defined policy ARNs.remove_policy_members
: Set tofalse
to ensure that policies are not detached from the group when they are not present in the defined resource. Default:true
assume_role_policy_document
: The JSON policy document to apply to this role for trust relationships. Dictates what entities can assume this role.
aws_iam_role 'example-role' do
action :create
path '/'
policy_members [
'arn:aws:iam::123456789012:policy/example-policy'
]
remove_policy_members true
assume_role_policy_document <<-EOH.gsub(/^ {4}/, '')
{
"Version": "2012-10-17",
"Statement": [
{
"Sid": "",
"Effect": "Deny",
"Principal": {
"AWS": "*"
},
"Action": "sts:AssumeRole"
}
]
}
EOH
end
Allows detailed CloudWatch monitoring to be enabled for the current instance.
enable
- Enable detailed CloudWatch monitoring for this instance (Default).disable
- Disable detailed CloudWatch monitoring for this instance.
aws_secret_access_key
,aws_access_key
and optionallyaws_session_token
- required, unless using IAM roles for authentication.region
- The AWS region containing the instance. Default: The current region of the node when running in AWS or us-east-1 if the node is not in AWS.
aws_instance_monitoring "enable detailed monitoring"
Allows termination protection (AKA DisableApiTermination
) to be enabled for an instance.
enable
- Enable termination protection for this instance (Default).disable
- Disable termination protection for this instance.
aws_secret_access_key
,aws_access_key
and optionallyaws_session_token
- required, unless using IAM roles for authentication.region
- The AWS region containing the instance. Default: The current region of the node when running in AWS or us-east-1 if the node is not in AWS.instance_id
- The id of the instance to modify. Default: The current instance.
aws_instance_term_protection "enable termination protection"
Use this resource to create and delete Kinesis streams. Note that this resource cannot be used to modify the shard count as shard splitting is a somewhat complex operation (for example, even CloudFormation replaces streams upon update).
create
: Creates the stream. No effect if the stream already exists.delete
: Deletes the stream.
starting_shard_count
: The number of shards the stream starts with
aws_kinesis_stream 'example-stream' do
action :create
starting_shard_count 1
end
resource_tag
can be used to manipulate the tags assigned to one or more AWS resources, i.e. ec2 instances, EBS volumes or EBS volume snapshots.
add
- Add tags to a resource.update
- Add or modify existing tags on a resource -- this is the default action.remove
- Remove tags from a resource, but only if the specified values match the existing ones.force_remove
- Remove tags from a resource, regardless of their values.
aws_secret_access_key
,aws_access_key
and optionallyaws_session_token
- required, unless using IAM roles for authentication.tags
- a hash of key value pairs to be used as resource tags, (e.g.{ "Name" => "foo", "Environment" => node.chef_environment }
,) required.resource_id
- resources whose tags will be modified. The value may be a single ID as a string or multiple IDs in an array. If noresource_id
is specified the name attribute will be used.
Assigning tags to a node to reflect its role and environment:
aws_resource_tag node['ec2']['instance_id'] do
tags('Name' => 'www.example.com app server',
'Environment' => node.chef_environment)
action :update
end
Assigning a set of tags to multiple resources, e.g. ebs volumes in a disk set:
aws_resource_tag 'my awesome raid set' do
resource_id ['vol-d0518cb2', 'vol-fad31a9a', 'vol-fb106a9f', 'vol-74ed3b14']
tags('Name' => 'My awesome RAID disk set',
'Environment' => node.chef_environment)
end
aws_resource_tag 'db_ebs_volume' do
resource_id lazy { node['aws']['ebs_volume']['db_ebs_volume']['volume_id'] }
tags ({ 'Service' => 'Frontend' })
end
create
- Create a Route53 recorddelete
- Remove a Route53 record
aws_secret_access_key
,aws_access_key
and optionallyaws_session_token
- required, unless using IAM roles for authentication.name
Required. String. - name of the domain or subdomain.value
String Array - value appropriate to thetype
.. for type 'A' value would be an IP address in IPv4 format for example.type
Required. String DNS record typettl
Integer default: 3600 - time to live, the amount of time in seconds to cache information about the recordweight
Optional. String. - a value that determines the proportion of DNS queries that will use this record for the response. Valid options are between 0-255. NOT CURRENTLY IMPLEMENTEDset_identifier
Optional . String. - a value that uniquely identifies record in the group of weighted record setsgeo_location
String.geo_location_country
Stringgeo_location_continent
Stringgeo_location_subdivision
Stringzone_id
Stringregion
Stringoverwrite
[true, false] default: truealias_target
Optional. Hash. - Associated with Amazon 'alias' type records. The hash contents varies depending on the type of target the alias points to.mock
[true, false] default: falsefail_on_error
[true, false] default: false
Create a simple record
route53_record "create a record" do
name "test"
value "16.8.4.2"
type "A"
weight "1"
set_identifier "my-instance-id"
zone_id "ID VALUE"
overwrite true
fail_on_error false
action :create
end
Delete an existing record. Note that value is still necessary even though we're deleting. This is a limitation in the AWS SDK.
aws_route53_record "delete a record" do
name "test"
value "16.8.4.2"
type 'A'
value '123'
action :delete
end
create
- Create a Route53 zonedelete
- Remove a Route53 zone
aws_secret_access_key
,aws_access_key
and optionallyaws_session_token
- required, unless using IAM roles for authentication.name
Required. String. - name of the zone.description
String. - Description shown in the Route53 UIprivate
[true, false]. default: false - Should this be a private zone for use in your VPCs or a Public zonevpc_id
String. If creating a Private zone this is the VPC to associate the zone with.
aws_route53_zone 'testkitchen.dmz' do
description 'My super important zone'
action :create
end
This feature is available only to instances within VPCs. It allows you to assign multiple private IP addresses to a network interface.
assign
- Assign a private IP to the instance.unassign
- Unassign a private IP from the instance.
aws_secret_access_key
,aws_access_key
and optionallyaws_session_token
- required, unless using IAM roles for authentication.ip
- the private IP address. - required.interface
- the network interface to assign the IP to. If none is given, uses the default interface.timeout
- connection timeout for EC2 API.
s3_file
can be used to download a file from s3 that requires aws authorization. This is a wrapper around the core chef remote_file
resource and supports the same resource attributes as remote_file
. See [remote_file Chef Docs] (https://docs.chef.io/resource_remote_file.html) for a complete list of available attributes.
aws_secret_access_key
,aws_access_key
and optionallyaws_session_token
- required, unless using IAM roles for authentication.region
- The AWS region containing the file. Default: The current region of the node when running in AWS or us-east-1 if the node is not in AWS.
create
: Downloads a file from s3create_if_missing
: Downloads a file from S3 only if it doesn't exist locallydelete
: Deletes a local filetouch
: Touches a local file
aws_s3_file '/tmp/foo' do
bucket 'i_haz_an_s3_buckit'
remote_path 'path/in/s3/bukket/to/foo'
region 'us-west-1'
end
s3_bucket
can be used to create or delete S3 buckets. Note that buckets can only be deleted if they are empty unless you specify delete_all_objects
true, which will delete EVERYTHING in your bucket first.
create
: Creates the bucketdelete
: Deletes the bucket
aws_secret_access_key
,aws_access_key
and optionallyaws_session_token
- required, unless using IAM roles for authentication.region
- The AWS region containing the bucket. Default: The current region of the node when running in AWS or us-east-1 if the node is not in AWS.versioning
- Enable or disable S3 bucket versioning. Default: falsedelete_all_objects
- Used with the:delete
action to delete all objects before deleting a bucket. Use with EXTREME CAUTION. default: false (for a reason)
aws_s3_bucket 'some-unique-name' do
aws_access_key aws['aws_access_key_id']
aws_secret_access_key aws['aws_secret_access_key']
versioning true
region 'us-west-1'
action :create
end
aws_s3_bucket 'another-unique-name' do
aws_access_key aws['aws_access_key_id']
aws_secret_access_key aws['aws_secret_access_key']
region 'us-west-1'
action :delete
end
The secondary_ip
resource provider allows one to assign/un-assign multiple private secondary IPs on an instance within a VPC. The number of secondary IP addresses that you can assign to an instance varies by instance type. If no ip address is provided on assign, a random one from within the subnet will be assigned. If no interface is provided, the default interface as determined by Ohai will be used.
aws_secondary_ip 'assign_additional_ip' do
aws_access_key aws['aws_access_key_id']
aws_secret_access_key aws['aws_secret_access_key']
ip ip_info['private_ip']
interface 'eth0'
action :assign
end
- Author:: Chris Walters ([email protected])
- Author:: AJ Christensen ([email protected])
- Author:: Justin Huff ([email protected])
Copyright 2009-2016, Chef Software, Inc.
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.