Memcached Layer
    Provides an OpsWorks memcached layer resource.
Example Usage
import * as pulumi from "@pulumi/pulumi";
import * as aws from "@pulumi/aws";
const cache = new aws.opsworks.MemcachedLayer("cache", {stackId: main.id});Content copied to clipboard
import pulumi
import pulumi_aws as aws
cache = aws.opsworks.MemcachedLayer("cache", stack_id=main["id"])Content copied to clipboard
using System.Collections.Generic;
using System.Linq;
using Pulumi;
using Aws = Pulumi.Aws;
return await Deployment.RunAsync(() =>
{
    var cache = new Aws.OpsWorks.MemcachedLayer("cache", new()
    {
        StackId = main.Id,
    });
});Content copied to clipboard
package main
import (
	"github.com/pulumi/pulumi-aws/sdk/v6/go/aws/opsworks"
	"github.com/pulumi/pulumi/sdk/v3/go/pulumi"
)
func main() {
	pulumi.Run(func(ctx *pulumi.Context) error {
		_, err := opsworks.NewMemcachedLayer(ctx, "cache", &opsworks.MemcachedLayerArgs{
			StackId: pulumi.Any(main.Id),
		})
		if err != nil {
			return err
		}
		return nil
	})
}Content copied to clipboard
package generated_program;
import com.pulumi.Context;
import com.pulumi.Pulumi;
import com.pulumi.core.Output;
import com.pulumi.aws.opsworks.MemcachedLayer;
import com.pulumi.aws.opsworks.MemcachedLayerArgs;
import java.util.List;
import java.util.ArrayList;
import java.util.Map;
import java.io.File;
import java.nio.file.Files;
import java.nio.file.Paths;
public class App {
    public static void main(String[] args) {
        Pulumi.run(App::stack);
    }
    public static void stack(Context ctx) {
        var cache = new MemcachedLayer("cache", MemcachedLayerArgs.builder()
            .stackId(main.id())
            .build());
    }
}Content copied to clipboard
resources:
  cache:
    type: aws:opsworks:MemcachedLayer
    properties:
      stackId: ${main.id}Content copied to clipboard
Properties
Link copied to clipboard
                Link copied to clipboard
                Link copied to clipboard
                Link copied to clipboard
                A map of tags to assign to the resource. .If configured with a provider default_tags configuration block present, tags with matching keys will overwrite those defined at the provider-level. The following extra optional arguments, all lists of Chef recipe names, allow custom Chef recipes to be applied to layer instances at the five different lifecycle events, if custom cookbooks are enabled on the layer's stack:
Link copied to clipboard