-
Notifications
You must be signed in to change notification settings - Fork 4
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
Convert Endpoint Service Catalog to Fargate #280
Convert Endpoint Service Catalog to Fargate #280
Comments
I attempted to start out with the bog-standard However, we ran into a neat little catch-22:
So I attempted to refactor the standard template into a new one that implemented the additional Listeners and Path, using the lessons of the existing Got it all working, everything looks like it'll work, but in the end CloudFormation isn't able to consider the deployment successful because the containers continually report "Task has exited" prematurely, with an error This error is new to us, so a little google-fu and we run across many explanations similar to this one: Which basically tells us that for whatever reason, the Task is not able to reach ECR over the Internet - i.e. there's a routing or SecurityGroup limitation so that all ECR download requests go answered. |
Further:
|
It turns out this is a test. Did you see the error above? The answer is up there in black and white, and you'll know it when you see it. ....spoilers ahead.... Did you see it?
No? Well then you're no worse than me at this. Look closer: Yep, somehow I slipped another character in, and the only way I noticed it was by pasting, then Cmd-Z'ing, and back and forth, until I noticed the reason why the |
Once this was conquered, I then attempted to deploy a flattened version of the SPA, where all files were housed at the root route, so that rather than requesting But alas, this is not to be. When we route only As I've said before, if we were to try to capture all requests for just the files at the root of the So I'm back to suffering with a one-off template (fargate-endpoints-catalog.yaml) that will likely only ever be used for one resource in all our assets on this HackOregon "stack". And while that works fine, it's definitely going to be a stumbling block for a future maintainer of this project (even future me is likely to get tripped up again). |
This should be a trivial operation - it's a single-page nginx app after all - but of course there are complications.
Related to #244 but will require special work one way or another.
The text was updated successfully, but these errors were encountered: