Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>You workaround is a reasonable one (and shows that you seem to be in control of your AWS operations already).</p> <p>You could improve on your custom solution eventually by means of the dedicated <a href="http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/aws-resource-cfn-customresource.html" rel="nofollow">CustomResource</a> type, which are <em>special AWS CloudFormation resources that provide a way for a template developer to include resources in an AWS CloudFormation stack that are provided by a source other than Amazon Web Services.</em> - the <a href="http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/crpg-walkthrough.html" rel="nofollow">AWS CloudFormation Custom Resource Walkthrough</a> provides a good overview of what this is all about, how it works and what's required to implement your own.</p> <p>The benefit of using this facade for a custom resource (i.e. the <a href="http://aws.amazon.com/elasticache/" rel="nofollow">Amazon ElastiCache</a> cluster in your case) is that its entire lifecycle (create/update/delete) can be handled in a similar and controlled fashion just like any officially supported CloudFormation resource types, e.g. resource creation failures would be handled transparently from the perspective of the entire stack.</p> <p>However, for the use case at hand you might actually just want to wait for official support becoming available:</p> <p><ul> <li>AWS has announced VPC support for ElastiCache in the context of the recent major <a href="http://aws.typepad.com/aws/2013/03/amazon-ec2-update-virtual-private-clouds-for-everyone.html" rel="nofollow">Amazon EC2 Update - Virtual Private Clouds for Everyone!</a>, which boils down to <em>Default VPCs for (Almost) Everyone</em>.<br></p> <blockquote> <p>We want every EC2 user to be able to benefit from the advanced networking and other features of Amazon VPC that I outlined above. To enable this, starting soon, instances for new AWS customers (and existing customers launching in new Regions) will be launched into the "EC2-VPC" platform. [...]</p> <p>You don’t need to create a VPC beforehand - simply launch EC2 instances or provision Elastic Load Balancers, RDS databases, <strong>or ElastiCache clusters</strong> like you would in EC2-Classic and we’ll create a VPC for you at no extra charge. We’ll launch your resources into that VPC [...] <em>[emphasis mine]</em></li> <li>This update sort of implies that any new services will likely be also available in VPC right away going forward (else the new <em>EC2-VPC</em> platform wouldn't work automatically for new customers as envisioned).</li> </ul> Accordingly I'd expect the CloudFormation team to follow suit and complete/amend their support for deployment to VPC going forward as well.</p> </blockquote>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload