Menggunakan Kontrol Layanan VPC dengan Memorystore for Redis
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Anda dapat melindungi instance Memorystore for Redis menggunakan Kontrol Layanan VPC.
Kontrol Layanan VPC melindungi dari pemindahan data yang tidak sah dan memberikan lapisan keamanan tambahan untuk instance Anda. Untuk informasi selengkapnya tentang
Kontrol Layanan VPC, lihat Ringkasan Kontrol Layanan VPC.
Setelah Memorystore for Redis API dilindungi oleh perimeter layanan Anda,
permintaan Memorystore for Redis API yang berasal dari klien di luar perimeter
harus memiliki aturan tingkat akses yang sesuai.
Melindungi instance Redis menggunakan Kontrol Layanan VPC
Tambahkan Memorystore for Redis API ke perimeter layanan Anda. Untuk
mengetahui petunjuk cara menambahkan layanan ke perimeter layanan, lihat
Memperbarui perimeter layanan.
Persyaratan konfigurasi
Jika menggunakan VPC Bersama dan Kontrol Layanan VPC, Anda harus memiliki project host yang menyediakan jaringan dan project layanan yang berisi instance Redis di dalam perimeter yang sama agar permintaan Redis berhasil.
Jika tidak, permintaan antara instance project layanan dan jaringan project host akan diblokir oleh perimeter layanan Kontrol Layanan VPC.
Kapan saja, memisahkan project host dan project layanan dengan perimeter dapat menyebabkan kegagalan instance Redis, selain permintaan yang diblokir.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-08-19 UTC."],[],[],null,["# Use VPC Service Controls with Memorystore for Redis\n\nYou can protect your Memorystore for Redis instances using VPC Service Controls.\n\nVPC Service Controls protect against data exfiltration and provide an extra\nlayer of security for your instances. For more information about\nVPC Service Controls, see [Overview of VPC Service Controls](/vpc-service-controls/docs/overview).\n\nOnce the Memorystore for Redis API is protected by your service perimeter,\nMemorystore for Redis API requests coming from clients outside of the perimeter\nmust have the proper access level rules.\n\nProtecting your Redis instances using VPC Service Controls\n----------------------------------------------------------\n\n1. [Create a service perimeter](/vpc-service-controls/docs/create-service-perimeters).\n\n2. Add the Memorystore for Redis API to your service perimeter. For\n instructions on adding a service to your service perimeter, see\n [Updating a service perimeter](/vpc-service-controls/docs/manage-service-perimeters#update).\n\nConfiguration requirements\n--------------------------\n\nIf you use both Shared VPC and VPC Service Controls, you must have the host\nproject that provides the network and the service project that contains the\nRedis instance inside the same perimeter in order for Redis requests to succeed.\nOtherwise, requests between the service project instance and the host project\nnetwork are blocked by the VPC Service Controls service perimeter.\n\nAt any time, separating the host project and service project with a perimeter\ncan cause a Redis instance failure, in addition to blocked requests.\n\nLimitations of VPC Service Controls for Redis instances\n-------------------------------------------------------\n\nFor a list of VPC Service Controls limitations for\nMemorystore, see [Supported products and limitations](/vpc-service-controls/docs/supported-products#memstore-redis)"]]
