Store credentials in the cloud development platform’s secret facility, grant them only to the people and repositories that need them, and assume any code running in a session can read secrets exposed to that session. A cloud container is not a safe boundary by itself, and “ephemeral” does not necessarily mean that files, credentials, or copies are erased.
The details differ across GitHub Codespaces, AWS CloudShell, and Google Cloud Shell. The controls below explain where credentials become available, what can persist, and how to reduce exposure in interactive development and automation.
Start with a safe handling pattern
- Use a dedicated secret store. Add credentials to the platform’s secret settings or secret manager, not source code, a checked-in
.envfile, a Dockerfile, logs, screenshots, or command output. - Limit scope. Grant each credential to the smallest practical set of users, repositories, cloud roles, resources, and actions. Prefer short-lived or federated credentials when the workflow supports them.
- Review what runs in the session. Treat repository setup files, lifecycle scripts, extensions, and other code as potentially able to use credentials available to the session.
- Expose credentials only when needed. Check which stage of environment creation or execution receives the secret. Avoid injecting a value into build steps or processes that do not need it.
- Check for copies before sharing or ending a session. Inspect files, shell history, logs, caches, artifacts, and persistent home directories. Cleanup behavior varies by platform.
If a credential may have been exposed, revoke or rotate it with its issuer, review access logs, and remove persisted copies.
How secrets behave in GitHub Codespaces
Store and scope development environment secrets
GitHub calls its feature “development environment secrets.” Secrets can be managed at personal, repository, or organization level; organization secrets can be restricted using repository access policies. GitHub documents a limit of 100 secrets per organization and 100 per repository, with a maximum size of 48 KB per secret. These are documented product limits and may change; check GitHub’s Codespaces secret guidance for current details.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
A newly created or changed secret becomes available when a codespace is created or restarted. An already-running codespace will not receive a changed value until it is stopped and restarted. See GitHub’s repository and organization secret instructions.
Know which processes can read them
Codespaces exports development environment secrets as environment variables into the user’s terminal session after the codespace is built and running. A process that can access that environment can use the values, so avoid printing them or passing them to untrusted commands.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
They are not available during Dockerfile build time or while a custom entry point is running at build time. This separation matters: do not put a secret in a Dockerfile to work around the timing limitation. GitHub describes availability and timing in its account-specific secret documentation.
Review repository setup and extensions
GitHub says each codespace uses its own newly built VM, but that does not make every repository or process trustworthy. A devcontainer.json configuration can install third-party extensions or run arbitrary postCreateCommand code. Extensions and lifecycle scripts operating in a session may be able to use credentials available there. Open trusted repositories, review setup changes, and restrict secrets and features to what the task requires. See GitHub’s Codespaces security guidance.
Free tools Windows power users keep installed
One-click scans. No signup required.
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
How credentials and persistence work in AWS CloudShell
Use IAM as the security boundary
AWS CloudShell automatically makes AWS console credentials available to a new shell session. AWS describes these as temporary, regularly rotated IAM credentials whose permissions are scoped to the user’s permissions. Its security guidance is explicit: “These credentials are the security boundary, not the container itself.” Therefore, use least-privilege IAM permissions and do not rely on the shell’s container boundary to protect credentials from code running inside it. AWS explains the model in its CloudShell IAM access documentation and CloudShell security FAQs.
Administrators can use IAM policies to deny forwarding console credentials into CloudShell. If forwarding is denied, users must configure credentials manually for AWS CLI access, so apply this control where the session does not need console credentials and plan for the resulting workflow.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
Check the CloudShell environment type before relying on cleanup
Persistence differs between public and VPC CloudShell. Public CloudShell home data is stored using Amazon S3 and persists. VPC CloudShell home data is deleted when the environment times out, is restarted, or is deleted. AWS documents an inactivity timeout of 20–30 minutes for VPC environments and 10 minutes in AWS GovCloud (US); these timings describe VPC CloudShell, not public CloudShell. Details are in AWS’s CloudShell overview.
Do not infer that all copies of a credential disappear just because a VPC environment is deleted. A secret copied into another file, log, artifact, or external service may have a different lifecycle.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
What Google Cloud Shell’s ephemeral VM does—and does not—mean
Google documents Cloud Shell as a preconfigured VM that is ephemeral by default. It prompts for authorization before Cloud API calls and sets GOOGLE_CLOUD_PROJECT from the active project in the console. Google also states that the VM is not directly associated with or managed by that project, and that the allocated VM user has root privileges. See Google’s explanation of how Cloud Shell works.
Ephemeral compute is not proof that every credential or user-created copy has been removed. Avoid storing secrets in files or output, and check any locations where your workflow may have copied them.
Choose credentials and controls for the workflow
| Approach | Credential and access model | Exposure to session code | Persistence considerations | Best fit |
|---|---|---|---|---|
| Platform development-environment secret | Stored in platform secret settings; scope can be personal, repository, or organization (Codespaces). | Available to processes that receive the environment variable; in Codespaces, after build and startup. | Check session files, logs, history, and other copies; timing and cleanup depend on platform. | Interactive cloud development where a task needs a specific secret. |
| CloudShell session identity | AWS CloudShell forwards temporary IAM credentials scoped to the user’s permissions; policies can deny forwarding. | Code running in the session can use credentials available to that session. | AWS public and VPC CloudShell home directories have different persistence behavior. | Interactive AWS administration with appropriately limited IAM permissions. |
| Federated role assumption for automation | A GitHub job can assume an AWS role through GitHub OIDC and retrieve values from Secrets Manager rather than store another AWS access key. | Limit access to the job and steps that need the value; AWS documents masking retrieved values as job environment variables. | Review job logs, artifacts, and any copied values as well as secret-store policy. | Automated GitHub workflows needing AWS secrets. |
The table compares documented patterns, not a vendor-published security ranking. Choose based on credential lifetime, permission scope, which processes need access, and what your environment preserves.
Use OIDC for GitHub automation where it fits
For a GitHub job that needs AWS Secrets Manager values, AWS documents using aws-actions/aws-secretsmanager-get-secrets@v2 and recommends GitHub OIDC role assumption for short-lived credentials. This avoids adding another long-lived AWS access key to GitHub’s stored secrets. The role still needs appropriately narrow permissions, and job steps that receive retrieved values must be treated as trusted code. Follow the AWS Secrets Manager guide for GitHub Actions to configure the integration.
Recommended Free Tools
Quick Recap
Before you close, share, or troubleshoot a session
- Search the working tree and relevant home directories for accidental copies of credentials, especially local environment files and generated configuration.
- Review shell history, logs, build output, caches, and artifacts for commands or values that may have exposed a secret.
- Check whether the home directory persists for the specific platform and environment type; do not assume all cloud sessions clean up alike.
- Rotate or revoke a credential if it may have been exposed, then review the issuer’s access logs and remove remaining copies.
- If a new Codespaces secret is missing, stop and restart the codespace so the updated value is loaded.
- If CloudShell CLI commands fail after credential forwarding is blocked, configure credentials through an approved method rather than weakening the IAM policy without review.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
