Skip to main content

This is a new service. Help us improve it and give your feedback by email.

Walkthrough Complete - LocalGov Drupal

You’ve completed the LocalGov Drupal walkthrough

Walkthrough complete

You've explored LocalGov Drupal with AI features

Congratulations! You've just experienced a modern, AI-enhanced content management system designed specifically for UK councils. In 15 minutes, you've seen what would typically require weeks of vendor meetings and procurement processes.

What you've learned

🖥️ Modern CMS experience

LocalGov Drupal provides a familiar, intuitive editing experience. Content editors can work confidently without technical training.

Value: Reduced training costs and faster content updates

🏛️ Council-specific design

Pre-built content types for services, guides, and directories. Follows GOV.UK design patterns that residents expect from government services.

Value: Faster setup with proven, accessible templates

☁️ Cloud-native deployment

One-click deployment on AWS. No server management, automatic scaling, and built-in security. Infrastructure as code for reproducibility.

Value: Lower operational overhead and faster time-to-value

🤖 AI-ready platform

This deployment is the foundation for AI-powered content editing, accessibility enhancements, and dynamic council generation features.

Value: Future-proof investment in modern technology

What's next

Share your findings

Create a PDF evidence pack to share with your stakeholders, committee members, or IT leadership team.

Generate Evidence Pack

Next steps

Generate Evidence Pack

Create your business case with what you've learned. Perfect for committee papers.

Generate Evidence Pack

Return to LocalGov Drupal

Review deployment options, costs, and technical details.

Back to scenario

Try Another

Explore more AI scenarios for local government.

Browse scenarios

Clean up your resources

Good news: Your resources will automatically delete after 2 hours from deployment. However, you can delete them now to stop any further charges immediately.

Warning Deleting your stack will permanently remove all data including:
  • Database content (RDS Aurora)
  • Uploaded files (EFS storage)
  • Any configuration changes you made

Step-by-step deletion

  1. Open the CloudFormation console

    Go to CloudFormation console (US East 1) (opens in new tab)

  2. Find your stack

    Look for a stack named: ndx-try-localgov-drupal-[timestamp]

    The timestamp is when you deployed. You can sort by "Created time" to find recent stacks.

  3. Select and delete

    Select the checkbox next to your stack, then click the Delete button.

  4. Confirm deletion

    Click Delete in the confirmation dialog. The stack status will change to DELETE_IN_PROGRESS.

  5. Wait for completion

    Deletion typically takes 5 to 10 minutes. The stack will disappear from the list when complete.

Costs stop after deletion

Once your stack is deleted, you will not incur any further charges for this scenario.
Estimated evaluation cost: Less than $0.50 for a 15-minute trial

Troubleshooting

Stack shows DELETE_FAILED status

This usually happens when resources can't be automatically cleaned up. Common causes:

  • S3 bucket not empty: The bucket may contain files. Go to S3, empty the bucket manually, then retry deletion.
  • Lambda functions in use: Wait a few minutes and retry. Sometimes functions take time to fully stop.
  • Network interfaces still attached: These usually clear within 5 to 10 minutes. Retry the deletion.

To retry deletion: Select the failed stack and click Delete again.

I can't find my stack in the list

If your stack isn't visible:

  • Check the region: Make sure you're viewing US East (N. Virginia) in the console header.
  • Stack already deleted: It may have auto-deleted after 2 hours. No action needed!
  • View deleted stacks: Click "View nested" dropdown and select "Deleted" to see recently deleted stacks.
Extending your evaluation time

If you want to continue testing beyond the 2-hour limit:

  • Resources will auto-delete after 2 hours total (from deployment)
  • Cost: approximately $1-2 per hour of active testing
  • Maximum cost is capped by template configuration

You can redeploy the scenario anytime to start fresh with a new 2-hour window.

Still having trouble? Contact the NDX:Try team or report an issue on GitHub (opens in new tab).

Try related scenarios

Explore other AI-powered scenarios for UK councils:

Questions or feedback?

We'd love to hear about your experience with this walkthrough: