{ "api_version": "1", "kind": "dse_post", "self": "https://update.dsesecurity.com/api/v1/posts/prepare-ec2-stop-start-changes-around-ephemeral-storage-and-public-addresses/", "item": { "id": "https://update.dsesecurity.com/updates/prepare-ec2-stop-start-changes-around-ephemeral-storage-and-public-addresses/", "slug": "prepare-ec2-stop-start-changes-around-ephemeral-storage-and-public-addresses", "url": "https://update.dsesecurity.com/updates/prepare-ec2-stop-start-changes-around-ephemeral-storage-and-public-addresses/", "alternate_urls": { "markdown": "https://update.dsesecurity.com/updates/prepare-ec2-stop-start-changes-around-ephemeral-storage-and-public-addresses.md", "json": "https://update.dsesecurity.com/api/v1/posts/prepare-ec2-stop-start-changes-around-ephemeral-storage-and-public-addresses/" }, "title": "Prepare EC2 stop-start changes around ephemeral storage and public addresses", "summary": "A stopped instance persists, but every runtime dependency may not survive the restart.", "format": { "slug": "guide", "name": "Guide" }, "priority": { "slug": "info", "name": "Information" }, "featured": false, "image": { "theme": "cyber-defense", "label": "Cyber defense", "alt": "Layered glass and metal cyber-defense structure with controlled blue and gold signal paths.", "card_url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-card.webp?v=1.8.20", "hero_url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-hero.webp?v=1.8.20", "social_url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20", "width": 2400, "height": 1350 }, "topics": [ { "slug": "cybersecurity", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "slug": "it", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "author": { "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team", "type": "Organization" }, "publisher": { "name": "Detection Systems & Engineering", "url": "https://dsesecurity.com/" }, "published_at": "2026-10-20T18:13:52+00:00", "modified_at": "2026-10-20T18:34:29+00:00", "reviewed_on": "2026-10-20", "reading_minutes": 2, "word_count": 245, "potentially_affected": "This applies to an EC2 stop/start maintenance operation, not hibernation or termination.", "dse_recommendation": "DSE recommends identifying instance-store use, address dependencies and application shutdown requirements before scheduling maintenance.", "primary_source": { "name": "AWS Documentation", "url": "https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Stop_Start.html", "published_on": null, "authority": "docs.aws.amazon.com" }, "publishing_principles": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usage_info": "https://update.dsesecurity.com/usage/", "copyright_notice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "content_html": "

A stopped instance persists, but every runtime dependency may not survive the restart.

\n

Source facts

\n

AWS supports stop/start for EBS-root instances. Starting typically moves the instance to another host and assigns a new public IPv4 address. Stopping erases data on instance-store volumes. AWS recommends copying required instance-store data to persistent storage before the stop and warns that bypassing graceful shutdown risks data integrity.

\n

Source: AWS Documentation.

\n

Applicability

\n

This applies to an EC2 stop/start maintenance operation, not hibernation or termination.

\n

DSE recommendation

\n

DSE recommends identifying instance-store use, address dependencies and application shutdown requirements before scheduling maintenance. Review DNS, allowlists and remote-management access that may depend on the current public address. Preserve required runtime data and confirm the restart procedure with the application owner. Assign someone to validate service recovery, and keep a route to the instance that does not assume the old address remains valid. Record the approved maintenance window and rollback options before stopping the workload. Require the maintenance owner to list the service checks needed after startup, including external callers and stored data. Capture a harmless before-and-after inventory in rehearsal, and make unresolved address or storage dependencies a reason to revise the maintenance plan.

\n

Verification

\n

Proposed verification: rehearse on a representative test instance, compare storage and network identities before and after, and validate the application’s start sequence. Confirm persistent data remains accessible and intentionally ephemeral data is handled correctly before approving the same operation in production.

\n

Official reference

\n

AWS Documentation. Reviewed October 20, 2026.

", "content_text": "A stopped instance persists, but every runtime dependency may not survive the restart.\nSource facts\nAWS supports stop/start for EBS-root instances. Starting typically moves the instance to another host and assigns a new public IPv4 address. Stopping erases data on instance-store volumes. AWS recommends copying required instance-store data to persistent storage before the stop and warns that bypassing graceful shutdown risks data integrity.\nSource: AWS Documentation.\nApplicability\nThis applies to an EC2 stop/start maintenance operation, not hibernation or termination.\nDSE recommendation\nDSE recommends identifying instance-store use, address dependencies and application shutdown requirements before scheduling maintenance. Review DNS, allowlists and remote-management access that may depend on the current public address. Preserve required runtime data and confirm the restart procedure with the application owner. Assign someone to validate service recovery, and keep a route to the instance that does not assume the old address remains valid. Record the approved maintenance window and rollback options before stopping the workload. Require the maintenance owner to list the service checks needed after startup, including external callers and stored data. Capture a harmless before-and-after inventory in rehearsal, and make unresolved address or storage dependencies a reason to revise the maintenance plan.\nVerification\nProposed verification: rehearse on a representative test instance, compare storage and network identities before and after, and validate the application’s start sequence. Confirm persistent data remains accessible and intentionally ephemeral data is handled correctly before approving the same operation in production.\nOfficial reference\nAWS Documentation. Reviewed October 20, 2026.", "content_markdown": "A stopped instance persists, but every runtime dependency may not survive the restart.\n\n## Source facts\n\nAWS supports stop/start for EBS-root instances. Starting typically moves the instance to another host and assigns a new public IPv4 address. Stopping erases data on instance-store volumes. AWS recommends copying required instance-store data to persistent storage before the stop and warns that bypassing graceful shutdown risks data integrity.\n\nSource: [AWS Documentation](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Stop_Start.html).\n\n## Applicability\n\nThis applies to an EC2 stop/start maintenance operation, not hibernation or termination.\n\n## DSE recommendation\n\nDSE recommends identifying instance-store use, address dependencies and application shutdown requirements before scheduling maintenance. Review DNS, allowlists and remote-management access that may depend on the current public address. Preserve required runtime data and confirm the restart procedure with the application owner. Assign someone to validate service recovery, and keep a route to the instance that does not assume the old address remains valid. Record the approved maintenance window and rollback options before stopping the workload. Require the maintenance owner to list the service checks needed after startup, including external callers and stored data. Capture a harmless before-and-after inventory in rehearsal, and make unresolved address or storage dependencies a reason to revise the maintenance plan.\n\n## Verification\n\nProposed verification: rehearse on a representative test instance, compare storage and network identities before and after, and validate the application’s start sequence. Confirm persistent data remains accessible and intentionally ephemeral data is handled correctly before approving the same operation in production.\n\n## Official reference\n\n[AWS Documentation](https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Stop_Start.html). Reviewed October 20, 2026." }, "json_ld": { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://dsesecurity.com/#organization", "name": "Detection Systems & Engineering", "alternateName": "DSE Security", "url": "https://dsesecurity.com/", "logo": { "@type": "ImageObject", "url": "https://update.dsesecurity.com/assets/dse-logo-20260812.png?v=1.8.20" } }, { "@type": "Organization", "@id": "https://update.dsesecurity.com/#editorial-team", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/", "parentOrganization": { "@id": "https://dsesecurity.com/#organization" } }, { "@type": "WebSite", "@id": "https://update.dsesecurity.com/#website", "name": "DSE Updates", "alternateName": "DSE Security Knowledge Hub", "url": "https://update.dsesecurity.com/", "inLanguage": "en-US", "publisher": { "@id": "https://dsesecurity.com/#organization" }, "potentialAction": { "@type": "SearchAction", "target": { "@type": "EntryPoint", "urlTemplate": "https://update.dsesecurity.com/?q={search_term_string}" }, "query-input": "required name=search_term_string" } }, { "@type": "WebPage", "@id": "https://update.dsesecurity.com/updates/prepare-ec2-stop-start-changes-around-ephemeral-storage-and-public-addresses/", "url": "https://update.dsesecurity.com/updates/prepare-ec2-stop-start-changes-around-ephemeral-storage-and-public-addresses/", "isPartOf": { "@id": "https://update.dsesecurity.com/#website" }, "lastReviewed": "2026-10-20" }, { "@type": "BreadcrumbList", "@id": "https://update.dsesecurity.com/updates/prepare-ec2-stop-start-changes-around-ephemeral-storage-and-public-addresses/#breadcrumbs", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "DSE Updates", "item": "https://update.dsesecurity.com/" }, { "@type": "ListItem", "position": 2, "name": "Cybersecurity", "item": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "@type": "ListItem", "position": 3, "name": "Prepare EC2 stop-start changes around ephemeral storage and public addresses", "item": "https://update.dsesecurity.com/updates/prepare-ec2-stop-start-changes-around-ephemeral-storage-and-public-addresses/" } ] }, { "@type": [ "Article", "TechArticle" ], "@id": "https://update.dsesecurity.com/updates/prepare-ec2-stop-start-changes-around-ephemeral-storage-and-public-addresses/#article", "identifier": "https://update.dsesecurity.com/updates/prepare-ec2-stop-start-changes-around-ephemeral-storage-and-public-addresses/", "url": "https://update.dsesecurity.com/updates/prepare-ec2-stop-start-changes-around-ephemeral-storage-and-public-addresses/", "headline": "Prepare EC2 stop-start changes around ephemeral storage and public addresses", "description": "A stopped instance persists, but every runtime dependency may not survive the restart.", "abstract": "A stopped instance persists, but every runtime dependency may not survive the restart.", "articleBody": "A stopped instance persists, but every runtime dependency may not survive the restart.\nSource facts\nAWS supports stop/start for EBS-root instances. Starting typically moves the instance to another host and assigns a new public IPv4 address. Stopping erases data on instance-store volumes. AWS recommends copying required instance-store data to persistent storage before the stop and warns that bypassing graceful shutdown risks data integrity.\nSource: AWS Documentation.\nApplicability\nThis applies to an EC2 stop/start maintenance operation, not hibernation or termination.\nDSE recommendation\nDSE recommends identifying instance-store use, address dependencies and application shutdown requirements before scheduling maintenance. Review DNS, allowlists and remote-management access that may depend on the current public address. Preserve required runtime data and confirm the restart procedure with the application owner. Assign someone to validate service recovery, and keep a route to the instance that does not assume the old address remains valid. Record the approved maintenance window and rollback options before stopping the workload. Require the maintenance owner to list the service checks needed after startup, including external callers and stored data. Capture a harmless before-and-after inventory in rehearsal, and make unresolved address or storage dependencies a reason to revise the maintenance plan.\nVerification\nProposed verification: rehearse on a representative test instance, compare storage and network identities before and after, and validate the application’s start sequence. Confirm persistent data remains accessible and intentionally ephemeral data is handled correctly before approving the same operation in production.\nOfficial reference\nAWS Documentation. Reviewed October 20, 2026.", "datePublished": "2026-10-20T18:13:52+00:00", "dateModified": "2026-10-20T18:34:29+00:00", "mainEntityOfPage": { "@id": "https://update.dsesecurity.com/updates/prepare-ec2-stop-start-changes-around-ephemeral-storage-and-public-addresses/" }, "inLanguage": "en-US", "isAccessibleForFree": true, "author": { "@type": "Organization", "name": "DSE Security Editorial Team", "url": "https://update.dsesecurity.com/#editorial-team" }, "publisher": { "@id": "https://dsesecurity.com/#organization" }, "image": { "@type": "ImageObject", "@id": "https://update.dsesecurity.com/updates/prepare-ec2-stop-start-changes-around-ephemeral-storage-and-public-addresses/#primaryimage", "url": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20", "contentUrl": "https://update.dsesecurity.com/assets/editorial/cyber-defense-social-v2.jpg?v=1.8.20", "width": 1200, "height": 630, "caption": "Prepare EC2 stop-start changes around ephemeral storage and public addresses" }, "articleSection": [ "Cybersecurity", "IT" ], "keywords": [ "Cybersecurity", "IT", "Guide", "Information priority" ], "genre": "Guide", "about": [ { "@type": "Thing", "name": "Cybersecurity", "url": "https://update.dsesecurity.com/topic/cybersecurity/" }, { "@type": "Thing", "name": "IT", "url": "https://update.dsesecurity.com/topic/it/" } ], "wordCount": 245, "timeRequired": "PT2M", "publishingPrinciples": "https://update.dsesecurity.com/updates/dse-updates-editorial-methodology/", "usageInfo": "https://update.dsesecurity.com/usage/", "copyrightHolder": { "@id": "https://dsesecurity.com/#organization" }, "copyrightNotice": "Copyright © 2026 Detection Systems & Engineering. All rights reserved.", "citation": { "@type": "CreativeWork", "name": "AWS Documentation", "url": "https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/Stop_Start.html" } } ] } }