Can we add the service discovery end point for a micro service in console when creating service template, something similar to what's available in sample templates or will it be available in near future?

Excellent! Happy to see that it worked. Closing this issue for now

Hi @rafavallina , After creating template through given configuration, i was able to get the service discovery option while creating a service,

Thank you

Hi @rafavallina , thank you for the response, i understand that we will be able to configure the service endpoints in template configuration and pushing them to s3 and when creating the template providing the s3 url that will gives us the output keys ServiceEndpoint, ServiceDiscovery in output e.g,

But i'm interested to know if there is another process, can we be able to provide directly add these inputs in proton console directly like how we are able to give the name, description, or other properties, while creating templates via console

Thank you

Support using PrivateLink for secure access to the Proton endpoint

This was launched at GA and I missed updating the roadmap: https://docs.aws.amazon.com/proton/latest/adminguide/infrastructure-security.html

Hi @hari-swrl if I'm getting this right, this is something that you can already do, by making the endpoint available as an output in the IaC template. See here: https://github.com/aws-samples/aws-proton-sample-templates/blob/79313fb73fded293d0bd91b3a4f28aea87b93d17/loadbalanced-fargate-svc/service/instance_infrastructure/cloudformation.yaml#L305

Any outputs in the IaC template will be passed on to Proton and visible in the Proton console.

This is exciting! Thanks so much everyone for the excitement. @MPM3278, @RichiCoder1, @adi-ads I'll reach out to you on email. @warden I personally prefer a round of 1:1s, even if it takes longer, so we can discuss more in-depth - happy to talk now or as we get closer to it :)

Much smaller team, but also interested in what Terraform + Proton could/would look like: [email protected]

@rafavallina how about having a roundtable of people interested (maybe in a second stage) so that we all know where Proton will be heading? :-) (ps. you can reach me at [email protected])

Hi Rafa,

We are heavily interested in AWS Proton since its announcement. All our IaC is heavily Terraform based and we are keen upcoming integration between Proton and TF. I can be reached at [email protected]

Can we add the service discovery end point for a micro service in console when creating service template, something similar to what's available in sample templates or will it be available in near future?

@rafavallina we are running 40 different software teams and evaluating proton to help drive support for all the teams from a core release & infrastructure team. Can be reached on [email protected]

Thanks @ahilsend! I'll drop you an email and we can go from there

Hi @rafavallina! We are heavy users of Terraform Open Source and are currently looking into AWS Proton for our future services deployments. This would be a huge benefit for our teams. Please feel free to get in touch via [email protected].

Hi @warden Thanks! I'd be happy to talk - I'm not sure I fully understand your setup, so it'd be helpful for me to figure it out

I'm happy to join the discussion, especially around CI/CD of terraform maintaned infra and how Proton is positioning itself there. TBH I'm looking at Proton, but I haven't found (yet?) any examples of e.g. serverless workflows for CI/CD of multi-service applications. For example, we have multiple repositories with repo-per-service and one infra repository that manages via CDK the shared infrastructure like DynamoDB tables etc. - I'm curious if Proton could help in this kind of workflow.

I'm happy to join the discussion, especially around CI/CD of terraform maintaned infra and how Proton is positioning itself there. TBH I'm looking at Proton, but I haven't found (yet?) any examples of e.g. serverless workflows for CI/CD of multi-service applications. For example, we have multiple repositories with repo-per-service and one infra repository that manages via CDK the shared infrastructure like DynamoDB tables etc. - I'm curious if Proton could help in this kind of workflow.

Hello everyone, this request has a bunch of notes and +1s, which is very exciting. Thanks! I'm actually in the lookout for customers using Terraform Open Source, to learn more about how it works today and ask questions about what Proton can do. If anyone in this thread is interest, please tell me and we can figure out a way to connect! Thanks :)

Hi @rafavallina, Would love to get in contact with you to talk about this! Our team has been looking forward to using proton since it was announced :)

