Terima Kasih Telah Memverifikasi Email Shopee-mu

Hai bobyirawan943,   Mohon verifikasi & daftarkan email bobyirawan97@gmail.com dengan klik tautan di bawah untuk mendapatkan promo terbaru serta penawaran eksklusif. Ya, saya mau verifikasi & daftar newsletter! Tidak, cukup verifikasi email Salam, Tim Shopee Butuh bantuan? Hubungi kami di sini.

Ayo, Belanja di Shopee!

 

Kebijakan Privasi | Syarat Layanan   Ini adalah email otomatis. Mohon untuk tidak membalas email ini. Tambahkan info@mail.shopee.co.id pada daftar kontak untuk memastikan email dari Shopee masuk ke inbox-mu.   Pacific Century Place Lt. 26 SCBD Lot 10, Jl. Jendral Sudirman Kav 52-53 Jakarta Indonesia 12190

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

READ MORE - Terima Kasih Telah Memverifikasi Email Shopee-mu

Security alert for bobyirawan92@gmail.com

This is a copy of a security alert sent to bobyirawan92@gmail.com. bobyirawan97@gmail.com is the recovery email for this account. If you don't recognize this account, remove it. A new sign-in on Windows bobyirawan92@gmail.com We noticed a new sign-in to your Google Account on a Windows device. If this was you, you don’t need to do anything. If not, we’ll help you secure your account. Check activity You can also see security activity at https://myaccount.google.com/notifications You received this email to let you know about important changes to your Google Account and services. © 2026 Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA

READ MORE - Security alert for bobyirawan92@gmail.com

Security alert for bobyirawan92@gmail.com

This is a copy of a security alert sent to bobyirawan92@gmail.com. bobyirawan97@gmail.com is the recovery email for this account. If you don't recognize this account, remove it. A new sign-in on Vivo 1904 bobyirawan92@gmail.com We noticed a new sign-in to your Google Account on a Vivo 1904 device. If this was you, you don’t need to do anything. If not, we’ll help you secure your account. Check activity You can also see security activity at https://myaccount.google.com/notifications You received this email to let you know about important changes to your Google Account and services. © 2026 Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA

READ MORE - Security alert for bobyirawan92@gmail.com

[Action Advised] Review Google Cloud credential security best practices

Secure service account and API keys to prevent unauthorized access.

MY CONSOLE   Hello Boby, We're writing to provide you with security best practices regarding the management of service account keys and API keys within your Google Cloud environment. Recent security trends indicate that long-lived credentials without proper security best practices remain a top security risk for unauthorized access. To ensure your environment remains secure, and to modernize your authentication strategy, we strongly advise implementing the unified security framework outlined below. What you need to do Action advised: Secure the credential lifecycle: Apply standard security hygiene by following these best practices: Zero-Code Storage: Never commit keys to source code or version control. Use Secret Manager to inject credentials at runtime. Disable Dormant Keys: Audit your active keys and decommission any that show no activity over the last 30 days. Enforce API Restrictions: Never leave an API key unrestricted. Limit keys to specific APIs (e.g., Maps Java Script only) and apply environmental restrictions (IP addresses, HTTP referrers, or bundle IDs). Apply Least Privilege: Never give full permissions to a service account. Use the IAM recommender to prune unused permissions for service accounts, ensuring only the absolute minimum access required for their function. Mandatory Rotation: Implement the iam.serviceAccountKeyExpiryHours policy to enforce a maximum lifespan for all user-managed service account keys. If service account keys are not needed, implement iam.managed.disableServiceAccountKeyCreation to disable the creation of new service account keys. Improve operational safeguards: Ensure a rapid response to security incidents by completing the following: Set Essential Contacts: Verify that your Essential Contacts are up to date to ensure critical security notifications reach the right people during an incident. Set Billing Anomaly and Budget Alerts: Ensure billing anomaly and budget alerts notifications are acted on. A sudden spike in consumption is often the first indicator of a compromised credential. We're here to help We are committed to helping you maintain a secure environment. If you have any questions or require assistance, please contact Google Cloud Support. Thanks for choosing Google Cloud. – The Google Cloud Team DOCUMENTATION SUPPORT

Was this information helpful?         © 2026 Google LLC 1600 Amphitheatre Parkway, Mountain View, CA 94043 You've received this mandatory service announcement to update you about important changes to Google Cloud or your account.

                                                                                     

READ MORE - [Action Advised] Review Google Cloud credential security best practices

[Product Update] Automatic enablement of new OpenTelemetry ingestion API

project_number,project_id,project_name
250107212471,planar-name-431008-j3,My First Project

We're enabling a new OTLP ingestion API starting Mar 4, 2026.

MY CONSOLE Hello Boby, We're writing to let you know that Cloud Observability has launched a new OpenTelemetry (OTel) ingestion API that supports native OpenTelemetry Protocol (OTLP) logs, trace spans, and metrics. Starting March 4, 2026, this API will be added as a dependency for the current Cloud Logging, Cloud Trace, and Cloud Monitoring ingestion APIs. This change ensures a seamless transition as collection tools migrate to this new unified endpoint. What you need to know Key changes: The existing Cloud Observability ingestion APIs (logging.googleapis.com, cloudtrace.googleapis.com, and monitoring.googleapis.com) are automatically activated when you create a Google Cloud project using the Google Cloud console or gcloud CLI. The behavior remains unchanged for projects created via API, which do not have these ingestion APIs enabled by default. Starting March 4, 2026, the new OTel ingestion endpoint telemetry.googleapis.com will automatically activate when any of these specified APIs are enabled. In addition, we will automatically enable this new endpoint for all existing projects that already have current ingestion APIs active. What you need to do No action is required from you for this API enablement change, and there will be no disruption to your existing services. You may disable the API at any time by following these instructions. Refer to the attachment for a list of the projects that will automatically enable the new endpoint. We're here to help If you have any questions or require assistance, please contact Google Cloud Support. Thanks for choosing Google Cloud Observability. – The Google Cloud Team SUPPORT

Was this information helpful?         © 2026 Google LLC 1600 Amphitheatre Parkway, Mountain View, CA 94043 You've received this mandatory service announcement to update you about important changes to Google Cloud or your account.

                                                                                     

READ MORE - [Product Update] Automatic enablement of new OpenTelemetry ingestion API