Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explore and document ECS Exec usage with Incubator #80

Closed
5 tasks
JasonEb opened this issue Feb 21, 2023 · 1 comment
Closed
5 tasks

Explore and document ECS Exec usage with Incubator #80

JasonEb opened this issue Feb 21, 2023 · 1 comment
Labels
complexity: large feature: guide how to's for the team to use incubator (can be wiki pages, contributing.md, etc.) ready for CoP Lead role: Dev Ops Engineer Engineer who maintains and deploys software size: 3pt Can be done in 13-18 hours skill: fargate

Comments

@JasonEb
Copy link
Contributor

JasonEb commented Feb 21, 2023

Overview

As a developer/system administrator/tech lead, I'd like documentation showcasing how to securely interact with Fargate applications on Incubator.

Currently the HFLA's incubator leverages ECS + Fargate to deploy software. A common use case would be how to connect into a deployed Fargate instance in order to manage its contents.

https://aws.amazon.com/blogs/containers/new-using-amazon-ecs-exec-access-your-containers-fargate-ec2/

Action Items

  • Determine service costs
  • Determine prerequisites
  • Document local setup
  • Document usage
  • Create article on Incubator/Ops wiki

Resources/Instructions

Resources
AWS Exec article
AWS ECS Exec for Debugging

@JasonEb JasonEb added dependency size: 3pt Can be done in 13-18 hours labels Feb 21, 2023
@ExperimentsInHonesty ExperimentsInHonesty transferred this issue from hackforla/ops Jun 13, 2024
@github-project-automation github-project-automation bot moved this to New Issue Review in CoP: DevOps: Project Board Jun 27, 2024
@ExperimentsInHonesty ExperimentsInHonesty added feature: guide how to's for the team to use incubator (can be wiki pages, contributing.md, etc.) skill: fargate role: Dev Ops Engineer Engineer who maintains and deploys software complexity: large ready for CoP Lead and removed feature: missing role: missing dependency: missing complexity: missing This label means the issue is missing a complexity label size: missing labels Aug 8, 2024
@sudhara
Copy link
Member

sudhara commented Aug 15, 2024

Per conversation at the leads meetings with @ExperimentsInHonesty , @chelseybeck , @RSkuma , @ale210 this issue is not needed. The reason being, no one should be able to update the contents of the ECS instance other than the GitHub pipeline CI/CD. We can revisit this later if it's needed in the future.

@sudhara sudhara closed this as not planned Won't fix, can't repro, duplicate, stale Aug 15, 2024
@github-project-automation github-project-automation bot moved this from New Issue Review to Done in CoP: DevOps: Project Board Aug 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity: large feature: guide how to's for the team to use incubator (can be wiki pages, contributing.md, etc.) ready for CoP Lead role: Dev Ops Engineer Engineer who maintains and deploys software size: 3pt Can be done in 13-18 hours skill: fargate
Projects
Development

No branches or pull requests

3 participants