Using Outposts - Amazon ElastiCache for Redis
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China.

Using Outposts

Amazon Outposts is a fully managed service that extends Amazon infrastructure, services, APIs, and tools to customer premises. By providing local access to Amazon managed infrastructure, Amazon Outposts enables customers to build and run applications on premises using the same programming interfaces as in Amazon Regions, while using local compute and storage resources for lower latency and local data processing needs. An Outpost is a pool of Amazon compute and storage capacity deployed at a customer site. Amazon operates, monitors, and manages this capacity as part of an Amazon Region. You can create subnets on your Outpost and specify them when you create Amazon resources such as ElastiCache clusters.

Note

In this version, the following limitations apply:

  • ElastiCache for Outposts only supports M5 and R5 node families.

  • Live migration is not supported.

  • Multi-AZ (cross Outpost replication is not supported).

  • Local snapshots are not supported.

  • ElastiCache for Outposts is not supported in the following regions: cn-north-1, cn-northwest-1 and ap-northeast-3.

Using Outposts with the Redis console

  1. Sign in to the Amazon Web Services Management Console and open the ElastiCache console at https://console.amazonaws.cn/elasticache/.

  2. On the navigation pane, choose Redis.

  3. In Cluster Engine, select Redis.

  4. Under Location, select On-Premises - Create your ElastiCache instances on Amazon Outposts.

Configure on-premises options

You can select either an available Outpost to add your cache cluster or, if there are no available Outposts, create a new one using the following steps:

Under On-Premises options:

  1. Under Redis settings:

    1. Name: Enter a name for the Redis cluster

    2. Description: Enter a description for the Redis cluster.

    3. Engine version compatilbility: Engine version is based on the Amazon Outpost region

    4. Port: Accept the default port, 6379. If you have a reason to use a different port, type the port number.

    5. Parameter group: Use the drop-down to select a default or custom parameter group.

    6. Node Type: Available instances are based on Outposts availability. Porting Assistant for .NET for Outposts only supports M5 and R5 node families. From the drop down list, select Outposts and then select an available node type you want to use for this cluster. Then select Save.

    7. Number of Replicas: Enter the number of read replicas you want created for this replication group. You must have at least one and no more than five read replicas. The default value is 2.

      The autogenerated names of the read replicas follow the same pattern as that of the primary cluster's name, with a dash and sequential three-digit number added to the end, beginning with -002. For example, if your replication group is named MyGroup, then the names of the secondaries would be MyGroup-002, MyGroup-003, MyGroup-004, MyGroup-005, MyGroup-006.

  2. Under Advanced Redis settings:

    1. Subnet Group: From the list, select Create new.

      • Name: Enter a name for the subnet group

      • Description: Enter a description for the subnet group

      • VPC ID: The VPC ID should match the Outpost VPC. If you select a VPC that has no subnet IDs on the Outposts, the list will return empty.

      • Availability Zone or Outpost: Select the Outpost you are using.

      • Subnet ID: Select a subnet ID that is available for the Outpost. If there are no subnet IDs available, you need to create them. For more information, see Create a Subnet.

    2. Select Create.

Viewing Outpost cluster details

On the Redis list page, select a cluster that belongs to an Amazon Outpost and note the following when viewing the Cluster details:

  • Availability Zone: This will represent the Outpost, using an ARN (Amazon Resource Name) and the Amazon Resource Number.

  • Outpost name: The name of the Amazon Outpost.

Using Outposts with the Amazon CLI

You can use the Amazon Command Line Interface (Amazon CLI) to control multiple Amazon services from the command line and automate them through scripts. You can use the Amazon CLI for ad hoc (one-time) operations.

Downloading and configuring the Amazon CLI

The Amazon CLI runs on Windows, macOS, or Linux. Use the following procedure to download and configure it.

To download, install, and configure the CLI

  1. Download the Amazon CLI on the Amazon Command Line Interface webpage.

  2. Follow the instructions for Installing the Amazon CLI and Configuring the Amazon CLI in the Amazon Command Line Interface User Guide.

Using the Amazon CLI with Outposts

Use the following CLI operation to create a cache cluster that uses Outposts:

  • create-cache-cluster – Using this operation, the outpost-mode parameter accepts a value that specifies whether the nodes in the cache cluster are created in a single Outpost or across multiple Outposts.

    Note

    At this time, only single-outpost mode is supported.

    aws elasticache create-cache-cluster \ --cache-cluster-id cache cluster id \ --outpost-mode single-outpost \