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

Improve support for AWS GovCloud #855

Closed
jeanduplessis opened this issue Aug 31, 2023 · 5 comments
Closed

Improve support for AWS GovCloud #855

jeanduplessis opened this issue Aug 31, 2023 · 5 comments
Labels
enhancement New feature or request is:triaged Indicates that an issue has been reviewed. stale

Comments

@jeanduplessis
Copy link
Collaborator

jeanduplessis commented Aug 31, 2023

What problem are you facing?

Support for AWS GovCloud is lacking in the provider today. We need to implement proper support for it.

Examples of issues users have faced so far:

How could Official AWS Provider help solve your problem?

Implement proper support for GovCloud.

Consider looking at how crossplane-contrib/provider-aws deals with this:

@jeanduplessis jeanduplessis added enhancement New feature or request needs:triage is:triaged Indicates that an issue has been reviewed. and removed needs:triage labels Aug 31, 2023
@mbbush
Copy link
Collaborator

mbbush commented Nov 6, 2023

One difficulty in supporting this using upjet is that when writing an ExternalName configuration, the region is available, but not the partition.

What if we had an ARNBuilder function or something, for use in constructing ARNs, which knew which regions are in which partitions? That could also help DRY up some of the string concatenation used in external name configurations, where we're currently assuming the aws-commercial partition, for e.g. iam policy, sns topic, elasticsearch domain, state functions, and others

Copy link

github-actions bot commented Apr 2, 2024

This provider repo does not have enough maintainers to address every issue. Since there has been no activity in the last 90 days it is now marked as stale. It will be closed in 14 days if no further activity occurs. Leaving a comment starting with /fresh will mark this issue as not stale.

@github-actions github-actions bot added the stale label Apr 2, 2024
Copy link

This issue is being closed since there has been no activity for 14 days since marking it as stale. If you still need help, feel free to comment or reopen the issue!

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 17, 2024
@jacob-kuder
Copy link

Any update on this?

@jacob-kuder
Copy link

/fresh

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request is:triaged Indicates that an issue has been reviewed. stale
Projects
None yet
Development

No branches or pull requests

3 participants