Awesome! How can I reach out to you? You can also try to send me a Twitter DM on twitter.com/rafavallina

Please feel free to reach me at [email protected]!

Hi, @rafavallina.

Hi @xeres the CloudFormation stack for the environment and each individual service instance all goes into the environment account, not in the management account. The only thing that's in the management account is the Proton resource itself (e.g. the environment resource or the service resource).

In my case, it looks like the following.

The management account:

AWSProton-<service>-cloudformation--<random letters> (This includes the ECR repository)

The environment Account:

AWSProton-<service>-<service instance>-cloudformation--<random letters> (This includes task definitions and the ECR service)

It succeeds right after the service instance is created. However, when the user updates the Dockerfile, the CI/CD pipeline runs the build and fails.

Because the ECR service can't pull an image from the management account, and the ECR repository does not allow cross account access by resource policies.

In this way, we needed the the environment AWS account ID in pipeline_infrastructure, and the administrator must implements cross account resource policies.

If this is trouble, should I contact AWS support? AWS Proton has already GA, haha.

Hi @frgud , Can you let us know which sample project you were trying to deploy when you got this exception?

Hi @viniciuschiele I'm sorry for the radio silence, I messed up my GH notifications and did not realized I had a bunch of pending stuff.

Did you try calling UpdateServicePipeline? https://docs.aws.amazon.com/proton/latest/APIReference/API_UpdateServicePipeline.html

The pipeline has to be treated like any other instance, and needs to be updated explicitly

Hi @xeres the CloudFormation stack for the environment and each individual service instance all goes into the environment account, not in the management account. The only thing that's in the management account is the Proton resource itself (e.g. the environment resource or the service resource). No CFN stacks in the management account in this case. Can you check if you have a different experience? If not, I'll close this issue as I think this is working.

Hello,

When creating a Proton service instance as part of the Create Service workflow in the AWS Console, I continually get the "unique_name required" error when supplying a service instance name. The service instance name is unique as I have no other service instances deployed. This blocks my ability to create a service instance.

Hi @frgud and apologies for not answering before as I messed my GitHub notifications. Have you tried reaching out to AWS support about this topic?

I'm going to close this issue for now as this roadmap is to influence future direction of the service. Please reopen if this is a systematic issue

@ngamradt-turner No, I think you got it right. We are thinking about the same. Will continue to update this channel as we make progress!

<!-- Please keep this note for the community -->

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

<!-- Thank you for keeping this note for the community -->

<!--

Security disclosures

If you think you’ve found a potential security issue, please do not post it in the Issues. Instead, please follow the instructions here or email AWS security directly.

-->

Tell us about your request Multi-account support is now available. Thank you for your hard work. I have tried using the sample template bundle (fargate-service).

SEE ALSO: aws-sample/aws-proton-sample-templates@main/loadbalanced-fargate-svc

AWS Proton creates the CloudFormation stack for the service in the management account if I'm not misunderstanding. This stack includes the ECR repository.

So, I push some Dockerfile to the repository; Fargate cannot pull a new image from the ECR repository.

However, the ECR repository does not have a resource policy to allow access from the environment account. Therefore, I probably have no way to get the environment AWS account ID in pipeline_infrastructure.

SEE ALSO: Infrastructure template file parameters - AWS Proton Environment account connections - AWS Proton

To solve this problem, I believe we need a variable in the Jinja template to get the environment AWS account ID to create resource policies.

Are you currently working around this issue? Although I haven't tried it yet, setting resource policies in ECR outside of AWS Proton's control.

Hello @rafavallina, based on my limited knowledge of the product, it appears that environments and services would be more important since templates can be uploaded as a bundle and reused (this is based on what I have read, haven't worked with it yet). If I am misunderstanding, please let me know.

@ngamradt-turner thanks for reaching out! No updates to give, but we are actively working on delivering this functionality. Will post here as we make further progress. A detail that would help with decision making: if we were to deliver some resource types before others (for instance, environments and services before environment templates) - what would be your preferred priority?